In Progress/High. It's kind of annoying, if only just for the log
entries. All of the connection/disconnection states depend a lot on the
RA interval used, but that's still also quite annoying, and the fix is
clearly safe (as it's a new route with a different metric, so we don't
risk breaking stuff too much).
I'm sponsoring this to -proposed shortly, just need to apply the
debdiff, quickly test that it's properly adding the routes, and we
should be ok. It will need to be carefully tested to make sure the added
metric doesn't clash with wireless/wired coexistence: basically, we need
to make sure that on a system connected to both wired and wireless that
has ipv6 on both interfaces, the wireless default v6 route added by NM
needs to have a lower priority (higher metric) than the default ipv6
route added by NM for the wired interface. This will make sure ethernet
remains "preferred" in the event that these networks are in fact
different, and I'm a little worried that the upstream patch breaks this.
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
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 “network-manager” package in Ubuntu:
In Progress
Bug description:
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/ubuntu/+source/network-manager/+bug/988183/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
