On 2020-03-06 22:11, Tom Horsley wrote:
This morning I installed a lot of updates on my machine
at work which is setup with "network", NOT NetworkManager.
I rebooted, and had no network. DHCP not giving me an IP,
ypbind not talking, etc.
After much flailing around, I found the socket
systemd-networkd.socket
enabled (I have no idea if it has always been enabled),
so I disabled it, rebooted again, and all networking
was once again functioning perfectly.
Just thought someone else might run into this and could
use my solution.
FWIW, all of my fully updated F31 systems have systemd-networkd.socket disabled. The
only
recent network related update on my systems was for NetworkManager-l2tp. And, also FWIW,
I've never experienced a update enabling a service or socket.
--
The key to getting good answers is to ask good questions.