no internet connection
It's just that after some time of use, the internet completely disappeared. What to do?
Solution:Jump to solution
Ok, here's another solution: open the file /etc/resolv.conf and in nameserver write the ip of the router, through which you can enter its panel. For keenetic it is 192.168.1.1. This, by the way, also appears in the guide I found, but I didn't notice that it is necessary to change something in this file too
27 Replies
The only thing that works is speedtest.
I finally managed to upload the log and log into Discord.
https://paste.centos.org/view/55418971
@Bazzite Maintainer
i might be wrong, but it looks like when your system came out of sleep mode, it failed to contact the DHCP server and get a list of DNS servers - as such it can no longer resolve any names
Why are other devices able to resolve?
Why has windows 11 always been able to?
And how long does it take for the system to wake up? Before that, I ran DD2 and was able to summon a pawn from the net. After quitting the game, there was no internet for about 20 minutes.
all i can tell you is that the log shows that it was unable to get a lease from the DHCP server, then the network manager saw your connection go up/down etc - id first look at verifying the connection from the device to the dhcp server - if its a cable, try replacing it
saying "why does it work on windows" repeatedly doesnt help you, or help others help you, in any way as it offers no additional information to what is causing the problem
And what additional information needed?
i'd start with verifying the connection between the device and the dhcp server
I can throw down the xray settings, show you what DNS is being used
personally, id start be verifying the non-software components involved - not just relying on "it works on other distros" - actaully check/replace the cable, verify the conenction between the device and the DHCP server is good and not flaky
Okay, I'll give it a try. It takes time. Thanks for the tip.
Okay, I replaced the cable and even hid it in a cable raceway. So far, there haven't been any internet problems, but I'll keep an eye on it for another day or two.
No, changing the cable didn't help
@Robbeh The bazzite seems to be very bad with DoH and DoT. It seems that if you select normal DNS servers in the router settings, the internet goes away for a shorter period of time
Ahahahahah, lol, it's not even a problem to connect to the internet, the computer basically loses connection with the router and it's not only inaccessible to the internet, but also to the local network
@Robbeh As soon as I googled the error that occurs when using the "ping" command, the solution appeared instantly. I had the same exact problem back in ubuntu 19. And yes, it is the bazzite settings that are to blame
it might be worth including the solution now that you have it - so it can help others if they come across the same issue?
Open the /etc/NetworkManager/NetworkManager.conf file and in the [main] section add the
dns=default line.
After that you should either reboot the PC or restart NetworkManager via systemctlgood times! 🙂
You may also have to write these commands:
It is also extremely important, if you also have windows, to turn off fast boot in it. I've read that windows hibernation can negatively affect the network card in linux
to be clear -- you can go through our entire github & containerfile. At no point is networkmanager touched.
To be honest, I don't really care what you touched on there and what you didn't. The fact of the matter is that the internet is not working well on your distro. And I don't care who is to blame - you, the developers of fedora or the developers of the fedora spin on which your distribution is based.
When I created this ticket I expected some help, because the distribution is atomic, I don't know what can be changed in it and what shouldn't. But in the end I helped myself
We can't help you with a problem we don't have and the fact that you landed on a solution of changing a config we don't touch means you'd have this problem on stock fedora and there's something going on specific to your end or your hardware
There's little we could have done
dns=default means forcing default DNS settings, which is the stock behavior that happens here
No custom DNS settings are enforced by us or the Fedora proejct
Yes, there is something going on on my hardware. For example, any other DNS servers that are not specified in the router settings are forbidden
Solution
Ok, here's another solution: open the file /etc/resolv.conf and in nameserver write the ip of the router, through which you can enter its panel. For keenetic it is 192.168.1.1. This, by the way, also appears in the guide I found, but I didn't notice that it is necessary to change something in this file too
Don't tell me that the whole problem was the systemd-resolved service and I went around the whole time, but didn't follow through with the solution
This is default behavior, your DNS server is your gateway. This setting should do nothing.
systemd-resolved is the standard DNS service for most distros, Fedora included.
I have now turned off this service and got an increase in the speed of loading steam. I'll check for stability tomorrow.
DNS has nothing to do with download speed
DNS is a service done once to get an IP address from a domain name and then never used again for the lifetime of that connection
But they matter to me. I can't have a device trying to give me its own dns. Everything must be resolved exclusively on the router
that is what is happening
again, default behavior
If I specify my DNS in the settings on my phone, I will lose interest too
What is the systemd-resolved service for then?
Now when I switch to desktop mode I don't even have time to see the steam update window, its tray icon appears immediately. I don't know what this service was actually responsible for, but so far it's only made me feel better
handling DNS
I'm gonna close this help thread then before something gets marked as a solution. For anyone that stumbles upon this:
Disabling systemd-resolved is a mistake, do not do it. Thank you.