On Tue, May 27, 2025 at 19:06:22 -0700, accipiter wrote: > 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.
Aha! See, when you actually post *details*, we can start to make some progress. An IP address in the 169.254.x.y network is self-assigned by an interface when it wants to get a DHCP address, but is unable to get a response from a DHCP server. So, you have two things going on here: * The interface is configured to try DHCP. * The DHCP client is not getting a response. Other people may be able to offer additional insights. This isn't a problem I've experienced first-hand. I only know about it from others on this mailing list.
