Description of problem: With the wireless card set to "off" (through the network settings in Gnome3), while system is running basically idle, the system log is filled with the following messages appearing every 10 seconds: Nov 25 15:25:01 f20 NetworkManager[594]: <error> [1385411101.243236] [rdisc/nm-lndp-rdisc.c:194] send_rs(): (wlp3s0): cannot send router solicitation: -101. Nov 25 15:25:11 f20 NetworkManager[594]: <error> [1385411111.243805] [rdisc/nm-lndp-rdisc.c:194] send_rs(): (wlp3s0): cannot send router solicitation: -101. Nov 25 15:25:21 f20 NetworkManager[594]: <error> [1385411121.234358] [rdisc/nm-lndp-rdisc.c:194] send_rs(): (wlp3s0): cannot send router solicitation: -101. Nov 25 15:25:31 f20 NetworkManager[594]: <error> [1385411131.236125] [rdisc/nm-lndp-rdisc.c:194] send_rs(): (wlp3s0): cannot send router solicitation: -101. Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-18.git20131003.fc20.x86_64 kernel-3.11.8-300.fc20.x86_64 My wireless network card: Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) How reproducible: All the time. Steps to Reproduce: 1.Boot system 2.Fire up 'journalctl -f' 3.Watch the stream of error messages Actual results: Repeated messages of: Nov 25 15:25:31 f20 NetworkManager[594]: <error> [1385411131.236125] [rdisc/nm-lndp-rdisc.c:194] send_rs(): (wlp3s0): cannot send router solicitation: -101. Expected results: Relative silence. Additional info:
what does "nmcli dev" show?
nmcli dev: DEVICE TYPE STATE em1 ethernet connected wlp3s0 wifi unavailable lo loopback unmanaged virbr0-nic tap unmanaged As I went to get the requested info, I checked the 'journalctl -f' output, and it no longer prints those messages every few seconds. Looking at the journalctl history, the messages stopped after a reboot on Nov 26th. The yum log shows NetworkManager was updated: Nov 26 11:17:52 Updated: 1:NetworkManager-glib-0.9.9.0-19.git20131003.fc20.x86_64 I suppose this can be closed now.
Don't close ... I still have this: Jan 09 10:23:00 jormungand.esat.kuleuven.be NetworkManager[601]: <error> [1389259380.722520] [rdisc/nm-lndp-rdisc.c:221] send_rs(): (wlp3s0): cannot send router solicitation: -101. Jan 09 10:23:10 jormungand.esat.kuleuven.be NetworkManager[601]: <error> [1389259390.721455] [rdisc/nm-lndp-rdisc.c:221] send_rs(): (wlp3s0): cannot send router solicitation: -101. Jan 09 10:23:20 jormungand.esat.kuleuven.be NetworkManager[601]: <error> [1389259400.724287] [rdisc/nm-lndp-rdisc.c:221] send_rs(): (wlp3s0): cannot send router solicitation: -101. Every 10 seconds... nmcli dev: DEVICE TYPE STATE em1 ethernet connected wlp3s0 wifi connected lo loopback unmanaged IPV6 turned off on the Wireless. So I cannot see why it should send out router solicitations... This might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1010540 although the error is '-99' there, why we have '-101'.
(In reply to Bert DeKnuydt from comment #3) > Don't close ... > > I still have this: > > […] > > Every 10 seconds... Same here. > This might be a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1010540 > although the error is '-99' there, why we have '-101'. Well, according to e.g. http://www-numi.fnal.gov/offline_software/srt_public_context/WebDocs/Errors/unix_system_errors.html : #define EADDRNOTAVAIL 99 /* Cannot assign requested address */ #define ENETUNREACH 101 /* Network is unreachable */ So I guess the issue is different ? BTW : NetworkManager-0.9.9.0-23.git20131003.fc20.x86_64 kernel-3.12.6-300.fc20.x86_64 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Same problem here. Kernel: 3.16.3-200.fc20.i686+PAE NetworkManager-0.9.9.0-45.git20131003.fc20.i686 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM (rev 04) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.