[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: networking.service: start operation timed out




On 27/8/22 7:55 pm, Curt wrote:
On 2022-08-27, Jeremy Ardley <jeremy@ardley.org> wrote:
I'd appreciate any suggestions about how to diagnose or cure the
problem.  I have set VERBOSE=yes in /etc/default/networking

First of all ensure NetworkManager is really dead.
Your advice and the advice of Andrew M.A. Cater appear
to be antithetical.

This is only an observation and not a criticism of any kind.

Maybe it's not a useful observation, though. I don't know.



My experience with linux networking has a history of banging my head against poorly explained, often buggy networking configurations.

I was sort of O.K. with the /etc/network/interfaces approach and could manage simple networks more or less reliably.

Then NetworkManager intruded and I could see for very simple uses it more or less worked and was perhaps easier for newbies. NM worked in addition to the /etc/network/interfaces.

My problems really came about when I started trying to use NetworkManager and a bunch of add-on utilities to add IPv6 delegation to my debian router. It became obvious NM was not my friend and did a lot of things that were not really explicable. My networking was not consistent or reliable.

I took a deep breath and dived into systemd-networkd and immediately found many people did not trust systemd-netword and systemnd. Nevertheless. I read the manual many times and I could get networkd to do everything I wanted in a predictable manner. I did have to go through eradicating NetworkManager and removing some of the add-ons such as radvd. I was also using isc-dhcp client and it was buggy as well. It's now deprecated. Going to systemd-networkd removed that as one of several sources of problems.


So from my point of view: networkd pretty good. NetworkManager and friends - nah!

The only thing I did do out of the ordinary was disable systemd-resolved which is still problematic. I replaced it with bind as a forwarder and reconfigured the resolve mechanism.

To make up for my going to the dark side with networkd I set up one of my servers with Devuan (actually it was Armbian and I did a risky but successful in-place conversion). Networking on the devuan system is straight forward (though they still allow NetworkManager). And the lack of systemd makes it seem familiar and easy to use)

Getting back to the OP. I recall he was complaining about NetworkManager still appearing in the logs. I gave him advice to make absolutely sure it couldn't be started by some obscure systemd process.

I still don't really trust systemd, but I'm quite happy with the subset systemd-networkd.


--
Jeremy

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: