[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-05-29 Thread Thomas M Steenholdt
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 This is not fixed, but is marked as a duplicate of #1624317 ** This bug has been marked a duplicate of bug 1624317 systemd-resolved breaks VPN with split-horizon DNS -- You received this bug

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-04-19 Thread Lonnie Lee Best
@gatoguan-os : You must have been speaking about the work-around here? https://bugs.launchpad.net/network-manager-applet/+bug/1633874 Is the above really a duplicate or not? Lately, I have not even been able to get that work-around (in the link above) to work in 16.04. Also, this is a related

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-04-19 Thread Thomas M Steenholdt
Seems to work in 1.4.4-1ubuntu3 in 17.04 at least... Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-04-05 Thread gatopeich
Seems fixed in version 1.2.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in NetworkManager-OpenVPN: New Status in

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-03-31 Thread gatopeich
Downgrading network-manager package (not the VPN ones) to v1.1.93 solves the issue so this is an obvious regression. Note that there was another bug marked as a duplicate of this one but with a more user-friendly description, along with the workaround. ** Changed in: network-manager (Ubuntu)

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Lonnie Lee Best
Bryn, thank for the suggested work around. However, it is not a workaround for me. My issue is that I have over 100 Remmina RDP desktop configurations saved that connect to numerous computers on different VPNs by computer name (not by ip address). However, I cannot ping those computers by name

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Thomas M Steenholdt
That is certainly a possibility, but unfortunately returns us to a state where applications have to be restarted when nameservers change (glibc resolved.conf issue). That's probably even worse in my situation at least. -- You received this bug notification because you are a member of Desktop

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Bryn Cooke
This workaround worked for me in 16.10: In /etc/NetworkManager/NetworkManager.conf Comment out: dns=dnsmasq The run: sudo service NetworkManager restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Aron Xu
** Tags added: nm-improvements -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in NetworkManager-OpenVPN: New Status in

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-20 Thread Lonnie Lee Best
Why is the status of this incomplete. I've verified this issue from numerous perspectives that probably all fundamental point directly to the issue Thomas has reported; see post#2. This is a terrible bug. Network-Manager updates were prematurely released to 14.04 stable and all succeeding

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-12 Thread Thomas M Steenholdt
Unfortunately not much traction here, and this appears to annoy people across distros. In the meantime, an ugly hack is to manually add all internal domains to the NetworkManager VPN config file's dns-search= parameter: dns-search=domain1.lan;domain2.lan;domain3.lan;example.com; This causes

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-05 Thread Thomas M Steenholdt
Wow - Long message, but what I got from it was "I need to see a debug log", correct? I'll attach that... I'll also point you to the problematic part: Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1915] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-05 Thread Mathieu Trudel-Lapierre
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

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-28 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-27 Thread Lonnie Lee Best
** Also affects: network-manager-openvpn Importance: Undecided Status: New ** Also affects: network-manager-vpnc Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-27 Thread Bryn Cooke
Does anyone know a workaround for 16.10? There is no option to downgrade the package there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Thomas M Steenholdt
Here's the thing, I'm on 16.10 which has the debian equiv listed as stretch/sid and my network-manager version is 1.2.4-0ubuntu1. Looking at Debian stretch and sid, they have network-manager packages in various versions but not 1.2.4. Furthermore, since Ubuntu employ their own patches,

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
For me, on 16.04.1, that's: debian stretch/sid I'm experiencing the issue on both 16.04.1 and 16.10. I posted a work around here: https://bugs.launchpad.net/network-manager-applet/+bug/1633874 -- You received this bug notification because you are a member of Desktop Packages, which is

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
You can find out with this command: cat /etc/debian_version Source: http://askubuntu.com/questions/445487/which-ubuntu-version-is-equivalent-to-debian-squeeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Thomas M Steenholdt
I'll do it :) Any helpful pointers to which package/version i should reference, since I don't have the real debian version of this package anywhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
One of us is going to have to endure submitting a new bug to debian regarding this issue and then linking that bug to this ubuntu bug. I think their bug system is email based and it is always an extra pain for me to deal with. So, I'd appreciate not having to be the one to do this. Thomas seems to

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Thomas M Steenholdt
No, that does not seem like the problem to me - Or it's not described correctly. I can't seem to find a proper match in that list. resolv.conf is not the issue here - the problem is in the DNS servers that dnsmasq uses. I.e. one is added to dnsmasq when my wireless connection comes up, and when I

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
Is this the cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777004 ??? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
Can someone figure out which of these debian bugs should be linked with this Ubuntu bug report: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=dnsmasq;dist=unstable ** Bug watch added: Debian Bug tracker #777004 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777004 -- You received this

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-26 Thread Lonnie Lee Best
** Tags added: xenial yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in network-manager package in Ubuntu:

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-20 Thread Lonnie Lee Best
If the "order in which dns servers are queried" is flawed, as you've discovered. That might be the root cause of a lot of other outstanding bugs: VPN - "Additional DNS servers" Settings are being Ignored: https://bugs.launchpad.net/network-manager-applet/+bug/1633874 network-manager ignoring DNS

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-10-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.