Description of problem: NetworkManager reports the connection status as offline frequently even though the network is actually fine. This message is seen regularly in the journal: connectivity: (wlp3s0) timed out e.g. from this boot: Jul 24 08:59:51 river NetworkManager[1097]: <info> [1500883191.6940] connectivity: (wlp3s0) timed out Jul 24 10:34:51 river NetworkManager[1097]: <info> [1500888891.6923] connectivity: (wlp3s0) timed out Jul 24 12:34:51 river NetworkManager[1097]: <info> [1500896091.6937] connectivity: (wlp3s0) timed out After removing NetworkManager-config-connectivity-fedora, all is well. How can I debug this? Version-Release number of selected component (if applicable): How reproducible: NetworkManager-config-connectivity-fedora.noarch 1:1.8.2-1.fc26 Additional info: Didn't have this problem in Fedora 25.
I have the same issue even with ethernet connection (enp0s25).
Hi, can anybody please set 'level=TRACE' in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart the NetworkManager service and attach the journal log when the issue happens again? Thanks!
Created attachment 1307261 [details] NetworkManager timed out log NM report offline status at : Mon 2017-07-31 22:43:45 CEST adrien-pc NetworkManager[4810]: <info> [1501533825.2392] connectivity: (enp0s25) timed out
(In reply to Adrien Nayrat from comment #3) > Created attachment 1307261 [details] > NetworkManager timed out log > > NM report offline status at : > > Mon 2017-07-31 22:43:45 CEST adrien-pc NetworkManager[4810]: <info> > [1501533825.2392] connectivity: (enp0s25) timed out Hi, can you please try calling curl manually and paste the output of: curl --interface enp0s25 -o - -D - http://fedoraproject.org/static/hotspot.txt Thanks.
Hello, Here the result : curl --interface enp0s25 -o - -D - http://fedoraproject.org/static/hotspot.txt HTTP/1.1 200 OK Date: Thu, 03 Aug 2017 11:06:11 GMT Server: Apache/2.4.6 (Red Hat Enterprise Linux) Last-Modified: Wed, 10 Feb 2016 01:16:25 GMT ETag: "2-52b602ec4539d" Accept-Ranges: bytes Content-Length: 2 Cache-Control: must-revalidate Expires: Thu, 03 Aug 2017 11:06:11 GMT AppTime: D=152 AppServer: proxy04.fedoraproject.org Vary: User-Agent Content-Type: text/plain; charset=utf-8 OK%
Hello, How can we avoid networkManager to call http://fedoraproject.org/static/hotspot.txt? One of my colleague has the same issue since he changed his ISP (to Orange France), same as me. I supposed the issue is between Orange and Fedora'server. Thanks
(In reply to Adrien Nayrat from comment #6) > Hello, > How can we avoid networkManager to call > http://fedoraproject.org/static/hotspot.txt? > > One of my colleague has the same issue since he changed his ISP (to Orange > France), same as me. > > I supposed the issue is between Orange and Fedora'server. > > Thanks Hi Adrien, the connectivity check configuration snippet for Fedora is located in: /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf You can shadow it creating: /etc/NetworkManager/conf.d/20-connectivity-fedora.conf (if you cancel the original file, future updates may restore the file) You can put there a custom URL used for the check or just add an empty file. Be warned anyway that if you just mask the file with an empty config you will disable connectivity checking and also proxy detection.
I believe this may be related to bug 1387865 on f25. In that case I found it was sensitive to local router configuration - that might be consistent with a change of ISP if the ISP provided a different router or changed configuration. I am on f26 now, I still have both my routers and I can run tests with different configurations if that would be helpful. At this point I suspect the problem is in different IPv6 support by the two routers but I can't pin it down.
I think this bug is likely related to: https://bugzilla.gnome.org/show_bug.cgi?id=786432 Which actually turns out to be a bug in curl.
(In reply to Alan Conway from comment #8) > I believe this may be related to bug 1387865 on f25. In that case I found it > was sensitive to local router configuration - that might be consistent with > a change of ISP if the ISP provided a different router or changed > configuration. > > I am on f26 now, I still have both my routers and I can run tests with > different configurations if that would be helpful. At this point I suspect > the problem is in different IPv6 support by the two routers but I can't pin > it down. I take it back - I definitely am losing my Wifi connection, so the connectivity test is behaving correctly in reporting it.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.