Hide Forgot
Fedora 24 pre-release; NetworkManager-1.2.0-0.8.rc1.fc24.x86_64 -- System is connected to a router via Ethernet cable, using static DHCP for addressing. At the time, system was also running a VPN connection over wired connection. Router was reset (powered off and on), but after this the wired connection is not restored, although the GNOME Shell icon for wired connection appears as if it was.
Created attachment 1146941 [details] journal output from reconnection attempt
Created attachment 1146942 [details] journal output from manually dropping and starting wired connection from GNOME Shell control
Do you remember (or have the chance to find out) if after the failed reconnection attempt the interface had IPv6 addresses and route configured? Because it seems that NM correctly restarts DHCPv4 after link goes up at 11:32:24 and, after a second, also starts DHCPv6 (presumably because a router advertisement was received). But DHCP servers are not available yet (since the router is still booting?) and so IPv4 configuration fails; which doesn't cause the failure of connection because ipv4.may-fail is set to yes and IPv6 auto-configuration succeeded. But in normal logs there isn't enough information to verify if this is what really happened. Could you set level=DEBUG in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart the service, reproduce the issue and attach new logs? Thanks!
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.