* 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 address hidden> Thu, 24 May 2012 20:39:12 -0400
This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu4.1
--------------- 0-0ubuntu4. 1) precise-proposed; urgency=low
network-manager (0.9.4.
* debian/ network- manager. upstart: add "and static-network-up" to ensure the patches/ git_kernel_ ipv6_default_ route_77de91e. patch: avoid fighting patches/ nm-ip6- rs.patch: avoid disconnections due to RDNSS expiry,
loopback device is really up before we start dnsmasq. (LP: #993379)
* debian/
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/
send a Router Sollicit to try and get new RDNSS data. (LP: #993571)
-- Mathieu Trudel-Lapierre <email address hidden> Thu, 24 May 2012 20:39:12 -0400