Launchpad has imported 13 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=820752.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-05-10T21:14:43+00:00 Andrew wrote: Description of problem: This is a wired ethernet network. Is connected to an Apple airport with IPv6 tunneling turned on; the tunneling is provided by Comcast/Xfinity. While the network seems to work okay (including ipv6.google.com), journald is filled up with this representative sample: May 10 10:39:35 mithos.talinet.net dnsmasq[997]: reading /etc/resolv.conf May 10 10:39:35 mithos.talinet.net dnsmasq[997]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 10 10:39:35 mithos.talinet.net dnsmasq[997]: using nameserver 10.0.1.1#53 May 10 10:39:35 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:40:31 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:41:18 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:41:18 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 10 10:41:18 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 10 10:41:18 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:41:27 mithos.talinet.net dnsmasq[997]: reading /etc/resolv.conf May 10 10:41:27 mithos.talinet.net dnsmasq[997]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 10 10:41:27 mithos.talinet.net dnsmasq[997]: using nameserver 10.0.1.1#53 May 10 10:41:27 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:43:31 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:44:26 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:44:26 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 10 10:44:26 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 10 10:44:26 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:45:11 mithos.talinet.net dnsmasq[997]: reading /etc/resolv.conf May 10 10:45:11 mithos.talinet.net dnsmasq[997]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 10 10:45:11 mithos.talinet.net dnsmasq[997]: using nameserver 10.0.1.1#53 May 10 10:45:11 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:45:17 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:45:17 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 10 10:45:17 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 10 10:45:17 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:46:01 mithos.talinet.net dnsmasq[997]: reading /etc/resolv.conf May 10 10:46:01 mithos.talinet.net dnsmasq[997]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 10 10:46:01 mithos.talinet.net dnsmasq[997]: using nameserver 10.0.1.1#53 May 10 10:46:01 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:46:14 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:46:14 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 10 10:46:14 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 10 10:46:14 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:46:36 mithos.talinet.net dnsmasq[997]: reading /etc/resolv.conf May 10 10:46:36 mithos.talinet.net dnsmasq[997]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 10 10:46:36 mithos.talinet.net dnsmasq[997]: using nameserver 10.0.1.1#53 May 10 10:46:36 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed May 10 10:46:36 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 10 10:46:36 mithos.talinet.net NetworkManager[787]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 10 10:46:36 mithos.talinet.net NetworkManager[787]: nm_ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed Version-Release number of selected component (if applicable): Fedora 17, NetworkManager 0.9.4.0.7.git20120403.fc17 How reproducible: Every reboot by default Steps to Reproduce: 1. Have ethernet plugged in 2. Boot 3. Monitor journald Actual results: Log flooded Expected results: Assertion-failure free operation. Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/3 ------------------------------------------------------------------------ On 2012-05-11T22:48:39+00:00 Andrew wrote: Created attachment 583945 NetworkManager Debug log Turned on debug logging on NetworkManager and captured the output. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/4 ------------------------------------------------------------------------ On 2012-05-14T14:22:22+00:00 Dan wrote: OK, so the problem is that your IPv6 tunnel is telling you it has 2 IPv6 nameservers, but it's just actually the same server listed twice, which NM wasn't expecting and so it does something dumb, causing the warning. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/5 ------------------------------------------------------------------------ On 2012-05-14T16:34:53+00:00 Dan wrote: Created attachment 584407 patch Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/6 ------------------------------------------------------------------------ On 2012-05-14T19:35:44+00:00 Andrew wrote: Created attachment 584453 New debug log, NetworkManager.service only I applied the patch against the upstream NetworkManager 0e262e04e1800f312d4c40c07b6394ffacb2d34d. While there are no assertions as expected, there is still something screwy going on causing a repetative reconfiguration, shown below. I've also attached the output of journalctl _SYSTEMD_UNIT=NetworkManager.service although it looks to be relatively the same as the previous log. I've also noticed that this isn't a problem when the IPv6 configuration is set to 'DHCP only', but that's probably expected. May 14 12:10:49 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:10:49 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:10:49 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 May 14 12:11:18 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:11:18 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:14:24 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:14:24 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:14:24 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 May 14 12:14:28 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:14:28 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:14:36 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:14:36 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:14:36 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 May 14 12:14:36 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:14:36 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:14:36 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:14:36 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:14:37 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:14:37 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:15:19 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:15:19 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:15:19 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 May 14 12:16:05 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:16:05 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:17:01 mithos.talinet.net /USR/SBIN/CROND[2725]: (agpotter) CMD (/usr/bin/flexget --cron) May 14 12:17:04 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:17:04 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:17:04 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 May 14 12:17:04 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv4 routing and DNS. May 14 12:17:04 mithos.talinet.net NetworkManager[651]: <info> Policy set 'System p5p1' (p5p1) as default for IPv6 routing and DNS. May 14 12:21:16 mithos.talinet.net dnsmasq[796]: reading /etc/resolv.conf May 14 12:21:16 mithos.talinet.net dnsmasq[796]: using nameserver 2002:62f4:3669:0:21e:52ff:fef1:811a#53 May 14 12:21:16 mithos.talinet.net dnsmasq[796]: using nameserver 10.0.1.1#53 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/7 ------------------------------------------------------------------------ On 2012-05-14T19:45:38+00:00 Dan wrote: (In reply to comment #4) > Created attachment 584453 [details] > New debug log, NetworkManager.service only > > I applied the patch against the upstream NetworkManager Oh! Cool, I was just putting it here for the other maintainers to look at. :) > While there are no assertions as expected, there is still something screwy > going on causing a repetative reconfiguration Oh, yeah, it wasn't expected to change that; for some reason, your IPv6 tunnel is configured to send out router advertisements extremely frequently. So each time it gets one, NM checks the data in it to see if anything changed since the last one. I guess we're not checking whether we actually need to update dnsmasq or not, so it's getting "updated" even when nothing changed. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/8 ------------------------------------------------------------------------ On 2012-05-15T15:52:08+00:00 Dan wrote: Pavel, see above; another thing to look at in your NMIP6Manager fixes (we're apparently emitting config-changed on RDNSS announcements even when nothing changed, resulting in unnecessary syslog spew) Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/9 ------------------------------------------------------------------------ On 2012-05-15T20:28:24+00:00 Dan wrote: fixed in git. since it doesn't actually affect functionality, I'm not going to worry about getting it into F17 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/10 ------------------------------------------------------------------------ On 2012-05-18T08:17:41+00:00 Pavel wrote: Thank you, Dan. I'll look into it. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/11 ------------------------------------------------------------------------ On 2012-05-21T17:11:35+00:00 Fedora wrote: NetworkManager-0.9.4.0-9.git20120521.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/NetworkManager-0.9.4.0-9.git20120521.fc17 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/12 ------------------------------------------------------------------------ On 2012-05-21T17:17:37+00:00 Fedora wrote: NetworkManager-0.9.4-6.git20120521.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/NetworkManager-0.9.4-6.git20120521.fc16 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/13 ------------------------------------------------------------------------ On 2012-05-28T01:23:33+00:00 Fedora wrote: NetworkManager-0.9.4-6.git20120521.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/14 ------------------------------------------------------------------------ On 2012-05-29T10:28:42+00:00 Fedora wrote: NetworkManager-0.9.4.0-9.git20120521.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/996032/comments/15 ** Changed in: network-manager (Fedora) Status: Unknown => Fix Released ** Changed in: network-manager (Fedora) Importance: Unknown => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 Released Status in network-manager package in Fedora: Fix Released 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
