On Wed, 28 May 2025, accipiter wrote: > On 5/27/25 7:40 PM, Titus Newswanger wrote: >> >> On 5/26/25 14:20, accipiter wrote: >>> 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. It is this erroneous connection entry that >>> appears connected to the eth0 device. >> I had a similar problem just yesterday. Could not remember what all I >> did to it in the past year, I do know I had majorly modified the >> networking. I completely redid the network configs but still had the ip >> address going back to the previous setup. Gave up on it and wiped the >> hard drive and reinstalled Debian 12. Now everything works great. >> > > It may come to that. Hate to do it, there are some old bits that I've > been using to interact with some specialized hardware - it's the whole > reason why I keep this 14-yo machine. I can *probably* reconstruct but > there's a finite probability that I'll miss something that I didn't > backup. Without a network connection it all gets harder. > > It seems likely that there's some detritus from one or more prior > versions of Debian that's screwing things up, but I'm not knowledgeable > enough to figure it out. > > This morning's reboot - networking reports via ifconfig and nmcli look > better (right IP#, gateway, /etc/resolv.conf set properly once I use > nmcli to force the device to connect, but can't ping the gateway nor > does pinging this system from other host get any reply. > > Thanks to everyone for your suggestions!! I'll make a few more attempts > before the total rebuild but I'm not optimistic. > > -F >
i've been watching this thread and i can't figure it out why is using network manager so important
