You are not logged in.
Pages: 1
Hi everyone!
I have problem with internet...
Every time when I try to open a site, there is delay before connecting
Downloading a package with pacman is the same story
My internet speed is good but the delay before downloading anything is ANNOYING
Please help me...
Offline
Sounds like a DNS problem. Once a download starts, is the download speed itself normal?
Did you, per chance, install and configure Avahi?
Wired? Wireless? Is this on a particular network or all networks?
Is this new behavior, or has it never been correct?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Also, how much delay (roughly, in seconds) - 1, 5, 25, …?
Next to avahi issues, please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
resolvectl status
dig heise.de # because you probably never visited this domain, so it's not cached
dig @8.8.8.8 heise.de # 8.8.8.8 is googles DNS serverOffline
Sounds like a DNS problem. Once a download starts, is the download speed itself normal?
Did you, per chance, install and configure Avahi?
Wired? Wireless? Is this on a particular network or all networks?
Is this new behavior, or has it never been correct?
Yes, download speed is normal
never used Avahi, instead installed and configured Apache
i tried both wired and wireless network and issue is on all networks
It is new behavior, i recently reinstalled archlinux......
Offline
Also, how much delay (roughly, in seconds) - 1, 5, 25, …?
Next to avahi issues, please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f resolvectl status dig heise.de # because you probably never visited this domain, so it's not cached dig @8.8.8.8 heise.de # 8.8.8.8 is googles DNS server
I would say, <5sec. delay. The output:
resolvectl status
dig heise.de # because you probably never visited this domain, so it's not cached
dig @8.8.8.8 heise.de # 8.8.8.8 is googles DNS server
bluetooth.service | bluetooth.target.wants
dbus-org.bluez.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
dirmngr.socket | sockets.target.wants
display-manager.service | system
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
httpd.service | multi-user.target.wants
mariadb.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
NetworkManager.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
sshd.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
vboxservice.service | multi-user.target.wants
xdg-user-dirs-update.service | default.target.wants
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
bash: dig: command not found
bash: dig: command not foundOffline
bash: dig: command not foundhttps://archlinux.org/packages/extra/x86_64/bind/
drill google.com
drill @8.8.8.8 google.com
nslookup google.comhttpd.service | multi-user.target.wants
Every time when I try to open a site
including or exclusive to the local domain?
Offline
bluetooth.service | bluetooth.target.wants
dbus-org.bluez.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
dirmngr.socket | sockets.target.wants
display-manager.service | system
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
httpd.service | multi-user.target.wants
mariadb.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
NetworkManager.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
sshd.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
vboxservice.service | multi-user.target.wants
xdg-user-dirs-update.service | default.target.wants
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
; <<>> DiG 9.18.5 <<>> heise.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20401
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;heise.de. IN A
;; ANSWER SECTION:
heise.de. 86400 IN A 193.99.144.80
;; Query time: 100 msec
;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
;; WHEN: Fri Jul 23 22:56:49 +02 2022
;; MSG SIZE rcvd: 53
; <<>> DiG 9.18.5 <<>> @8.8.8.8 heise.de
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21844
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;heise.de. IN A
;; ANSWER SECTION:
heise.de. 20917 IN A 193.99.144.80
;; Query time: 70 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Fri Jul 23 22:56:49 +02 2022
;; MSG SIZE rcvd: 53The delay is like this:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=104 time=222 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=104 time=878 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=104 time=75.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=104 time=81.7 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=104 time=78.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=104 time=80.1 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=104 time=75.2 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=104 time=82.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=104 time=76.3 msWhat does mean
multi-user.target.wants
?
including or exclusive to the local domain?
Local domain? Sorry, I honestly don't know much about this stuff
Offline
So you by default get a 100ms response from your gateway (router and likely forwarding the DNS configured there) and a 70ms response from google (8.8.8.8) - neither is super-fast but in line w/ your pings.
From the ping results, the generally high latency is however not the problem - the first two responses are massive outliers w/ ~3 and ~10 times the average latency.
What's the output for
ping -c5 _gateway and do you also get the initial delay when running two pings in parallel?
(ie. open two terminals, run "ping 8.8.8.8" in one and once the response there is down to ~80ms, run "ping 1.1.1.1" in the other terminal and pay attention to the initial response time)
Offline
So you by default get a 100ms response from your gateway (router and likely forwarding the DNS configured there) and a 70ms response from google (8.8.8.8) - neither is super-fast but in line w/ your pings.
From the ping results, the generally high latency is however not the problem - the first two responses are massive outliers w/ ~3 and ~10 times the average latency.What's the output for
ping -c5 _gatewayand do you also get the initial delay when running two pings in parallel?
(ie. open two terminals, run "ping 8.8.8.8" in one and once the response there is down to ~80ms, run "ping 1.1.1.1" in the other terminal and pay attention to the initial response time)
ING _gateway(fe80::1%wlp0s20f3) 56 data bytes
64 bytes from fe80::1%wlp0s20f3 (fe80::1%wlp0s20f3): icmp_seq=1 ttl=64 time=225 ms
64 bytes from fe80::1%wlp0s20f3 (fe80::1%wlp0s20f3): icmp_seq=2 ttl=64 time=44.4 ms
64 bytes from fe80::1%wlp0s20f3 (fe80::1%wlp0s20f3): icmp_seq=3 ttl=64 time=1.20 ms
64 bytes from fe80::1%wlp0s20f3 (fe80::1%wlp0s20f3): icmp_seq=4 ttl=64 time=4.60 ms
64 bytes from fe80::1%wlp0s20f3: icmp_seq=5 ttl=64 time=1.22 ms
--- _gateway ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 20494ms
rtt min/avg/max/mdev = 1.195/55.263/224.874/86.367 msalso, i dont get delay when running two pings
Offline
So on a much lower scale you get the same initial delay from the gateway.
I'd normally blame power saving, but that doesn't fit "wired and wireless", thee first two pings instead of only the first one and also absolutely not the vastly different initial delay when pinging the gateway instead of some IP.
…
Do you have the opportunity to test the system against a different router/AP (office, starbucks, …)?
As a mitigation strategy:
if you keep "ping -q _gateway" running in some terminal, does the original problem ("Every time when I try to open a site, there is delay before connecting") disappear?
Sidebar:
never used Avahi, instead installed and configured Apache
Humm?
https://wiki.archlinux.org/title/Avahi is a service discovery protocol and Apache is a webserver (that's why I asked for your local domain) - they have no relation an if you only installed apache because it sounds(?) like avahi, you should probably get rid of apache again.
Offline
And my only concern of Avahi is that improper removal of it can leave a broken system that tries something that no longer exists first. If it was never installed, the concern is moot.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Hi,
I seem to have the same problem, but it happens only on the university wifi. Also, the problem wasn't there from the start, it only began some weeks ago.
Is there any solution?
Last edited by Achille0072 (2023-11-14 09:03:38)
Offline
Probably not, the thread is 18 months old and the limited condition sounds like it's probably a different issue.
=> Open a new thread and there please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
# the following commands only make sense on the affected network
ip a
ip r
dig google.com # bind packageOffline
Pages: 1