Hide Forgot
Description of problem: NetworkManager is flooding the system log with Policy messages when IpV6 settings are set to Automatic. Version-Release number of selected component (if applicable): NetworkManager-0.9.4-1.git20120328.fc16.x86_64 How reproducible: Always. Steps to Reproduce: 1. Set IPv6 settings to Automatic 2. Connect 3. Watch system log Actual results: Apr 2 01:02:54 localhost dnsmasq[1380]: reading /etc/resolv.conf Apr 2 01:02:54 localhost dnsmasq[1380]: using nameserver 74.82.42.42#53 Apr 2 01:02:54 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv4 routing and DNS. Apr 2 01:02:54 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv6 routing and DNS. Apr 2 01:02:56 localhost dnsmasq[1380]: reading /etc/resolv.conf Apr 2 01:02:56 localhost dnsmasq[1380]: using nameserver 74.82.42.42#53 Apr 2 01:02:56 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv4 routing and DNS. Apr 2 01:02:56 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv6 routing and DNS. Apr 2 01:02:58 localhost dnsmasq[1380]: reading /etc/resolv.conf Apr 2 01:02:58 localhost dnsmasq[1380]: using nameserver 74.82.42.42#53 Apr 2 01:02:58 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv4 routing and DNS. Apr 2 01:02:58 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv6 routing and DNS. Apr 2 01:03:00 localhost dnsmasq[1380]: reading /etc/resolv.conf Apr 2 01:03:00 localhost dnsmasq[1380]: using nameserver 74.82.42.42#53 Apr 2 01:03:00 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv4 routing and DNS. Apr 2 01:03:00 localhost NetworkManager[12549]: <info> Policy set 'halberd' (wlan0) as default for IPv6 routing and DNS. Expected results: All is silent Additional info: As with the other IPv6-related NM bugs, setting it to Ignore makes the messages not happen.
Hello, I have the same issue. I solved this problem by disabling the IPv6 configuration. I am using the Network-Manager version 0.9.4.0 in my Debian Sid.
I have the same issue. I have noticed opening a new tab in Google Chrome can trigger these messages. I don't consider switching off IPv6 to be a solution, as that is like saying covering up the engine fault warning light in a car fixes the problem with the engine.
So, this probably indicates that your router is sending out IPv6 Router Announcements every 2 seconds, which is ridiculous, so you may want to investigate that and see. But anyway, we're working on fixing up NM's behavior here, so that when nothing changes between RAs, it doesn't log anything.
Dan, I'm using OpenWRT on my router, and it's dynamically generated radvd configuration (/var/etc/radvd.conf) does not change the RA intervals, so they'd be the defaults of approximately once every 3 to 10 minutes. (That's not to say there isn't broken IPv6 CPE out there that sends RAs too often - http://www.users.on.net/~markachy/resi_ipv6_cpe.pdf)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #3) > But anyway, we're working on fixing up NM's > behavior here, so that when nothing changes between RAs, it doesn't log > anything. this happened. In F18, NM shouldn't log those things if they haven't changed.