[SOLVED] Network dropping on laptop

pitastrudl · 2026-03-24 11:12:20

I am having issues with my network dropping or not connecting. It happened on different wifi networks. After reconnecting to the network it works, then the wifi drops and few minutes later reconnects and drops again. This has been happening for 2 weeks, updated a few times since then. I thought it was powersaving but that setting below did not work. Any tips in what direction to go to, let me know.

Laptop 21MC0017MB (ThinkPad T14 Gen 5) with Ryzen

Wifi card:
product: QCNFA765 Wireless Network Adapter
vendor: Qualcomm Technologies, Inc

description: Ethernet interface
product: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0

Kernel: Linux archlinux 6.19.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Mar 2026 16:33:17 +0000 x86_64 GNU/Linux

DMESG https://0x0.st/Pf-6.txt
boot journal: https://0x0.st/Pf-I.txt

❯ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
autovt@.service                          | system
awsvpnclient.service                     | multi-user.target.wants
bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | multi-user.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
powertop.service                         | multi-user.target.wants
powertop.service                         | sleep.target.wants
remote-fs.target                         | multi-user.target.wants
rustdesk.service                         | multi-user.target.wants
systemd-networkd-resolve-hook.socket     | sockets.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-varlink-metrics.socket  | sockets.target.wants
systemd-networkd-varlink.socket          | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs.service                    | graphical-session-pre.target.wants

❯ cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[connection]
wifi.powersave = 2

edit: i wanted to add, the wifi stays connected but connectivity to the outside internet drops.

Last edited by pitastrudl (2026-03-26 08:36:59)

schard · 2026-03-24 11:27:40

With systemd-networkd + systemd-resolved and NetworkManager, you appear to have two competing networking services active. Decide on one and deactivate the other.

seth · 2026-03-24 12:59:31

resolved is orthogonal to the other two (it's mandatory for networkd and optional for NM)

edit: i wanted to add, the wifi stays connected but connectivity to the outside internet drops.

What exactly does that mean?

ping -c1 _gateway
ping -c1 8.8.8.8
ping -c1 google.com

pitastrudl · 2026-03-24 14:20:15

I have disabled networkD only and the other units from launching again, leaved resolved on. I've found further clues.

I had similar issues in Germany in a Airbnb, I am now in Croatia in a hotel and have similar issues on their wifi, so do have some other people with Linux(Ubuntu/Arch derivative) on them and Mac laptops seem to have no issues. Phones have no issues either. From what I can gather it could be just the network not liking whatever Linux type laptops are doing. If i share the hotels wifi via my phone (hotel wifi->phone hotspot->hotspot wifi->laptop) it works without issue. I tried adding wireless-regdb and enabling WIRELESS_REGDOM="HR" but that did not help either.

In regards to the

> edit: i wanted to add, the wifi stays connected but connectivity to the outside internet drops.

I wanted to clarify, that the wifi radio stays on and connected to the AP but the connectivity with the internet is dropping / unstable.

The ping commands took some time to finish executing.

~ on ☁️  (eu-central-1) took 29s 
❯ ping -c1 _gateway      
PING _gateway (172.17.0.1) 56(84) bytes of data.
64 bytes from 172.17.0.1: icmp_seq=1 ttl=64 time=0.057 ms
WIRELESS_REGDOM="HR"
--- _gateway ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms

~ on ☁️  (eu-central-1) took 39s 
❯ ping -c1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


~ on ☁️  (eu-central-1) took 10s 
❯ ping -c1 google.com
ping: google.com: Name or service not known

❯ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f  
autovt@.service                          | system
awsvpnclient.service                     | multi-user.target.wants
bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
paccache.timer                           | multi-user.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
powertop.service                         | multi-user.target.wants
powertop.service                         | sleep.target.wants
remote-fs.target                         | multi-user.target.wants
rustdesk.service                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs.service                    | graphical-session-pre.target.wants

seth · 2026-03-24 14:25:05

Airbnb … in a hotel

You'll typically have to sign up w/ a code in some captive portal.

pitastrudl · 2026-03-24 14:30:28

No captive portals here were needed on either of the wifi access points.

seth · 2026-03-24 14:47:18

nmap 172.17.0.1

Can you open http://172.17.0.1/ or https://172.17.0.1/ ?

You /do/ have a connection to the gateway, the problem is the traffic afterwards, neither do you have DNS nor a connection (but a route) to 8.8.8.8 (googles open DNS server)
Together w/ the context that yells the requirement for secondary authentication.

pitastrudl · 2026-03-24 15:20:00

There does not seem to be anything on those IPs. Nmap just gets stuck, does not output anything.

~ on ☁️  (eu-central-1) 
❯ nc -zv 172.17.0.1 80
archlinux [172.17.0.1] 80 (http): Connection refused

~ on ☁️  (eu-central-1) took 5s 
❯ nc -zv 172.17.0.1 443
172.17.0.1 443 (https): Connection refused

seth · 2026-03-24 15:56:50

Mar 24 10:39:30 archlinux NetworkManager[1948]: <warn>  [1774345170.6968] keyfile: ipv4.ignore-auto-dns: invalid setting: Key file contains key “ignore-auto-dns” which has a value that cannot be interpreted.

Did you try to add this “ignore-auto-dns” key?

Mar 24 10:39:37 archlinux systemd-networkd[1468]: wlp2s0: DHCPv4 address 172.17.10.238/20, gateway 172.17.0.1 acquired from 172.17.0.1
Mar 24 10:39:37 archlinux NetworkManager[1948]: <info>  [1774345177.2489] dhcp4 (wlp2s0): state changed new lease, address=172.17.11.151
…
Mar 24 10:44:33 archlinux systemd-resolved[1457]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 195.29.150.3.
Mar 24 10:44:37 archlinux systemd-resolved[1457]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 172.17.0.1.
Mar 24 10:44:37 archlinux systemd-resolved[1457]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 195.29.150.3.
Mar 24 10:44:53 archlinux systemd-resolved[1457]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 172.17.0.1.
Mar 24 10:44:54 archlinux systemd-resolved[1457]: Using degraded feature set TCP instead of UDP for DNS server 172.17.0.1.

172.17.0.1 maintains 172.17.10.238/20 and hands you 172.17.11.151
Also 172.17.0.1 and 195.29.150.3 are somehow (likely via dhcp) configured as DNS (195.29.150.3 being the Croatian Telecom)

nmap was "stuck" for how long? Did you attempt a UDP scan?

sudo nmap -Pn _gateway
sudo nmap -Pn -sU -p53 _gateway
dig @_gateway google.com
sudo nmap --script broadcast-dhcp-discover

Did you reboot after disabling networkd?

Mar 24 11:09:01 archlinux NetworkManager[14433]: <info>  [1774346941.8385] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Mar 24 11:09:01 archlinux NetworkManager[14433]: <info>  [1774346941.8386] device (wlp2s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Mar 24 11:09:01 archlinux NetworkManager[14433]: <info>  [1774346941.8388] manager: NetworkManager state is now CONNECTED_SITE
Mar 24 11:09:01 archlinux NetworkManager[14433]: <info>  [1774346941.8390] device (wlp2s0): Activation: successful, device activated.
Mar 24 11:09:01 archlinux NetworkManager[14433]: <info>  [1774346941.9635] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 24 11:09:01 archlinux kdeconnectd[4218]: Failed to send mDNS query: Cannot assign requested address
Mar 24 11:09:03 archlinux systemd-networkd[1468]: wlp2s0: Gained IPv6LL
…
Mar 24 11:09:11 archlinux systemd-timesyncd[1458]: Timed out waiting for reply from 185.103.216.7:123 (185.103.216.7).

Please post an updated journal…

pitastrudl · 2026-03-24 16:18:10

Sooooo, it seems that Docker installed had the same subnet as the Wifi network, changed the subnet and the issue is gone.

3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 172.17.11.151/20 brd 172.17.15.255 scope global dynamic noprefixroute wlp2s0
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

Added this /etc/docker/daemon.json and restarting Docker.

❯ cat /etc/docker/daemon.json                            
{
  "default-address-pools": [
    {"base": "10.10.0.0/16", "size": 24}
  ],
  "bip": "10.10.0.1/24"
}

Thank you for helping!

Last edited by pitastrudl (2026-03-24 16:18:33)

Arch Linux

#1 2026-03-24 11:12:20

[SOLVED] Network dropping on laptop

#2 2026-03-24 11:27:40

Re: [SOLVED] Network dropping on laptop

#3 2026-03-24 12:59:31

Re: [SOLVED] Network dropping on laptop

#4 2026-03-24 14:20:15

Re: [SOLVED] Network dropping on laptop

#5 2026-03-24 14:25:05

Re: [SOLVED] Network dropping on laptop

#6 2026-03-24 14:30:28

Re: [SOLVED] Network dropping on laptop

#7 2026-03-24 14:47:18

Re: [SOLVED] Network dropping on laptop

#8 2026-03-24 15:20:00

Re: [SOLVED] Network dropping on laptop

#9 2026-03-24 15:56:50

Re: [SOLVED] Network dropping on laptop

#10 2026-03-24 16:18:10

Re: [SOLVED] Network dropping on laptop

Board footer