Hello!
As in the title. I have two computers running NixOS, a Surface Book 2 and an Acer Aspire E15; on the Surface, after suspend, the WiFi connection takes minutes to come back, and then comes and goes sporadically, while on the Acer, I have to run something like ifconfig to wake up the adapter. This happens with both wpa_supplicant and networkmanager.
Any help would be greatly appreciated!
Can you show the output of journalctl -b -u wpa_supplicant?
When the laptop resumes from sleep the daemon should be automatically restarted and it will wait an(y) interface to come up. If everything is working you should see something like this:
systemd[1]: Stopping WPA Supplicant instance...
systemd[1]: Stopped WPA Supplicant instance.
systemd[1]: Started WPA Supplicant instance.
wpa_supplicant-start[596]: Waiting for wireless interfaces
wpa_supplicant-start[596]: Adding interface wlp3s0
wpa_supplicant[596]: Successfully initialized wpa_supplicant
(I’m the maintainer of networking.wireless module, so I don’t know about network manager)
-- Journal begins at Sun 2022-01-23 07:33:06 UTC, ends at Fri 2022-04-01 15:04:16 UTC. --
Apr 01 01:47:30 sandshrew systemd[1]: Started WPA Supplicant instance.
Apr 01 01:47:31 sandshrew wpa_supplicant-start[1581]: Waiting for wireless interfaces
Apr 01 01:47:33 sandshrew systemd[1]: Stopping WPA Supplicant instance...
Apr 01 01:47:33 sandshrew systemd[1]: wpa_supplicant.service: Deactivated successfully.
Apr 01 01:47:33 sandshrew systemd[1]: Stopped WPA Supplicant instance.
Apr 01 01:47:33 sandshrew systemd[1]: Started WPA Supplicant instance.
Apr 01 01:47:33 sandshrew wpa_supplicant-start[1732]: Adding interface wlp1s0
Apr 01 01:47:33 sandshrew wpa_supplicant[1732]: Successfully initialized wpa_supplicant
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise=-92 txrate=6500
Apr 01 02:00:06 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=87800
Apr 01 02:00:11 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-75 txrate=81000
Apr 01 02:00:11 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=-75 txrate=81000
Apr 01 02:00:11 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=-75 txrate=81000
Apr 01 02:00:11 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:00:11 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:00:14 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:00:14 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:00:14 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:00:14 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:00:14 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:00:15 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-47 noise=-84 txrate=117000
Apr 01 02:02:09 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-42 noise=-81 txrate=52000
Apr 01 02:05:26 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:05:26 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:05:29 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-39 noise=-81 txrate=130000
Apr 01 02:05:36 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:05:36 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:05:36 sandshrew wpa_supplicant[1732]: BSSID 76:9b:e8:10:98:40 ignore list count incremented to 2, ignoring for 10 seconds
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:05:39 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=-84 txrate=130000
Apr 01 02:05:46 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:05:46 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:05:46 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:05:46 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:05:46 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:05:47 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-68 noise=-92 txrate=6500
Apr 01 02:05:53 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:05:53 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:05:53 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:05:53 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:05:53 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:05:54 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-40 noise=-78 txrate=117000
Apr 01 02:06:00 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:06:01 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:06:01 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:06:01 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:06:01 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:06:01 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise=-92 txrate=6500
Apr 01 02:16:18 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:16:18 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:16:21 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-68 noise=-92 txrate=6500
Apr 01 02:21:33 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:21:33 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:21:33 sandshrew wpa_supplicant[1732]: BSSID 74:9b:e8:10:98:48 ignore list count incremented to 2, ignoring for 10 seconds
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:21:36 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-92 txrate=6500
Apr 01 02:36:58 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:36:58 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:36:58 sandshrew wpa_supplicant[1732]: BSSID 74:9b:e8:10:98:48 ignore list count incremented to 3, ignoring for 60 seconds
Apr 01 02:37:01 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:37:01 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:37:01 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:37:01 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:37:01 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:37:02 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-68 noise=-75 txrate=6500
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:47:18 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-39 noise=-78 txrate=117000
Apr 01 02:47:25 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:47:25 sandshrew wpa_supplicant[1732]: wlp1s0: Association request to the driver failed
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 02:47:28 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-40 noise=-80 txrate=130000
Apr 01 02:47:34 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 02:47:34 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 02:47:34 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 02:47:35 sandshrew wpa_supplicant[1732]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 02:47:35 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 02:47:35 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise=-92 txrate=6500
Apr 01 03:06:20 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=87800
Apr 01 14:52:24 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=76:9b:e8:10:98:40 reason=3 locally_generated=1
Apr 01 14:52:24 sandshrew systemd[1]: Stopping WPA Supplicant instance...
Apr 01 14:52:24 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 01 14:52:24 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 01 14:52:24 sandshrew wpa_supplicant[1732]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Apr 01 14:52:24 sandshrew wpa_supplicant[1732]: wlp1s0: CTRL-EVENT-TERMINATING
Apr 01 14:52:24 sandshrew systemd[1]: wpa_supplicant.service: Deactivated successfully.
Apr 01 14:52:24 sandshrew systemd[1]: Stopped WPA Supplicant instance.
Apr 01 14:52:24 sandshrew systemd[1]: Started WPA Supplicant instance.
Apr 01 14:52:24 sandshrew wpa_supplicant-start[76942]: Adding interface wlp1s0
Apr 01 14:52:24 sandshrew wpa_supplicant[76942]: Successfully initialized wpa_supplicant
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: Associated with 76:9b:e8:10:98:40
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: WPA: Key negotiation completed with 76:9b:e8:10:98:40 [PTK=CCMP GTK=CCMP]
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 76:9b:e8:10:98:40 completed [id=0 id_str=]
Apr 01 14:52:27 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-92 txrate=6500
Apr 01 14:52:29 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-92 txrate=6500
Apr 01 14:53:26 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=87800
Apr 01 14:53:34 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-92 txrate=81000
Apr 01 14:54:40 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=81000
Apr 01 14:54:46 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-92 txrate=87800
Apr 01 14:54:55 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=81000
Apr 01 14:55:03 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=-92 txrate=87800
Apr 01 14:55:17 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=-92 txrate=87800
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: Associated with 74:9b:e8:10:98:48
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: WPA: Key negotiation completed with 74:9b:e8:10:98:48 [PTK=CCMP GTK=CCMP]
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 74:9b:e8:10:98:48 completed [id=0 id_str=]
Apr 01 14:57:41 sandshrew wpa_supplicant[76942]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-42 noise=-84 txrate=130000
As you can see from the timestamps, it’s associating pretty fast:
Apr 01 01:47:33 sandshrew systemd[1]: Stopped WPA Supplicant instance.
Apr 01 01:47:33 sandshrew systemd[1]: Started WPA Supplicant instance.
Apr 01 01:47:33 sandshrew wpa_supplicant-start[1732]: Adding interface wlp1s0
Apr 01 01:47:33 sandshrew wpa_supplicant[1732]: Successfully initialized wpa_supplicant
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: Trying to associate with 76:9b:e8:10:98:40 (SSID='Wofie' freq=5745 MHz)
Apr 01 01:47:40 sandshrew wpa_supplicant[1732]: wlp1s0: Associated with 76:9b:e8:10:98:40
the problem may be that the connection drops because the signal is quite poor:
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=-75 txrate=81000
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=-75 txrate=81000
Trying to associate with 74:9b:e8:10:98:48 (SSID='Wofie' freq=2462 MHz)
Association request to the driver failed
[...]
Bah, I knew my WiFi would kill me one day… Is there any other way to solve this, perhaps?
Unless there is some power management issue, frequent disconnections just mean there is a bad signal/noise ratio. Since you’re having the same issue on two different machines, it’s likely the second option.
Try moving closer to the access point to see if the problem persists. You could also run a scan to see if there are overlapping networks (and changing channels).
How would I run the scan? Also, what channel would you recommend? Would unstable work, or should I roll wpa_supplicant (and / or any other necessary packages) back to 21.11?
If I move any closer to the access point, I might as well be using an ethernet connection! 
Ahah no, I meant changing the WiFi channel, not the NixOS one.
If you’re in a place with lots of wireless network, it’s possible some of these are close or have the same channel are yours, increasing the noise.
You can check with a WiFi scanner: there’s linssid in Nixpkgs, for example.
Got it. I think it’s the network itself; the new provider is absolutely horrible… Actually, could you tell me if something is wrong with this ifconfig info?
wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.36 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2607:9880:1190:1:68a:33e9:d4f8:8bc3 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:61c0:3f0e:7f8c:79cc prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:32a0:a59c:6aa9:ae28 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:2941:8330:168d:d94 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:c60b:e0d6:2412:fe26 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:2753:5a1f:5065:6589 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:655e:2571:b780:27a9 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:ab1a:4fa6:9f35:2a88 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:69a:a449:93be:cfbe prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:450:61:eb55:6f60 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:e78b:676d:4283:38a6 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:81fa:2c10:7688:4e35 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:bf5f:2044:a8d0:9cdf prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:792c:496e:d76f:f1f6 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:b308:99c7:e292:f49f prefixlen 64 scopeid 0x0<global>
inet6 fe80::c69d:edff:fe21:a1ba prefixlen 64 scopeid 0x20<link>
inet6 2607:9880:1190:1:54ff:21c7:8efa:d66e prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:ef20:a74c:1004:efaa prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:2b43:62a7:adea:4e14 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:c69d:edff:fe21:a1ba prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:ed9c:ad03:fee1:3988 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:3b1:cc90:df7c:e65f prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:a92a:72ff:ccc4:8153 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:a63f:d320:78d5:a9eb prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:6e1c:62a3:46e6:bc85 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:4481:3ecc:1f5f:a65d prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:e75b:b09:e6cf:68b prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:d670:c4f9:b72d:f864 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:f1db:b3ac:f312:a42a prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1::c097 prefixlen 128 scopeid 0x0<global>
inet6 2607:9880:1190:1:c966:b69c:c0c2:148e prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:326b:d6b5:6041:612f prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:3371:97e0:e62f:eae2 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:65ee:8e68:41b1:7beb prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:c12a:1189:695:b1b2 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:4bd0:5bc6:c86e:556a prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:8d29:930c:e9ef:2412 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:755a:653c:e7d:fe04 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:c26f:e11c:8c2a:21e9 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:2251:d6b0:ada9:2a67 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:9d0f:80eb:cc9b:7a07 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:3ad4:3767:ee3d:b97a prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:5109:2ab0:b338:35b8 prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:7ffd:5988:5e56:bdfe prefixlen 64 scopeid 0x0<global>
inet6 2607:9880:1190:1:8fea:60f1:2172:7f7d prefixlen 64 scopeid 0x0<global>
ether c4:9d:ed:21:a1:ba txqueuelen 1000 (Ethernet)
RX packets 853690 bytes 1061375294 (1012.2 MiB)
RX errors 0 dropped 91477 overruns 0 frame 0
TX packets 274890 bytes 43975140 (41.9 MiB)
TX errors 46 dropped 0 overruns 0 carrier 0 collisions 0
There seem to be way too many inet6 entries.
That’s fine; with ipv6 you’ll often get randomized IP addresses that cycle for privacy reasons, given there’s no NAT so the IP uniquely identifies your computer. They persist for a while.
Does your ISP set up the wireless network for you? The channel settings should happen entirely on the router, if you are sharing the router with a bunch of other people (as is sadly getting more and more common, ISPs just providing passwords for WPA2-PSK protected wifis, completely ignoring security or performance) you should probably call your ISP and ask them to get a repeater closer to you.
If you do have your own router, it entirely depends on the manufacturer, firmware, etc. how and whether configuring your wireless channel is even possible, but the basic theory is just that these are different sub-bands of the wireless frequency your network is communicating with. If there are many networks using the same wavelength that will cause interference (and this is common, because most people don’t bother/know to scan, and implementations are lazy and just use channel 11 99% of the time).
Find your router’s IP, sign into its admin page (it’ll likely have a default password set if you’ve never configured it, and you should change that), and look around the UI to see if it can be configured. Many UIs implement a scan button, if they don’t you can use iw dev wlp1s0 scan to dump a bunch of info about wireless networks near your computer.
It’s also worth checking if there’s anything metallic near your router or such, or anything else that might make the signal struggle reaching you.
Thanks for the clarification! Regarding the signal, however, what was happening was that, appararently, 5 GHz frequencies can’t reach me on the second floor, but our modem provides both 5 GHz and 2.4 GHz at the same time with the same SSID; I had to set up our extender, which allows me to pick which range I wanted, i.e. 2.4 GHz. If all goes well in the next few days, I think I can close this issue, then!