Network Manager cannot handle IPv6 router advertisements properly

[dgf]

Hi,

I have setup my network with an IPv6-tunnel. I installed radvd on my router, which runs openwrt 10.03.1, to announce the IPv6-capability. Inside these router advertisements my router is also as DNS-Resolver advertised. Network Manager causes high CPU load on my laptop and puts a lot of text into syslog.

I think this is also related to this bug in debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649205

I use Ubuntu 12.04 on a Thinkpad X220. When I figured how to upload my syslog, I will put it here.

grats dgf
---
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
DistroRelease: Ubuntu 12.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
 default via 192.168.1.2 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.130 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=de:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise
Uname: Linux 3.2.9-030209-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-02-14 (34 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WifiSyslog:
 Mar 20 09:20:21 barcas kernel: [69466.692279] iwlwifi 0000:03:00.0: Tx aggregation enabled on ra = 20:4e:7f:6f:78:f3 tid = 0
 Mar 20 09:20:30 barcas wpa_supplicant[794]: WPA: Group rekeying completed with 20:4e:7f:6f:78:f3 [GTK=CCMP]
 Mar 20 09:21:08 barcas kernel: [69514.139758] iwlwifi 0000:03:00.0: Tx aggregation enabled on ra = 20:4e:7f:6f:78:f3 tid = 0
 Mar 20 09:22:21 barcas kernel: [69586.457817] iwlwifi 0000:03:00.0: Tx aggregation enabled on ra = 20:4e:7f:6f:78:f3 tid = 0
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-02-18T12:45:39.014900
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.3.995 connected enabled enabled enabled enabled enabled

[dgf (dgf)]

here comes the syslog in a compressed file. launchpad did not accept it uncompressed

[Mathieu Trudel-Lapierre (cyphermox)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 958519

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

apport information

[dgf (dgf)]

I was wrong with the debian bug in the description. This one seems to be a different one. Please do something about it, because this one causes a lot of disc writes into syslog and a high cpu-usage.

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu1

---------------
network-manager (0.9.4.0-0ubuntu1) precise; urgency=low

  * New upstream release 0.9.4.0: (LP: #960494)
    - settings: quiet warning when checking for AdHoc WPA connections
    - core: suppress useless log message when route already exists (LP: #958519)
    - TODO: remove bridging/bonding and InfiniBand
    - core: do a better job of applying bond configuration
    - libnm-util: improve NMSettingBond:verify()
    - libnm-util: fix an NMSettingBond bug
    - core: fix NMDeviceBond:dispose() to chain up
    - wifi: work around more wl.o stupidity
    - ip6: fix setting default route with libnl3 (bgo #668286)
    - firewall: set interface zone before IP configuration (rh #805405)
    - libnm-glib: ensure bindings-created objects work as expected (rh #802536)
    - mobile: ensure IPv4 timeout fails activation
    - utils: override VPN plugin's never-default when ignoring auto routes
    - wifi: make sure we're connected to netlink before using it
    - libnm-glib: add 'registered' property for NMSecretAgent
    - keyfile: fix testcases after InfiniBand transport-mode default change
    - wifi: disable Ad-Hoc WPA connections (LP: #905748)
    - infiniband: fix missing sentinel
    - Add a workaround for a problem creating InfiniBand connections
    - core: treat missing IPv6 setting as AUTO
    - libnm-glib: add errors to nm_device_connection_compatible() and device
      classes
    - vpn: add a new field so VPN plugins can specify multiple domains
    - dnsmasq: allow proxying dnssec data (upstreamed Ubuntu patch)
    - gsm: pass the PPP auth preferences for STATIC and DHCP device use
    - core: allow IPv4 to fail by default
  * debian/control: add Pre-Depends as required for maintscript.
  * debian/control: bump debhelper Build-Depends to (>= 8.1.0~).
  * debian/control: bump Standards-Version to 3.9.3.
  * debian/copyright: update copyright and migrate to format 1.0; thanks to
    Michael Biebl for the work. (LP: #907294)
  * debian/patches/nm-change-dnsmasq-parameters.diff: refreshed.
  * debian/patches/dnsmasq-dnssec-passthrough.patch: dropped, applied upstream.
  * debian/patches/nl3-default-ip6-route.patch: dropped, applied upstream.
  * debian/libnm-glib4.symbols: add new symbols:
    + nm_device_connection_compatible@Base
    + nm_device_*_error_get_type@Base
    + nm_device_*_error_quark@Base
    + nm_secret_agent_get_registered@Base
  * debian/network-manager.postrm: cleanup timestamps and seen-bssids files on
    purge.
  * debian/network-manager.{pre,post}inst: clean up and remove old migration
    steps; we can reimplement just the ones we need in maintscript.
  * debian/network-manager.maintscript:
    - fix the migration of /etc/dbus-1/system.d/NetworkManager.conf to its new
      name /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, so we do
      not have leftover files after upgrade.
    - reimplement the rename of nm-system-settings.conf to NetworkManager.conf
      in this format (Debian has already done so).
  * debian/patches/git_doc_fixups_54618a7.patch: fix building documentation to
    make sure the documentation pages aren'...

[Mathieu Trudel-Lapierre (cyphermox)]

What we fixed there was obviously just the error message. For the rest, we pretty much have to deal with restarting dnsmasq when there is a new router advertisement (because addresses may have changed). That's something we should possibly look into for precise+1.

As a workaround, I would suggest changing the interval for router advertisements if it's possible.

[dgf (dgf)]

At the moment it is fine. Either Network-Manager nor dnsmasq spams my syslog. I let you know, if it happens again.