This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu5
---------------
network-manager (0.9.4.0-0ubuntu5) quantal; 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)
* debian/patches/git_remove_ifpppstatsreq_6b64e4d.patch: remove the use of
the ifpppstatsreq struct, which has been dropped in newer kernels: use
ifreq and ppp_stats separately instead.
-- Mathieu Trudel-Lapierre <[email protected]> Wed, 23 May 2012 15:28:36
-0400
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
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/988183
Title:
Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
default route"
Status in NetworkManager:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “network-manager” package in Fedora:
Unknown
Bug description:
[Impact]
Minor impact, this should only be affecting users of the kernel mainline
packages since we're not shipping kernel 3.3.0 where the issue is presumed to
occur, take care of letting these users also benefit from stable connections
since they may need these kernels for new hardware support (and kernels that
may be backported in the future). This only affects IPv6-enabled network where
the kernel expects to setup a default route by itself and doesn't play nice
with something else modifying the routes.
[Development Fix]
Fixed upstream, as
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=77de91e5a8b1c1993ae65c54b37e0411e78e6fe6.
See https://bugzilla.gnome.org/show_bug.cgi?id=673476 (upstream bug). This
change only affects NetworkManager's code, doesn't require rebuild of any
dependant package.
[Stable Fix]
See above "Development fix".
[Test Case]
1) Connect to an IPv6 network with a kernel 3.3.0 or higher.
2) Observe behavior in 'ip route -6' and messages in /var/log/syslog.
Wireless connections should remain stable.
[Regression Potential]
Only IPv6 could be affected, no potential for regression expected for IPv4
routing or other parts of NetworkManager. Routing may be incorrect, resulting
in the wrong device taking precedence for data being sent over the network when
IPv6 is in use; IPv6 connections (or connections altogether, if IPv6 is set to
"Required" (which is not by default)) may be torn down or unavailable due to
invalid routes.
---------
Hi,
I am observing a lot of "ICMPv6 RA: ndisc_router_discovery() failed to add
default route" in my logs.
After a fresh reboot:
$ dmesg | grep "ICMPv6 RA: ndisc_router_discovery() failed to add default
route." | wc -l
46
First, I thought this is a kernel issue, but than I found a bug-report
in the Red Hat BTS in [1].
Just FYI: I am on Linux-3.4-rc4 - with the original Ubuntu/precise
kernel I haven't seen this which is linux-image-3.2.0-23-generic
(3.2.0-23.36).
- Sedat -
[1] https://bugzilla.redhat.com/show_bug.cgi?id=785772
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
Uname: Linux 3.4.0-rc4-4-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
Date: Wed Apr 25 08:40:50 2012
ExecutablePath: /usr/sbin/NetworkManager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
IpRoute:
default via 192.168.178.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.22
metric 2
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=de_DE.UTF-8
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE
TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
myCastle-WLAN WPA (Wireless LAN) a74880ae-a336-4133-9454-b0376557cb6c
802-11-wireless 1335335775 Mi 25 Apr 2012 08:36:15 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unmanaged
/org/freedesktop/NetworkManager/Devices/1
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/988183/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
