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
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
Am 15.05.2018 um 14:39 schrieb Thomas Haller:
what does `ip link show` say?
Hi,
NO CARRIER. I did understand that NM is not able to handle this ?
[oppa@localhost ~]$ ip link show
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
Am 15.05.2018 um 13:33 schrieb Thomas Haller:
On Tue, 2018-05-15 at 12:24 +0200, Stephan Goldenberg wrote:
Am 14.05.2018 um 22:46 schrieb Thomas Haller:
On Mon, 2018-05-14 at 20:45 +0200, Stephan Goldenberg wrote:
It's a plain old cable based 1GBit/s connection. No WLAN, no
other
fancy
Am 14.05.2018 um 22:46 schrieb Thomas Haller:
On Mon, 2018-05-14 at 20:45 +0200, Stephan Goldenberg wrote:
It's a plain old cable based 1GBit/s connection. No WLAN, no other
fancy
network. What do you need to hunt this down ?
Hi,
what's the output of `nmcli device` and `nmcli connection
Hi,
I had this with Fedora 27, which made me move to systemd-networkd. But
that served SELinux alerts.
After freshly installing Fedora 28 all was fine. After suspend
NetworkManager was able to keep the internet connection. But then there
was an update for NetworkManager last friday. Since