You are not logged in.
My home internet was not working yesterday on any devices. Naturally, I tried a reboot of the router, but it didn't resolve the issue. I ended up resetting the router by pressing the small button on the back using a paperclip. This resolved the issue for all my devices except for on Linux. I dual boot Arch Linux and Windows on the same laptop, and the internet works just fine on Windows and any other device. When I connect to the network, it works for around ~5 seconds, then stops working for some time, then works again for ~5 seconds. See the ping below. The result is the same connecting wirelessly or using Ethernet. It works just fine on any other network and also worked just fine on my home network before the router reset. I have tried deleting the entries in /etc/NetworkManager/system-connections/ to no avail.
What would be my first steps for troubleshooting this? I've also tried pinging google's IP address directly, but that doesn't work either, so it doesn't seem like it's a DNS issue.
Running kernel 6.1.7.
PING google.com (142.250.180.110) 56(84) bytes of data.
64 bytes from mil04s42-in-f14.1e100.net (142.250.180.110): icmp_seq=1 ttl=108 time=27.3 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=2 ttl=108 time=27.1 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=3 ttl=108 time=26.7 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=4 ttl=108 time=27.2 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=5 ttl=108 time=27.0 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=6 ttl=108 time=26.6 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=7 ttl=108 time=26.5 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=8 ttl=108 time=26.8 ms
--- Around a 2 min pause here ---
64 bytes from mil04s42-in-f14.1e100.net (142.250.180.110): icmp_seq=207 ttl=108 time=1441 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=208 ttl=108 time=431 ms
64 bytes from mil04s42-in-f14.1e100.net (142.250.180.110): icmp_seq=209 ttl=108 time=26.7 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=210 ttl=108 time=26.8 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=211 ttl=108 time=26.7 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=212 ttl=108 time=27.1 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=213 ttl=108 time=26.6 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=214 ttl=108 time=26.8 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=215 ttl=108 time=26.4 ms
64 bytes from ber01s03-in-f14.1e100.net (142.250.180.110): icmp_seq=216 ttl=108 time=26.5 ms
Last edited by hawkis (2023-01-23 07:03:53)
Offline
I dual boot Arch Linux and Windows on the same laptop, and
… want to take a look at the 3rd link below.
When I connect to the network, it works for around ~5 seconds, then stops working for some time, then works again for ~5 seconds.
Output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
?
Offline
I dual boot Arch Linux and Windows on the same laptop, and
… want to take a look at the 3rd link below.
When I connect to the network, it works for around ~5 seconds, then stops working for some time, then works again for ~5 seconds.
Output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
?
Thanks. I've already disabled fast boot. I managed to fix the issue by restoring my system to an older snapshot. I have no idea what specifically fixed the issue, though. What do you think could have been the culprit?
Last edited by hawkis (2023-01-22 11:28:10)
Offline
I managed to fix the issue by restoring my system to an older snapshot.
No, you moved back in time.
As time progresses and if you repeat what you did, you'll hit the problem again.
This approach is usually not very helpful.
What do you think could have been the culprit?
Cosmic rays? Vengeful gods?
There's really no way of telling. When you hit the problem again, we'll take a look at the system to identify the cause.
Until then please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
No, you moved back in time.
As time progresses and if you repeat what you did, you'll hit the problem again.
This approach is usually not very helpful.
I agree. However, I immediately fully upgraded the system (like it was when it was not working prior) and it didn't break. I guess time will tell.
Until then please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Done.
Offline