Comment 12 for bug 1629611
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
This isn't how VPNs are supposed to work. I understand that things get incredibly complicated in this case, but they are complicated in the first place.
Some things to watch out for:
- IPv4 and IPv6 should both be configured the same way; you want either both to be set to split-tunnelling ("Use this connection only for the resources on its network" under Routes), or both not. Having the two use a different setting will make things not work correctly (you will have the wrong set of DNS nameservers configured in dnsmasq, even if you only have IPv4 nameservers).
- Adding separate nameservers and search domains in the UI may be handled very differently than receiving nameservers from the VPN itself.
If you're seeing this bug, please *file your own* bug report in launchpad, and make sure you add at least the *debug* logs from NetworkManager as well as mentioning exactly how the IPv4/IPv6 and underlying Routes dialogs are configured. To add debug logs for NetworkManager for VPNs, you may run 'nmcli general logging level debug' before reproducing the issue. The information will show up in /var/log/syslog (which is the file you want to include, after reviewing it to remove any sensitive information such as the exact IPs and domain names, or making the bug private).
People should not mark their own bugs as duplicate of others and these kinds of issues are complicated and easily confused as the same thing when they might not be. There is also no point in reporting this on Debian, as they likely don't have the same patches applied.