Wireless Network Disconnected Frequently

kehongying · 2020-06-01 16:31:35

Hi everyone,

I've suffered from a strange problem since February. I'm using NetworkManager to manage my network instead of netctl. Once I restart my laptop, my wifi will be connected automatically, but disconnect after a few seconds. This problem can be solved in a strange way: I need to reboot and boot my Windows 10, then reboot back to Arch Linux.
It is very inconvenient for me to boot twice every time. Is there anyone who has the same problem and solved? Or it is Win10's problem?

My laptop is Lenovo Y530. Dual system with Win10.
Kernel Version: 5.6.15-arch1-1 #1 SMP PREEMPT Wed, 27 May 2020 23:42:26 +0000 x86_64 GNU/Linux
NetworkManager Version: 1.24.2-1

There is some log before and after the wifi disconnect as the following:

[kehongying@KeHongYing ~]$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Mon 2020-06-01 23:44:04 CST; 1min 41s ago
       Docs: man:NetworkManager(8)
   Main PID: 814 (NetworkManager)
      Tasks: 3 (limit: 19044)
     Memory: 21.0M
     CGroup: /system.slice/NetworkManager.service
             └─814 /usr/bin/NetworkManager --no-daemon

Jun 01 23:44:30 KeHongYing NetworkManager[814]: <info>  [1591026270.6874] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 01 23:44:31 KeHongYing NetworkManager[814]: <info>  [1591026271.2448] dhcp6 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 01 23:44:31 KeHongYing NetworkManager[814]: <info>  [1591026271.2460] policy: set 'fat' (wlp7s0) as default for IPv6 routing and DNS
Jun 01 23:44:31 KeHongYing NetworkManager[814]: <info>  [1591026271.2468] dhcp6 (wlp7s0): state changed unknown -> bound
Jun 01 23:45:25 KeHongYing NetworkManager[814]: <info>  [1591026325.7468] device (wlp7s0): supplicant interface state: completed -> disconnected
Jun 01 23:45:28 KeHongYing NetworkManager[814]: <info>  [1591026328.1451] device (wlp7s0): supplicant interface state: disconnected -> scanning
Jun 01 23:45:41 KeHongYing NetworkManager[814]: <warn>  [1591026341.2739] device (wlp7s0): link timed out.
Jun 01 23:45:41 KeHongYing NetworkManager[814]: <info>  [1591026341.2743] device (wlp7s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 01 23:45:41 KeHongYing NetworkManager[814]: <info>  [1591026341.2748] manager: NetworkManager state is now DISCONNECTED
Jun 01 23:45:43 KeHongYing NetworkManager[814]: <info>  [1591026343.9413] device (wlp7s0): set-hw-addr: set MAC address to 3E:45:4F:E8:C3:E5 (scanning)
[kehongying@KeHongYing ~]$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Mon 2020-06-01 23:44:04 CST; 2min 6s ago
       Docs: man:NetworkManager(8)
   Main PID: 814 (NetworkManager)
      Tasks: 3 (limit: 19044)
     Memory: 21.0M
     CGroup: /system.slice/NetworkManager.service
             └─814 /usr/bin/NetworkManager --no-daemon

Jun 01 23:45:41 KeHongYing NetworkManager[814]: <info>  [1591026341.2748] manager: NetworkManager state is now DISCONNECTED
Jun 01 23:45:43 KeHongYing NetworkManager[814]: <info>  [1591026343.9413] device (wlp7s0): set-hw-addr: set MAC address to 3E:45:4F:E8:C3:E5 (scanning)
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <warn>  [1591026346.2666] platform-linux: do-change-link[3]: failure changing link: failure 114 (Operation already in progress)
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <warn>  [1591026346.2682] device (wlp7s0): Activation: failed for connection 'fat'
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.2708] device (wlp7s0): supplicant interface state: scanning -> interface_disabled
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.2780] device (wlp7s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.3136] dhcp4 (wlp7s0): canceled DHCP transaction
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.3136] dhcp4 (wlp7s0): state changed bound -> done
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.3138] dhcp6 (wlp7s0): canceled DHCP transaction
Jun 01 23:45:46 KeHongYing NetworkManager[814]: <info>  [1591026346.3138] dhcp6 (wlp7s0): state changed bound -> done

seth · 2020-06-01 17:56:12

find /etc/systemd -type l -exec test -f {} \; -print

Also ensure to disable windows fast boot (see my signature for a link)

kehongying · 2020-06-02 04:06:55

I've checked that fast boot is disabled.

[kehongying@KeHongYing ~]$ find /etc/systemd -type l -exec test -f {} \; -print
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/graphical.target.wants/optimus-manager.service
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/tlp.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent.socket

Is there any strange point?

seth · 2020-06-02 05:37:52

The usual cause is conflicting network managing services (eg. NM + dhcpcd) but that's not the case here.

From the service status, try to disable https://wiki.archlinux.org/index.php/Ne … domization
The next contender would be TLP

kehongying · 2020-06-03 09:55:43

It seems that randomize the MAC isn't working.

Do you mean that TLP would cause the NetworkManager can't initialize successfully?

seth · 2020-06-03 11:32:53

The idea is to NOT randomize the MAC address for scanning.
Otherwise TLP might send the device into a poewer saving state from which it doesn't wake up properly.

kehongying · 2020-06-04 06:13:21

I think that default is NOT randomized. And I've tried both but it does still not work.

I've disabled tlp.service and tlp-sleep.service and unmask the rfkill-service and rfkill-socket(someone say that these two might cause confliction).
I also tried to downgrade the NetworkManager when I found this problem in February. But I still can't find a proper solution to solve this.

V1del · 2020-06-04 09:09:31

The default is to randomize which is why the suggestion is to disable it. if that doesn't work nor disabling power saving helps i'd also hazard a guess based on that log that it might also be an issue with NMs dhcp client in which case you might want to try: https://wiki.archlinux.org/index.php/Ne … HCP_client

kehongying · 2020-06-06 06:01:49

Oh, I've seen it writes default is YES on arch wiki. I'm sorry about that. I've set it to NOT randomize after that day.

I tried to install dhclient and tested these days, but it still can't solve the problem.
Won't the dhclient conflict with NMs?

Last edited by kehongying (2020-06-06 11:46:55)

seth · 2020-06-06 06:16:47

Not if you don't activate it a second service, but advise NM to use it as its dhcp provider (as detailed in the link V1del posted)

kehongying · 2020-09-22 12:43:12

This problem hasn't solved.

While updating the package and system(:: Running post-transaction hooks...), it occurs some of the messages as follows.

( 5/14) Applying kernel sysctl settings...
Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).

It seems that there are some explicit in my system, where should I fix it. This might cause my internet problem.

V1del · 2020-09-22 13:17:56

These messages are normal and not generally cause for concern, did you try what I suggested? What's the updated journal log?

kehongying · 2020-09-23 05:52:07

I've tried it before. I install dhclient and modify the config file as wiki write.

The journal log with NM is as following.

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Wed 2020-09-23 13:53:24 CST; 50s ago
       Docs: man:NetworkManager(8)
   Main PID: 758 (NetworkManager)
      Tasks: 3 (limit: 19039)
     Memory: 18.6M
     CGroup: /system.slice/NetworkManager.service
             └─758 /usr/bin/NetworkManager --no-daemon

Sep 23 13:53:25 KeHongYing NetworkManager[758]: <info>  [1600840405.2503] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 23 13:53:25 KeHongYing NetworkManager[758]: <info>  [1600840405.3902] device (wlp7s0): driver supports Access Point (AP) mode
Sep 23 13:53:25 KeHongYing NetworkManager[758]: <info>  [1600840405.3907] manager: (wlp7s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 23 13:53:25 KeHongYing NetworkManager[758]: <info>  [1600840405.3915] device (wlp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 23 13:53:25 KeHongYing NetworkManager[758]: <info>  [1600840405.8671] device (wlp7s0): set-hw-addr: set MAC address to 0A:9E:5D:BC:0D:F1 (scanning)
Sep 23 13:53:28 KeHongYing NetworkManager[758]: <info>  [1600840408.5811] ovsdb: Could not connect: No such file or directory
Sep 23 13:53:28 KeHongYing NetworkManager[758]: <info>  [1600840408.6655] device (wlp7s0): supplicant interface state: internal-starting -> disconnected
Sep 23 13:53:28 KeHongYing NetworkManager[758]: <info>  [1600840408.6655] device (wlp7s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'manag>
Sep 23 13:53:34 KeHongYing NetworkManager[758]: <info>  [1600840414.6409] manager: startup complete
Sep 23 13:53:53 KeHongYing NetworkManager[758]: <info>  [1600840433.6416] agent-manager: agent[3f359c0552eb3665,:1.34/org.kde.plasma.networkmanagement/1000]: agent registered

If I reboot and start arch after start win10 first, the log is as following.

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Wed 2020-09-23 13:43:58 CST; 6min ago
       Docs: man:NetworkManager(8)
   Main PID: 760 (NetworkManager)
      Tasks: 4 (limit: 19039)
     Memory: 26.0M
     CGroup: /system.slice/NetworkManager.service
             ├─ 760 /usr/bin/NetworkManager --no-daemon
             └─1288 /usr/bin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/NetworkManager/dhclient-wlp7s0.pid -lf /var/lib/NetworkManager/dhclient-ac6c26f1-1c63-4900-92cf-54f006e>

Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5528] dhcp4 (wlp7s0): option subnet_mask          => '255.255.0.0'
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5528] dhcp4 (wlp7s0): state changed unknown -> extended
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5573] device (wlp7s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5911] device (wlp7s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5921] device (wlp7s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5937] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.5998] manager: NetworkManager state is now CONNECTED_SITE
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.6000] policy: set 'ntu_peap' (wlp7s0) as default for IPv4 routing and DNS
Sep 23 13:44:32 KeHongYing NetworkManager[760]: <info>  [1600839872.6110] device (wlp7s0): Activation: successful, device activated.
Sep 23 13:44:33 KeHongYing NetworkManager[760]: <info>  [1600839873.9550] manager: NetworkManager state is now CONNECTED_GLOBAL

Last edited by kehongying (2020-09-23 05:59:14)

seth · 2020-09-23 06:26:56

I'm quite sure V1del meant the entire journal, not the NM status. But it already shows that you're still using the internal dhcp implementation rather than dhclient.

kehongying · 2020-09-24 06:53:34

I've modified the /etc/NetworkManager/conf.d/dhcp-client.conf. And also enable dhclient@wlp7s0 at this time.

But I still stuck without starting win10 before.

Here are some NM and dhclient status:

[kehongying@KeHongYing ~]$ systemctl status dhclient@wlp7s0
● dhclient@wlp7s0.service - dhclient on wlp7s0
     Loaded: loaded (/usr/lib/systemd/system/dhclient@.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2020-09-24 14:41:20 CST; 52s ago
   Main PID: 764 (dhclient)
      Tasks: 1 (limit: 19039)
     Memory: 4.5M
     CGroup: /system.slice/system-dhclient.slice/dhclient@wlp7s0.service
             └─764 /usr/bin/dhclient -pf /run/dhclient@wlp7s0/dhclient.pid -d wlp7s0

Sep 24 14:41:46 KeHongYing dhclient[764]: send_packet: Network is down
Sep 24 14:41:46 KeHongYing dhclient[764]: dhclient.c:2456: Failed to send 300 byte long packet over wlp7s0 interface.
Sep 24 14:41:46 KeHongYing dhclient[764]: send_packet: Network is down
Sep 24 14:41:46 KeHongYing dhclient[764]: dhclient.c:2456: Failed to send 300 byte long packet over wlp7s0 interface.
Sep 24 14:42:03 KeHongYing dhclient[764]: DHCPDISCOVER on wlp7s0 to 255.255.255.255 port 67 interval 14
Sep 24 14:42:03 KeHongYing dhclient[764]: DHCPDISCOVER on wlp7s0 to 255.255.255.255 port 67 interval 14
Sep 24 14:42:03 KeHongYing dhclient[764]: send_packet: Network is down
Sep 24 14:42:03 KeHongYing dhclient[764]: dhclient.c:2456: Failed to send 300 byte long packet over wlp7s0 interface.
Sep 24 14:42:03 KeHongYing dhclient[764]: send_packet: Network is down
Sep 24 14:42:03 KeHongYing dhclient[764]: dhclient.c:2456: Failed to send 300 byte long packet over wlp7s0 interface.

[kehongying@KeHongYing ~]$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Thu 2020-09-24 14:41:20 CST; 1min 4s ago
       Docs: man:NetworkManager(8)
   Main PID: 763 (NetworkManager)
      Tasks: 3 (limit: 19039)
     Memory: 18.5M
     CGroup: /system.slice/NetworkManager.service
             └─763 /usr/bin/NetworkManager --no-daemon

Sep 24 14:41:30 KeHongYing NetworkManager[763]: <error> [1600929690.5939] device (wlp7s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_sup>
Sep 24 14:41:30 KeHongYing NetworkManager[763]: <info>  [1600929690.5940] manager: startup complete
Sep 24 14:41:40 KeHongYing NetworkManager[763]: <warn>  [1600929700.8219] device (wlp7s0): re-acquiring supplicant interface (#1).
Sep 24 14:41:45 KeHongYing NetworkManager[763]: <error> [1600929705.3874] device (wlp7s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_sup>
Sep 24 14:41:47 KeHongYing NetworkManager[763]: <info>  [1600929707.9777] agent-manager: agent[1b5c52446534fcc8,:1.34/org.kde.plasma.networkmanagement/1000]: agent registered
Sep 24 14:41:55 KeHongYing NetworkManager[763]: <warn>  [1600929715.8255] device (wlp7s0): re-acquiring supplicant interface (#2).
Sep 24 14:42:00 KeHongYing NetworkManager[763]: <error> [1600929720.3670] device (wlp7s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_sup>
Sep 24 14:42:10 KeHongYing NetworkManager[763]: <warn>  [1600929730.8249] device (wlp7s0): re-acquiring supplicant interface (#3).
Sep 24 14:42:15 KeHongYing NetworkManager[763]: <error> [1600929735.4053] device (wlp7s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_sup>
Sep 24 14:42:25 KeHongYing NetworkManager[763]: <warn>  [1600929745.8288] device (wlp7s0): re-acquiring supplicant interface (#4).

Or should I modify other config files to switch to dhclient completely?

seth · 2020-09-24 11:19:31

I've modified the /etc/NetworkManager/conf.d/dhcp-client.conf. And also enable dhclient@wlp7s0 at this time.

This way you created a race condition on the device - disable dhclient@wlp7s0 again.
Also check the output of rfkill and if win10 has a reliable impact on the situation, I'm less than convinced that windows fast boot (NOT the setting in your BIOS/UEFI) is really disabled.

Last edited by seth (2020-09-24 11:20:45)

kehongying · 2020-09-25 03:19:46

I've checked windows fast boot is disabled. I follow https://www.windowscentral.com/how-disa … st-startup and check it many times.

The rfkill output is as follow.

[kehongying@KeHongYing ~]$ rfkill
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 3 bluetooth hci0              unblocked unblocked

Arch Linux

#1 2020-06-01 16:31:35

Wireless Network Disconnected Frequently

#2 2020-06-01 17:56:12

Re: Wireless Network Disconnected Frequently

#3 2020-06-02 04:06:55

Re: Wireless Network Disconnected Frequently

#4 2020-06-02 05:37:52

Re: Wireless Network Disconnected Frequently

#5 2020-06-03 09:55:43

Re: Wireless Network Disconnected Frequently

#6 2020-06-03 11:32:53

Re: Wireless Network Disconnected Frequently

#7 2020-06-04 06:13:21

Re: Wireless Network Disconnected Frequently

#8 2020-06-04 09:09:31

Re: Wireless Network Disconnected Frequently

#9 2020-06-06 06:01:49

Re: Wireless Network Disconnected Frequently

#10 2020-06-06 06:16:47

Re: Wireless Network Disconnected Frequently

#11 2020-09-22 12:43:12

Re: Wireless Network Disconnected Frequently

#12 2020-09-22 13:17:56

Re: Wireless Network Disconnected Frequently

#13 2020-09-23 05:52:07

Re: Wireless Network Disconnected Frequently

#14 2020-09-23 06:26:56

Re: Wireless Network Disconnected Frequently

#15 2020-09-24 06:53:34

Re: Wireless Network Disconnected Frequently

#16 2020-09-24 11:19:31

Re: Wireless Network Disconnected Frequently

#17 2020-09-25 03:19:46

Re: Wireless Network Disconnected Frequently

Board footer