This is an Acer Aspire one laptop, with a 32 bit CPU and Debian 12.7. Whenever I install Linux on it, the Internet works for about one day. And when I boot it up the next day, it just stops working. This is the case for WiFi, Ethernet and USB tethering via Android.
After running networkctl it gave me this:
I can ping 8.8.8.8 in this state, but not gnu.org. I can't open websites in Firefox either.
Then I ran "sudo systemctl start systemd-networkd". The networkctl output changed but everything worked exactly as the above two images. Couldn't open websites still.
Yesterday everything was working perfectly
Edit: Thanks to @nanook@friendica.eskimo.com and @MyNameIsRichard@lemmy.ml I finally have internet access on my 12-year old e-waste!
What a weird question. Networkd works anywhere systemd works, why whould desktops be any different.
It’s the same as asking someone “why are you using systemd-boot instead of grub?” Because I like systemd boot better and it’s easier to configure. Same with networkd, configuration is stupid simple, I have installed it on my work machine even.
As for op: since you can manually ping ip addresses and the issue seems to be time-based, could it be that your machine is somehow not renegotiating a dhcp lease?
Well the machine's time is off by a few hours after I power it off for a night. So the time is incorrect right now. This might explain why it suddenly stops when I wake up and reopen it a day after installation. Should I manually set the correct time to fix it?
If the time is off by that much after being powered off, this tells me two things:
An incorrect clock can absolutely cause network issues, so I would bet that’s what is causing you trouble