I just want to add a comment that the reason for the problem itself is that both the IPv4 and IPv6 stacks receive a pointer to the same DNS server using both an IPv4 address and an IPv6 address.
Once I disabled IPv6 name servers in both radvd and isc-dhcp-server6 configurations and only used an IPv4 address to point to the DNS server the error disappeared from my logs. Not having IPv6 DNS servers will obviously affect IPv6-only clients. I would argue that pointing to the same DNS server using both IPv4 and IPv6 on a dualstack machine is the correct thing to do, so the message shouldn't really trigger any error. I'm not sure how the DNS server is determined to be the same, I'm assuming ARP or some identifier sent from the DNS server validates that claim. If so, the simple workaround might be to return a different identifier from the DNS server based on IPv4 or IPv6 connection. -- 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/996032 Title: Constant _ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed messages in syslog Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Status in “network-manager” package in Fedora: Unknown Bug description: [Impact] Causes extra messages to spam syslog on every address addition netlink message, or every route change. (Very often) No actual behavioral impact aside from a log which is potentially very rapidly growing due to these warning messages. [Test Case] This requires an Apple Airport device connected in IPv6 tunneling mode. 1) Connect the computer to the Airport device's network. You should see IN6_ARE_ADDR_EQUAL assertions without the patch, and no such messages with the patch applied. [Regression Potential] Changes testing logic for IP address comparison to return silently rather than asserting (because assertions cause the messages to be printed to syslog); so no actual impact on that side except for the messages not being printed out. However, this introduces duplicates checking for the routes and addresses as well, which has a small potential for extra routes to be missing if the duplicate checking fails to consider extra flags which would make the similar-looking routes or addresses actually very different. ---- When both the Ethernet and wlan are connected to an Apple Airport running IPv6. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CheckboxSubmission: 55cafa5b8b82ed224cc59d444cb1fc25 CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab Date: Mon May 7 17:31:00 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.112 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.108 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-07 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Apple Network ad3977 6e164836-7615-41dd-b5bb-d76c15a3d43c 802-11-wireless 1336408221 Mon 07 May 2012 17:30:21 BST yes no /org/freedesktop/NetworkManager/Settings/2 Ethernet 8d5e9b11-7cd5-4f58-a0fd-3f3cbea16909 802-3-ethernet 1336408221 Mon 07 May 2012 17:30:21 BST yes no /org/freedesktop/NetworkManager/Settings/1 Brightbox 92ea9b57-86a6-4867-b825-5c8278657559 vpn 1336407670 Mon 07 May 2012 17:21:10 BST no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernet connected /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996032/+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
