Linux

48698 readers

1270 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

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

submitted 1 month ago* (last edited 1 month ago) by maliciousonion@lemmy.ml to c/linux@lemmy.ml

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 @nanook@friendica.eskimo.com and @MyNameIsRichard@lemmy.ml I finally have internet access on my 12-year old e-waste!

you are viewing a single comment's thread
view the rest of the comments

[–] nanook@friendica.eskimo.com 20 points 1 month ago (1 children)

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

[–] maliciousonion@lemmy.ml 1 points 1 month ago (2 children)

What can I do to fix the problem here?

[–] MyNameIsRichard@lemmy.ml 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.

[–] maliciousonion@lemmy.ml 9 points 1 month ago

Tysm, @MyNameIsRichard@lemmy.ml and @nanook@friendica.eskimo.com.

[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.

[–] nanook@friendica.eskimo.com 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.