You are not logged in.
My connection is driving me crazy.
It takes a very long time to load a webpage.
But if I connect through a VPN (I use Private Internet Access), then it takes a short time.
So it must be a misconfiguration on my part, not a problem of the ISP.
How can I diagnose the problem?
Offline
So it must be a misconfiguration on my part, not a problem of the ISP.
Not necessarily.
How can I diagnose the problem?
Browsers come with a bunch of debugging options. First they show what they’re doing or what they are waiting for in the bottom line. If that’s not helpful enough, hit F12 and have a look at the options there.
english is not my first language. If you find a mistake in this post, please mention it in your reply – this way I can learn. TIA
Offline
Bad DNS? IPv4 ./. IPv6?
Try to
dig google.comon and off VPN
Offline
Hello,
I'll try to explain my problem better.
With the VPN off, it doesn't happen always.
It happens sometimes.
So I need some tool that sort of monitor my connection to see what's happening.
I think it's useless I run commands when it works because that's not gonna diagnose what's happening when it doesn't work.
I'm away from home now. I'll try again next year when I come back.
Thanks a lot for your help.
Offline
I need some tool that sort of monitor my connection
Try tcpdump(1). Just don't ask me how to use it ![]()
Jin, Jîyan, Azadî
Offline
I think it's useless I run commands when it works because
… that would only illustrate the functional conditions what would then help to spot significant differences from the disfunctional condition ![]()
Post the output as well as also better "ip a; ip r" with the VPN enabled, the VPN disabled and things still working and the VPN disabled and the network malfunctioning.
Also post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fYou don't know what's wrong, we're only incrementally learning how/when things are wrong - the more data we have on the problem, the more likely we're going to pin it down.
@HoaS, by using wireshark instead ![]()
Offline