On 16 Sep 2024 14:46 -0400, from debianl...@videotron.ca (Frank McCormick): >> # systemctl restart networking > > I'll reboot and try that. Following a suggestion I found on the net I did > sudo /etc/init.d/networking restart and that **seems** to have restarted the > network, BUT browsers can't find any sites and Thunderbird reports failures > to connect. I think I am over my head here but could it be a DNS problem ??
That certainly seems plausible. Check your /etc/resolv.conf. Is it there? Is it sane? Also check /etc/nsswitch.conf, particularly the hosts: entry. The old-style sysvinit /etc/init.d scripts should be just wrappers around the corresponding systemctl commands if you are running systemd, which you almost certainly do unless you've gone out of your way to do otherwise. Confirm that you have IP (assuming IPv4 here; adjust as necessary if you are in an IPv6-only world): $ systemctl status networking $ ip sh a $ ip -N route $ sudo traceroute -In 8.8.8.8 $ host www.example.com (That last will likely fail to return anything useful if you have IP but not DNS, possibly as a result of a DHCP failure or a broken /etc/resolv.conf. A traceroute to Google's multicast public DNS resolver should get you _something_ out of your local network. -I is use ICMP which requires elevated privileges, hence sudo.) Particularly, look for your network interface having an IP address on the expected subnet from `ip sh a`, and look for a meaningful `default` route in the output of `ip -N route`. If you have an IP address in the 169.254.x.x range, then you have a DHCP issue. You mention that you did a system upgrade earlier in the day, which finished successfully. What exactly was updated then, and from what and to what? The most recent apt log might very well be instructive. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
