You are not logged in.
hello, i am having a strange problem with the network. after a while (~hours) some webpages (for example google.com and github.com) take forever to load, while other sites remain unaffected.
here is my investigation so far:
the network is a simple home setup, wan -> router (cheap tp-link one) -> host (wired, dhcp)
happens on different machines with similar arch installs, no issues with win7 (on the same machine) and osx
its not a dns issue (ping, dig, nslookup work fine)
it happens regardless of the http client (different browser, curl, even telnet)
tried turning off/on the interface with ip link, doesn't fix it
happens on stock and linux-ck kernel the same
ran strace on curl and telnet a couple times, in case of curl it hangs on a poll after the connect, telnet hangs on the connect
has anyone else ran into this?
thank you
Offline
I have seen something similar to this recently, only I had not researched quite as well as you did and I assumed I had a DNS problem (dig was equally non-responsive).
Here's one thing that I did on a whim that seemed to correct the problem. In /etc/resolv.conf I added the line:
options single-request
There was one other instance where I saw a similar problem. In the network, I had created a duplicate machine from a cloned image. It turned out that my original had a static IP assignment, so I did not have unique network addresses.
Offline
thanks for the suggestion, unfortunately doesn't help. like i said, its definately not a dns issue. forcing ipv4, enabling single-request, connecting thru the ip address instead of teh domain name, all the same.
the only thing that helps is a reboot, afaik.
Offline
Have you tried unloading and loading the network module?
Offline
Couldn't hurt to check the logs of your router if possible. It could be that something Arch is doing is causing the router to act up.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
thank you for the further suggestions
i have tried looking at the router logs, but nothing seems out of the ordinary, the hanging connections don't show up in the logs
i unloaded the module that provides the driver for the nic, but that didn't fix the problem
however, shortly after that i switched from dhcpcd to systemd-networkd. looks like that solved the problem, the system has been running for 30 hours since, without the issue coming back
i have absolutely no idea how can this be relevant tho, i tried releasing the ip and getting a new one (with dhcpcd), that didn't help. still, maybe of some use to someone :-)
Offline