Connection drop sometimes

hully · 2023-11-18 09:57:10

Here is the problem.

I use Firefox, and my internet usage is mostly web browsing.

Sometimes, when I connect to a website, it takes a long time, and then says that the page is unavailable. Then when I reload, it works. Or sometimes it takes a long time and then it connects.

Normally, it connects instantly.

Now this can be a problem of Firefox, of my configuration (drivers, NetworkManager or whatever), or the ISP.

I conjecture it's a problem of the ISP side, because when this happens the NetworkManager applet shows a "Limited connectivity" warning.

But I need to isolate the problem and log exactly when it happens and what is happening exactly (failure to resolve DNS names? failure to connect at all?).

Because if I call my ISP, it tells me to "do a speed test", and make me do the "Speedtest by Ookla".

The problem is that, it either doesn't work (don't connect at all), or work very well.

How can I monitor my connection and have detailed log of what's happening?

seth · 2023-11-18 13:36:01

You should first and foremost check the system journal - NM is extremely chatty about what happens.

While FF doesn't work™, check

ip a
ip r
dig google.com
dig @8.8.8.8 google.com
ping -c8 _gateway # LAN
ping -c8 8.8.8.8 # IP
ping -c8 google.com # domain via nslookup

And for FF specifically, see https://wiki.archlinux.org/title/Firefox/Privacy#Disable/enforce_'Trusted_Recursive_Resolver' and https://wiki.archlinux.org/title/Firefo … over_HTTPS and what's configured on your side.

hully · 2023-11-18 15:14:52

Here is the output of `journalctl --boot --reverse --unit=NetworkManager --since 2023-11-18 --until now > jrn.log`, with personal information abridged.

it doesn't show anything strange also because the last entry is from hours ago:

Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7494] dhcp6 (wlan0): state changed new lease
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7466] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7465] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7465] dhcp6 (wlan0): state changed no lease
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7465] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7465] dhcp6 (wlan0): canceled DHCP transaction
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7464] device (wlan0): ip:dhcp6: restarting
Nov 18 12:51:43 HOSTNAME NetworkManager[964]: <info>  [1700308303.7459] device (wlan0): supplicant interface state: 4way_handshake -> completed
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5440] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5440] device (wlan0): supplicant interface state: associated -> 4way_handshake
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5252] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5252] device (wlan0): supplicant interface state: associating -> associated
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5067] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.5066] device (wlan0): supplicant interface state: authenticating -> associating
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.4807] device (p2p-dev-wlan0): supplicant management interface state: completed -> authenticating
Nov 18 12:51:42 HOSTNAME NetworkManager[964]: <info>  [1700308302.4807] device (wlan0): supplicant interface state: completed -> authenticating
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3439] dhcp6 (wlan0): state changed new lease
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3402] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3400] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3399] dhcp6 (wlan0): state changed no lease
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3399] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3399] dhcp6 (wlan0): canceled DHCP transaction
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3398] device (wlan0): ip:dhcp6: restarting
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.3389] device (wlan0): supplicant interface state: 4way_handshake -> completed
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.2358] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Nov 18 12:46:40 HOSTNAME NetworkManager[964]: <info>  [1700308000.2357] device (wlan0): supplicant interface state: associated -> 4way_handshake
Nov 18 12:46:37 HOSTNAME NetworkManager[964]: <info>  [1700307997.0169] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Nov 18 12:46:37 HOSTNAME NetworkManager[964]: <info>  [1700307997.0168] device (wlan0): supplicant interface state: associating -> associated
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.9974] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.9974] device (wlan0): supplicant interface state: authenticating -> associating
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.9710] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.9710] device (wlan0): supplicant interface state: scanning -> authenticating
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.8348] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.8347] device (wlan0): supplicant interface state: disconnected -> scanning
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.7536] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.7535] device (wlan0): supplicant interface state: completed -> disconnected
Nov 18 11:31:06 HOSTNAME NetworkManager[964]: <info>  [1700303466.9477] audit: op="statistics" interface="wlan0" ifindex=3 args="2000" pid=3394 uid=1000 result="success"
Nov 18 11:27:51 HOSTNAME NetworkManager[964]: <info>  [1700303271.1231] dhcp6 (wlan0): state changed new lease
Nov 18 11:27:51 HOSTNAME NetworkManager[964]: <warn>  [1700303271.1221] dns-sd-resolved[1c20cad151c02bd6]: send-updates SetLinkDNS@3 failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid DNS server address
Nov 18 11:27:51 HOSTNAME NetworkManager[964]: <info>  [1700303271.1210] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.8279] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.4639] device (wlan0): Activation: successful, device activated.
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.4398] manager: NetworkManager state is now CONNECTED_SITE
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.4397] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.4396] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.4072] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <warn>  [1700303269.4071] dns-sd-resolved[1c20cad151c02bd6]: send-updates SetLinkDNS@3 failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid DNS server address
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.3416] policy: set 'NETWORKSSID' (wlan0) as default for IPv4 routing and DNS
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.3413] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.3413] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.3413] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NETWORKSSID"
Nov 18 11:27:49 HOSTNAME NetworkManager[964]: <info>  [1700303269.3413] device (wlan0): supplicant interface state: 4way_handshake -> completed
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2678] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2677] device (wlan0): supplicant interface state: associated -> 4way_handshake
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2470] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2469] device (wlan0): supplicant interface state: associating -> associated
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2274] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.2273] device (wlan0): supplicant interface state: authenticating -> associating
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1733] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1732] device (wlan0): supplicant interface state: disconnected -> authenticating
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1553] Config: added 'psk' value '<hidden>'
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1553] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1553] Config: added 'bgscan' value 'simple:30:-65:300'
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1552] Config: added 'scan_ssid' value '1'
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1552] Config: added 'ssid' value 'NETWORKSSID'
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1552] device (wlan0): Activation: (wifi) connection 'NETWORKSSID' has security, and secrets exist.  No new secrets needed.
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1549] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1546] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1528] sup-iface[1126d4ded39d248c,1,wlan0]: wps: type pbc start...
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1526] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1526] device (wlan0): Activation: (wifi) access point 'NETWORKSSID' has security, but secrets are required.
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1523] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1520] manager: NetworkManager state is now CONNECTING
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1517] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1515] device (wlan0): Activation: starting connection 'NETWORKSSID' (ABRIDGED)
Nov 18 11:27:48 HOSTNAME NetworkManager[964]: <info>  [1700303268.1508] policy: auto-activating connection 'NETWORKSSID' (ABRIDGED)
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2236] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2235] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2233] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2232] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7)
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2232] Wi-Fi P2P device controlled by interface wlan0 created
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2230] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.2230] device (wlan0): supplicant interface state: internal-starting -> disconnected
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.1788] manager: NetworkManager state is now DISCONNECTED
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.1787] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 18 11:27:45 HOSTNAME NetworkManager[964]: <info>  [1700303265.1784] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 18 11:27:44 HOSTNAME NetworkManager[964]: <info>  [1700303264.9565] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 18 11:27:44 HOSTNAME NetworkManager[964]: <info>  [1700303264.9564] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.8460] device (wlan0): set-hw-addr: reset MAC address to MACADDRESS2 (unmanage)
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.7728] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.7713] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.7710] device (wlan0): supplicant interface state: completed -> disconnected
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.7176] device (wlan0): set-hw-addr: set MAC address to MACADDRESS (scanning)
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.6715] dhcp6 (wlan0): state changed no lease
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.6715] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.6714] dhcp6 (wlan0): canceled DHCP transaction
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.6701] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.4160] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.4151] manager: NetworkManager state is now ASLEEP
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.4139] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.4013] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 18 11:27:16 HOSTNAME NetworkManager[964]: <info>  [1700303236.4009] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 18 10:50:28 HOSTNAME NetworkManager[964]: <info>  [1700301028.9350] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 18 10:49:06 HOSTNAME NetworkManager[964]: <info>  [1700300946.0182] audit: op="statistics" interface="wlan0" ifindex=3 args="2000" pid=3394 uid=1000 result="success"
Nov 18 10:46:13 HOSTNAME NetworkManager[964]: <info>  [1700300773.8122] manager: NetworkManager state is now CONNECTED_SITE
Nov 18 10:25:55 HOSTNAME NetworkManager[964]: <info>  [1700299555.9501] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 18 10:25:46 HOSTNAME NetworkManager[964]: <info>  [1700299546.8128] manager: NetworkManager state is now CONNECTED_SITE
Nov 18 10:25:02 HOSTNAME NetworkManager[964]: <info>  [1700299502.1021] audit: op="statistics" interface="wlan0" ifindex=3 args="2000" pid=3394 uid=1000 result="success"
Nov 18 01:40:27 HOSTNAME NetworkManager[964]: <info>  [1700268027.9304] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 18 01:40:25 HOSTNAME NetworkManager[964]: <info>  [1700268025.8124] manager: NetworkManager state is now CONNECTED_SITE

Last edited by hully (2023-11-18 16:32:53)

hully · 2023-11-18 15:24:08

While FF doesn't work™, check

That is not going to work.

The problem is that it either works perfectly, or it doesn't work at all.

All those tools wait for the response to arrive, and eventually go timeout and retry.

But if they go timeout, we don't know why (except that it didn't receive the response in a pre-specified time), while if the response arrive, everything runs perfectly.

For example:

➜ dig @8.8.8.8 google.com
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out

; <<>> DiG 9.18.20 <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59012
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		300	IN	A	142.250.180.174

;; Query time: 29 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sat Nov 18 16:16:32 CET 2023
;; MSG SIZE  rcvd: 55

Also my router is apparently blocking ICMP reply:

➜ ping -c8 google.com 
PING google.com (142.250.201.46) 56(84) bytes of data.

--- google.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7095ms

But that always happened, and it works if I use a VPN:
(with VPN):

❯ ping -c8 google.com 
PING google.com (172.217.17.78) 56(84) bytes of data.
64 bytes from ams16s30-in-f78.1e100.net (172.217.17.78): icmp_seq=1 ttl=115 time=134 ms
64 bytes from ams16s30-in-f78.1e100.net (172.217.17.78): icmp_seq=2 ttl=115 time=135 ms
64 bytes from fjr04s12-in-f14.1e100.net (172.217.17.78): icmp_seq=3 ttl=115 time=219 ms
64 bytes from ams16s30-in-f78.1e100.net (172.217.17.78): icmp_seq=4 ttl=115 time=243 ms
64 bytes from ams16s30-in-f78.1e100.net (172.217.17.78): icmp_seq=5 ttl=115 time=164 ms
64 bytes from fjr04s12-in-f14.1e100.net (172.217.17.78): icmp_seq=6 ttl=115 time=187 ms
64 bytes from fjr04s12-in-f14.1e100.net (172.217.17.78): icmp_seq=7 ttl=115 time=210 ms
64 bytes from ams16s30-in-f14.1e100.net (172.217.17.78): icmp_seq=8 ttl=115 time=234 ms

--- google.com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7006ms
rtt min/avg/max/mdev = 134.438/190.774/243.270/40.065 ms

I need something that monitors the connection constantly. I don't know exactly how.

At least, it seems not to be a problem of Firefox.

Also, when Firefox "doesn't work" it lasts 5/6 seconds. There is no time to run all of those commands, which in any case will just wait for those 5 seconds until the connection works again, and then return the correct result.

seth · 2023-11-18 15:36:34

Here is the output of

semi-relevant stuff.
Either look at the journal or post the complete journal of a boot covering the issue.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the current one.

That is not going to work.

Yes it does, you posted at least some of the output.

Also my router is apparently blocking ICMP reply:

No. Or (if this was true, which it's very *very* most likely not) get a router that's not complete FUBAR.

PS: your APs BSSID is way more valuable than the SSID except that it's still useless to anyone out of physical proximity and so is your MAC, certainly the random one for scanning and the other one is only a problem wrt "tracking" ie. if you post it on various locations or if you allow NM to use it for your IPv6 address (which isn't the default behavior either)

Last edited by seth (2023-11-18 15:43:31)

hully · 2023-11-18 16:34:32

No. Or (if this was true, which it's very *very* most likely not) get a router that's not complete FUBAR.

Then why I do not get ping replies, except if I use a VPN?

EDIT: removed question for which I found the answer myself

Last edited by hully (2023-11-18 17:18:29)

hully · 2023-11-18 16:39:46

the other one is only a problem wrt "tracking" ie. if you post it on various locations

I'm concerned about tracking and privacy. I don't want people to recognize my activity on the internet.

hully · 2023-11-18 17:16:00

Here is the journal log: https://raw.githubusercontent.com/10b14 … ournal.log

seth · 2023-11-18 20:16:36

That journal is 33MB in 290955 lines!
Most of it is "Framebuffer memory not appropriate for scanout" and some plasma and cs2 spam over the course of two days… no wonder you were not looking at that

There're no conflicting network services, you've an iwlwifi chip, no kernel or firmware errors because of that.
You're exclusively using IPv4 DNS but you don't seem to get any IPv4 lease? Or did you just delete those lines??
(LAN IPs are not sensitive in any way shape or form…)

On a limb: lock the connection to the 5GH BSSID or rfkill bluetooth and most certainly check whether you can still ping the _gateway when you lost the connection.

hully · 2023-11-18 20:39:24

You're exclusively using IPv4 DNS but you don't seem to get any IPv4 lease?

I didn't delete anything and don't know what is IPv4 lease.
But if you are referring to DHCP, I've set up static IP address through the NetworkManager applet, because I'm running a local server.

seth · 2023-11-18 20:43:48

Ok, that explains that.
It also means the router might run into a collision w/ that - make sure to exclude that IP from the routers dhcp stack or configure the router to bind your MAC to that IP (and use dhcp instead of a static IP)

Nevertheless

lock the connection to the 5GH BSSID or rfkill bluetooth and most certainly check whether you can still ping the _gateway when you lost the connection

hully · 2023-11-18 20:48:53

What do you mean rfkill bluetooth? To run "rfkill block bluetooth"? But I use bluetooth. I have a pair of bluetooth earbuds.

I have pinned the connection to 5GHz. Is this suggestion due to the fact that my device is switching between the 5 GHz and the 2.5 GHz back and forth?

If so, why we choose the former and not the latter?

My ISP gave me the router. I don't know whether and how much can I configure it.

hully · 2023-11-18 21:08:37

ok I have set up a static lease in the router and restored DHCP on localhost

seth · 2023-11-18 21:09:40

But I use bluetooth. I have a pair of bluetooth earbuds.

Yes I know. And now you'll test whether the connection remains stable if you don't let them interfere.

Is this suggestion due to the fact that my device is switching between the 5 GHz and the 2.5 GHz back and forth?

Yes and we chose that because BT operates on 2.4GHz.

hully · 2023-11-18 21:17:58

oh ok.

In the router settings there was also a "firewall" section. I lowered it to "user" and didn't set any rules.

But still I can't get a response from pinging.

Why?

---

It looks like we could infer my device was switching back and forth from these lines:

Nov 18 12:46:36 HOSTNAME wpa_supplicant[977]: wlan0: CTRL-EVENT-DISCONNECTED bssid=BSSID_5GHz reason=4 locally_generated=1
Nov 18 12:46:36 HOSTNAME wpa_supplicant[977]: BSSID d6:35:1d:81:66:8c ignore list count incremented to 2, ignoring for 10 seconds
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.7535] device (wlan0): supplicant interface state: completed -> disconnected
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.7536] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.8347] device (wlan0): supplicant interface state: disconnected -> scanning
Nov 18 12:46:36 HOSTNAME NetworkManager[964]: <info>  [1700307996.8348] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Nov 18 12:46:36 HOSTNAME wpa_supplicant[977]: wlan0: SME: Trying to authenticate with BSSID_2.5GHz (SSID='NETWORKSSID' freq=2437 MHz)

Last edited by hully (2023-11-18 21:19:16)

seth · 2023-11-18 21:24:09

But still I can't get a response from pinging.

Pinging what? The _gateway?

To lock the 5GHz BSSID see https://wiki.archlinux.org/title/Networ … ets_(WiFi)

Reboot w/ the recent changes in place, wait for the connection to drop out and post an updated journal.

hully · 2023-11-19 01:55:26

seth wrote:

Pinging what? The _gateway?

Any remote server, for example google. Cannot get a response back:

➜ ping google.com
PING google.com (216.58.205.46) 56(84) bytes of data.

hully · 2023-11-19 02:17:53

Nah, still happening.

Here the logs: https://raw.githubusercontent.com/10b14 … ournal.log

Pinging the gateway works:

➜ ip r
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.200 metric 600 
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.200 metric 600
➜ ping 192.168.1.1 
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=5.34 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=35.7 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=5.38 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.48 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.37 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=5.64 ms
^C
--- 192.168.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5009ms
rtt min/avg/max/mdev = 5.343/10.490/35.737/11.290 ms

Last edited by hully (2023-11-19 02:19:21)

seth · 2023-11-19 08:14:53

So it's between the gateway and the next hop (ie. your ISP)
Tried to reboot the router? Do you have more hosts in the LAN that you could ping at those moments?

Because it's like top-posting.
Why.
Please don't use "-r" w/ journalctl.

hully · 2023-11-20 10:18:38

ok thanks.

It is working now.

I'll try to ping another device connected to the LAN and eventually recall my ISP

seth · 2023-11-25 12:06:23

And 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.

Arch Linux

#1 2023-11-18 09:57:10

Connection drop sometimes

#2 2023-11-18 13:36:01

Re: Connection drop sometimes

#3 2023-11-18 15:14:52

Re: Connection drop sometimes

#4 2023-11-18 15:24:08

Re: Connection drop sometimes

#5 2023-11-18 15:36:34

Re: Connection drop sometimes

#6 2023-11-18 16:34:32

Re: Connection drop sometimes

#7 2023-11-18 16:39:46

Re: Connection drop sometimes

#8 2023-11-18 17:16:00

Re: Connection drop sometimes

#9 2023-11-18 20:16:36

Re: Connection drop sometimes

#10 2023-11-18 20:39:24

Re: Connection drop sometimes

#11 2023-11-18 20:43:48

Re: Connection drop sometimes

#12 2023-11-18 20:48:53

Re: Connection drop sometimes

#13 2023-11-18 21:08:37

Re: Connection drop sometimes

#14 2023-11-18 21:09:40

Re: Connection drop sometimes

#15 2023-11-18 21:17:58

Re: Connection drop sometimes

#16 2023-11-18 21:24:09

Re: Connection drop sometimes

#17 2023-11-19 01:55:26

Re: Connection drop sometimes

#18 2023-11-19 02:17:53

Re: Connection drop sometimes

#19 2023-11-19 08:14:53

Re: Connection drop sometimes

#20 2023-11-20 10:18:38

Re: Connection drop sometimes

#21 2023-11-25 12:06:23

Re: Connection drop sometimes

Board footer