Re: F28 - Update reintroduced missing connection after suspend
On Wed, 2018-05-16 at 10:58 +0200, Stephan Goldenberg wrote: > Am 16.05.2018 um 09:40 schrieb Stephan Goldenberg: > > > I'm going to switch to networkd now and it will work. > > Hi, > > I made the move and network is just fine, even after resume from > suspend. The mislabeling of /etc/resolv.conf seems to be fixed too. > So I > stick with networkd. Somehow NetworkManager can't handle my system > but > networkd can. > > Gnome thinks the network is broken because it needs NetworkManager > for > some reason but I have no problems with that. I just care about the > network being up and running after boot and after resume. > > Regards, > Stephan > Hi, if the link has no carrier, then that is not related to NetworkManager. It is likely a kernel issue or the switch to which your computer is connected. It is not clear, why networkd would work with cable (seemingly) unplugged. But great if it works for you!! Clearly Gnome would not know that you are connected to a network, because networkd does not expose a meaningful D-Bus API that Gnome could use. It should however work just fine without it (some features missing). If not, that would be a bug (in Gnome). best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F28 - Update reintroduced missing connection after suspend
Am 16.05.2018 um 09:40 schrieb Stephan Goldenberg: I'm going to switch to networkd now and it will work. Hi, I made the move and network is just fine, even after resume from suspend. The mislabeling of /etc/resolv.conf seems to be fixed too. So I stick with networkd. Somehow NetworkManager can't handle my system but networkd can. Gnome thinks the network is broken because it needs NetworkManager for some reason but I have no problems with that. I just care about the network being up and running after boot and after resume. Regards, Stephan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F28 - Update reintroduced missing connection after suspend
Am 15.05.2018 um 19:53 schrieb Thomas Haller: NO CARRIER. I did understand that NM is not able to handle this ? Hi, NO-CARRIER has nothing to do with NetworkManager. Kernel thinks, that the cable is not plugged in. Consequently, NetworkManager does not autoactivate the profile. Even if it would, DHCP could not complete, because there is no cable (or at least, kernel thinks so). You need to solve that problem. networkd also won't be able to do DHCP on such a link. Maybe the switch to which you are connected, disables the link... best, Thomas Hi, that exactly is the point. This has to do with NetworkManager or its configuration. Or maybe something in the suspend/resume cycle changed. The PC is connected to a Fritzbox. Nothing has changed regarding the hardware or its configuration. No firmware update, no nothing. I'm going to switch to networkd now and it will work. Regards, Stephan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
