Yes, please bring to 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592721
Title:
Don't write search domains to resolv.conf in the case of split DNS
To manage notifications about this bug go
Is there a way to backport this to 16.04? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592721
Title:
Don't write search domains to resolv.conf in the case of split DNS
To manage
I think I am observing a regression caused by this fix: after
disconnecting/reconnecting a VPN connection, DNS resolution is broken.
Here are the details:
- VPN is set up as OpenVPN with split-tunneling ("Use this connection
only for resources on its network" is checked). The VPN's DNS domain is
PS: Restarting network-manager an reconnecting to the VPN works around
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592721
Title:
Don't write search domains to resolv.conf in the case
This bug seems to bite me in a slightly different way. Please let me
know if you feel that this is really a separate bug...
Also, this is happening on Yakkety - network-manager-1.2.4-0ubuntu1
When I connect to my work VPN, I'm not using split-tunnelling. Still the
DNS resolution is split,
I'm releasing the SRU now to land the fixes for the other two bugs. I'm
fairly convinced that this at least does not regress the situation here.
If it is not fixed for you after rebooting/restarting dnsmasq, can you
please reopen? Thanks!
--
You received this bug notification because you are a
This bug was fixed in the package network-manager -
1.2.2-0ubuntu0.16.04.3
---
network-manager (1.2.2-0ubuntu0.16.04.3) xenial; urgency=medium
* debian/tests/wpa-dhclient: Don't assume that the IPv6 prefix length from
the DHCP server is /64. (LP: #1609898)
network-manager
James: I'm not familiar with this specific fix, but I know that
restarting NetworkManager will not kill/restart the spawned dnsmasq
instances (by its own choice: KillMode=process). Does it help to stop
NM, kill the dnsmasqs, and then restart it? (Or just a reboot)
--
You received this bug
I'm afraid this didn't work for me. I installed network-manager
1.2.2-0ubuntu0.16.04.3 from xenial-proposed, ran 'systemctl restart
NetworkManager' as root and reconnected to the VPN and I see the same
behaviour (i.e. I get DNS resolution failure for non-VPN domains). I
am on wifi only and both
Hello Mathieu, or anyone else affected,
Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.2-0ubuntu0.16.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this
** Description changed:
+ [Impact]
+ All VPN users meaning to use split-tunnelling in a situation where leaking
DNS data to the internet about what might be behind their VPN is undesirable.
+
+ [Test case]
+ 1) connect to VPN
+ 2) Use dig to request a name that should be on the VPN
+ 3) Verify
This bug was fixed in the package network-manager - 1.2.2-0ubuntu4
---
network-manager (1.2.2-0ubuntu4) yakkety; urgency=medium
[ Mathieu Trudel-Lapierre ]
* debian/patches/libnm-Check-self-still-NMManager-or-not.patch: updated and
refreshed to make gbp pq happy.
*
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification
13 matches
Mail list logo
