On 25/01/2025 14:17, Thomas Anderson wrote:
$ nmcli connection show
IP4.ADDRESS[1]: 192.168.1.6/24
IP4.GATEWAY: 192.168.1.1
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh =
0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh =
192.168.1.1, mt = 100
IP4.DNS[1]: 192.168.1.8
Is it the same before NetworkManager restart when routing is incorrect?
(Save output to files and compare them.) It was not Debian bullseye, but
even earlier I definitely used static configuration as a workaround in
rare cases of ISP DHCP server failures. However it was not automatic
connection at the boot time. Have you tried to search for NetworkManager
bugs (I consider it unlikely since RedHat recommends it even on servers)?
On 24/01/2025 18:35, Thomas Anderson wrote:
I have not found an error messages
Is there a chance that you added some init script earlier?
Have you grepped syslog files for namely for errors or read other early
messages as well?
Since some people on this list consider syslog as the only source of the
truth, I believe, it is better to ask it explicitly if you have inspected
journalctl -b -u NetworkManager
and for the case of interference with some other tool
journalctl -b
