this post was submitted on 02 Nov 2024

27 points (93.5% liked)

Linux

48652 readers

1025 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

[SOLVED] Internet strangely stops working after one day of installation. (lemmy.ml)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

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 @[email protected] and @[email protected] I finally have internet access on my 12-year old e-waste!

all 12 comments

sorted by: hot top controversial new old

[–] [email protected] 16 points 1 month ago

0 days since it was DNS

[–] [email protected] 3 points 1 month ago

If worse comes to worse, you can always just remove the symlink of /etc/resolv.conf which presently will point to something in /run/systemd, and replace it with a static file with known good name servers in it. You'll lose having a DNS cache but at least your machine will function.

[–] [email protected] 20 points 1 month ago (1 children)

Fact that you can still ping but not resolve means your name servers aren't set right.

[–] [email protected] 1 points 1 month ago (2 children)

What can I do to fix the problem here?

[–] [email protected] 10 points 1 month ago* (last edited 1 month ago) (1 children)

Update /etc/systemd/resolved.conf and add some DNS servers (in this example, 1.1.1.1 is CloudFlare, and 8.8.8.8 and 8.8.4.4 are Google but you can use your preferred DNS servers.)

[Resolve]
DNS=1.1.1.1 8.8.8.8
FallbackDNS=8.8.4.4

Restart system resolved:

service systemd-resolved restart

Run resolvectl status (or systemd-resolve --status in older versions of systemd) to see if the settings took.

If they don't take after a reboot, there's something else going on.

[–] [email protected] 9 points 1 month ago

Tysm, @[email protected] and @[email protected].

[Resolve]
DNS=1.1.1.1 8.8.8.8
FallbackDNS=8.8.4.4

I added this to the file /etc/resolv.conf and it's working again.

[–] [email protected] 4 points 1 month ago

@maliciousonion You can go into network manager and specify different working name servers, you can cat /etc/resolv.conf to make sure it is sane.

[–] [email protected] -3 points 1 month ago* (last edited 1 month ago) (1 children)

Why are you using networkd instead of networkmanager on a desktop? The two don't work together.

Anyway, it looks like a DNS problem. You can manually specify DNS servers (like 8.8.8.8, 8.8.4.4) in whatever network management you're using.

Alternatively you can edit ~~/etc/hosts~~ (I meant /etc/resolv.conf obviously) and then make it immutable (chattr +i /etc/hosts) to prevent changes.

[–] [email protected] 8 points 1 month ago* (last edited 1 month ago) (2 children)

Why are you using networkd instead of networkmanager on a desktop?

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?

[–] [email protected] 2 points 1 month ago (1 children)

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?

[–] [email protected] 3 points 1 month ago

If the time is off by that much after being powered off, this tells me two things:

Your RTC battery is very likely dead. Should be simple to replace, it would be on the motherboard but then again accessing it might be a little tricky on a laptop
NTP is probably not set up, or set up incorrectly. It should automatically sync the time on boot

An incorrect clock can absolutely cause network issues, so I would bet that’s what is causing you trouble