You are not logged in.
Pages: 1
I noticed that lately while using any web browser(Konqueror or Firefox), when I type in some url and hit enter(or click a link), web browser just gets stuck for a few seconds. The same happens when I use ping. It takes like 10 seconds to see the first reponse from the server.
I have both Arch and Windows on my machine. There is no such problem on Windows.
Offline
Likely a slow/broken DNS resolution. Without knowing what you're actually using to connect to the network nor which configurations you've set up you might want to read: https://wiki.archlinux.org/index.php/Do … resolution
Offline
You need to tell a little bit more about your network configuration to get any help, as there is little information to go on from your post. How have you setup your network in Arch? Wifi or Ethernet? What other (outside computer) H/W?
It is still possible this a problem with your other H/W and/or your ISP, such as an ipv6 issue (this is just one example). Windows might not be using ipv6 at all (there are ways to disable it, in both Windows and any Linux distribution) and surprisingly many ISPs might have problems with IPV6 from time to time. In addition to your ISP, other sources of problems includes your router, modem etc.; better list your whole network setup here. But an easy way to test this is to use:
ping -4 www.google.com. It could also be a problem with your DNS configuration, and you can bypass your DNS by giving an IP address instead:
ping 8.8.8.8. If either one is quick to respond, you have narrowed down the possible causes. It is a good idea to also ping your router(s) and use traceroute.
Most probably it all boils down to differences between how your network has been configured in Windows and Linux. Also try commands such as ifconfig (in Arch) and ipconfig (in Windows, or whatever the equivalent is in Windows these days), compare and post the results here (however, it is a good idea to remove sensitive information such as your IP addresses and MAC addresses, but do note any differences you might have between the OSes).
Last edited by Wild Penguin (2020-07-14 09:09:10)
Offline
You need to tell a little bit more about your network configuration to get any help, as there is little information to go on from your post. How have you setup your network in Arch? Wifi or Ethernet? What other (outside computer) H/W?
It is still possible this a problem with your other H/W and/or your ISP, such as an ipv6 issue (this is just one example). Windows might not be using ipv6 at all (there are ways to disable it, in both Windows and any Linux distribution) and surprisingly many ISPs might have problems with IPV6 from time to time. In addition to your ISP, other sources of problems includes your router, modem etc.; better list your whole network setup here. But an easy way to test this is to use:
ping -4 www.google.com. It could also be a problem with your DNS configuration, and you can bypass your DNS by giving an IP address instead:
ping 8.8.8.8. If either one is quick to respond, you have narrowed down the possible causes. It is a good idea to also ping your router(s) and use traceroute.
Most probably it all boils down to differences between how your network has been configured in Windows and Linux. Also try commands such as ifconfig (in Arch) and ipconfig (in Windows, or whatever the equivalent is in Windows these days), compare and post the results here (however, it is a good idea to remove sensitive information such as your IP addresses and MAC addresses, but do note any differences you might have between the OSes).
Sorry, since I'm almost a complete noob in this, I will probably say some nonsense and will be slow.
I use wifi. I use NetworkManager to connect.
I rent a flat. A guy that owns this place has a router here.
I am able to ping my router without any delays.
ping 8.8.8.8 is fast, while
ping -4 google.com is slow.
I will work on comparing outputs of ifconfig/ipconfig on different OSes.
Offline
ping 8.8.8.8is fast, while
ping -4 google.comis slow.
See V1del's post. It's spot on.
Online
Sort of solved by starting and enabling systemd-resolved.
systemctl enable systemd-resolved
systemctl start systemd-resolvedWish I knew exactly what is going on. From what I can understand my DNS server had some issues. But by starting systemd-resolved, my machine now has it's own DNS server to which my requests are forwared to. The first time a pinged google.com after starting systemd-resolved it was slow. But after pinging google.com again it was fast(as it shoud be). So I suppose now my machine knows ip adress of google.com.
Does my guess make sense?
Offline
systemd-resolved is a local DNS cache, so subsequent queries (after the result was cached) will not suffer from the timeout.
Some popular public DNS servers:
1.1.1.1 - cloudflare
8.8.8.8 / 8.8.4.4 - google
9.9.9.9 - quad9/IBM
https://en.wikipedia.org/wiki/OpenDNS
Online
Pages: 1