FS#69897 - NetworkManager VPN autoconnect DNS leak

Attached to Project: Arch Linux
Opened by Bonnie (g00fyseal) - Saturday, 06 March 2021, 13:49 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 07 March 2021, 20:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When the option to automatically connect to VPN is enabled in the NetworkManager GUI and the computer wakes up from sleep, browserleaks.com/ip reports the DNS addresses from my internet provider. When I manually disconnect and reconnect to the VPN, these addresses are hidden, which is the expected behavior. Recently there was an issue where it was impossible to enable the option to automatically connect to VPN at all since clicking on this option would cause the NetworkManager GUI to crash. This issue was resolved in a recent update, however, now the issue with DNS leaking has appeared.

Additional info:
* package version(s)
nm-connection-editor 1.20.0-2, networkmanager 1.30.0-2

Steps to reproduce:
Enable 'Automatically connect to VPN' in the NetworkManager GUI.
Suspend or restart the computer.
Go to browserleaks.com/ip and check the DNS Leak Test.
Disconnect from VPN then reconnect.
Go again to browserleaks.com/ip and check the DNS Leak Test.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Sunday, 07 March 2021, 20:29 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Configuration issue.
Comment by Jan Alexander Steffens (heftig) - Sunday, 07 March 2021, 15:17 GMT
What's your resolv.conf setup? Are you using systemd-resolved (with /etc/resolv.conf linked to /run/systemd/resolve/stub-resolv.conf)? Are you using resolvconf?
Comment by Bonnie (g00fyseal) - Sunday, 07 March 2021, 16:31 GMT
I don't have /run/systemd/resolve
It seems resolv.conf *sometimes* fails to automatically switch from 'Generated by NetworkManager' to 'Generated by resolvconf' when waking up from sleep.
Comment by Jan Alexander Steffens (heftig) - Sunday, 07 March 2021, 18:30 GMT
Do you require resolvconf (openresolv)? Can you try removing it?
Comment by Bonnie (g00fyseal) - Sunday, 07 March 2021, 19:05 GMT
I cannot remove it, wireguard-tools requires openresolv and I am unable to connect without it.
Comment by Jan Alexander Steffens (heftig) - Sunday, 07 March 2021, 19:17 GMT
Since you say you need resolvconf, NM needs to be configured to use it.

In /etc/NetworkManager/NetworkManager.conf:

[main]
rc-manager=resolvconf
Comment by Bonnie (g00fyseal) - Sunday, 07 March 2021, 20:02 GMT
Adding that has seemed to fix the issue. Thanks. I'll continue to monitor it to make sure it's not a false positive since there is a random nature to this issue.

Loading...