On 5/26/25 7:40 PM, Max Nikulin wrote:
On 27/05/2025 02:20, accipiter wrote:
nmcli c edit eth0
[...]
Attempting to delete/remove the connection entry with the wrong data
simply caused the defective connection entry to be replicated, only
now with yet another UUID.
Is there a chance that NetworkManager is under control of netplan.io in
your case?
Commands from https://wiki.debian.org/NetworkManager#Troubleshooting
might help to figure out what goes wrong in your case.
This is weird.
Looking at the Debian troubleshooting recommendations (thanks for the
reference!) - I started looking at the journalctl -b output. To my
surprise, there were some lines from dhcpcd . What??? So I disabled
that with systemctl - then retried the nmcli edit process.
At first it didn't seem to do any good, mis-replicating the eth0
connection when I killed that particular eth0 using its UUID. But then
I tried killing *both* eth0 connections, then trying to re-edit / create
the eth0 connection - and I was left with just a single connection!!
Restarting the networking (/etc/init.d/networking restart) *seemed* to
have an initially correct setup as ifconfig showed the right IP
addressing. But nmcli showed 2 addresses - the manual one that I
wanted, and additionally 169.254.220.204 and wrong gateway/routing. And
I couldn't ping my gateway.
Looking once more using *nmcli c show eth0* showed the right settings
for ipv4 parameters, but also had IP4 parameters with the 169.254...
crap. And at least my initial attempt failed when I tried to delete
these (capitalized) IP4 and GENERAL parameters.
Maybe I'm closer????
Thanks all!!
-F
