This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu4.1
---------------
network-manager (0.9.4.0-0ubuntu4.1) precise-proposed; urgency=low
* debian/network-manager.upstart: add "and static-network-up" to ensure the
loopback device is really up before we start dnsmasq. (LP: #993379)
* debian/patches/git_kernel_ipv6_default_route_77de91e.patch: avoid fighting
with the kernel for what IPv6 default route should be set: let the kernel
set his own, then add a new route with a different metric so that we can
go back and remove it later. (LP: #988183)
* debian/patches/nm-ip6-rs.patch: avoid disconnections due to RDNSS expiry,
send a Router Sollicit to try and get new RDNSS data. (LP: #993571)
-- Mathieu Trudel-Lapierre <[email protected]> Thu, 24 May 2012 20:39:12
-0400
** Changed in: network-manager (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993379
Title:
Network Manager starts before the loopback device is ready, leading to
dnsmasq not listening on any interface, breaking DNS resolution
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993379/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
