# Zero 2 W Cannot Connect to Wifi **URL:** \ **Category:** Troubleshooting\ **Tags:** wifi\ **Created:** [18 February 2025 04:39 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792 "2025-02-18T04:39:45Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [18 February 2025 04:39 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/1 "2025-02-18T04:39:45Z")
### Creating a bug report/issue I have searched the existing open and closed issues #### Required Information - DietPi version | `cat /boot/dietpi/.version` Core=9 Sub=10 RC=0 - Distro version | `echo $G_DISTRO_NAME $G_RASPBIAN` bookworm 0 - Kernel version | `uname --all` Debian 1:6.6.74-1+rpt1 - Architecture | `dpkg --print-architecture` arm64 - SBC model | `echo $G_HW_MODEL_NAME` or (EG: RPi3) RPZ2W - Power supply used | (EG: 5V 1A RAVpower) Desktop USB - SD card used | (EG: SanDisk ultra) PNY 32GB Elite Class 10 U1 #### Steps taken to fix issue - Issue happens on both DietPi and official Raspian - The Pi connects to the router when the router is not password protected - The Pi connects normally through ethernet - Issue happens when trying both DCHP and Static - All other devices connect to router normally (Android, Windows, ChromeOS, macOS) - I have changed router settings to use WPA-PSK [TKIP], WPA2-PSK [AES], WPA-PSK [TKIP] + WPA2-PSK [AES] - I have changed the router channels to all available ones - I have changed the password to something simpler (it normally is \*\*\*\*\*\*\*[] I thought the brackets might be messing things up) - The router I am using is the Netgear C6900 - Ran Angry IP Scanner to see if I had somehow ran out of IPs #### Things I haven’t tried due to various reasons - Switching to a worse monitor (I saw somewhere that a high resolution monitor can prevent it from connecting to WiFi. It connected just fine with no password on said monitor, so I haven’t tried it. - New SD card (I don’t have any spares laying around) - Factory Reset Router (I REALLY don’t want to deal with everything that comes with) ---
**Author:** ![StephanStS](https://dietpi.com/forum/user_avatar/dietpi.com/stephansts/32/2522_2.png) [@StephanStS](https://dietpi.com/forum/u/StephanStS)\ **Post date:** [18 February 2025 11:49 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/2 "2025-02-18T11:49:26Z")
Would it be an option for you to use a “micro USB LAN adapter” to connect to the router? If this works, in the next step you can try to connect to the router via WiFi using the `dietpi-config` tool. If this works, you can go on to investigate the correct settings via `dietpi-wifi.txt`. When I had problems, this mostly helped me. General questions: - Which router do you use? - Can you access this router with other wireless hardware (e.g. notebook)? - Did you setup the `dietpi-wifi.txt` correctly (e.g. `aWIFI_KEY[0]` value)? ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [18 February 2025 15:16 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/3 "2025-02-18T15:16:18Z")
Ethernet has always connected fine. I would just prefer to run everything over wifi. While it’s connected through ethernet, it still doesn’t connect through wifi Router is a Netgear C6900 Every other device connects to the router fine I’ve only tried to setup te Wifi through `dietpi-config`, no editing text files ---
**Author:** ![StephanStS](https://dietpi.com/forum/user_avatar/dietpi.com/stephansts/32/2522_2.png) [@StephanStS](https://dietpi.com/forum/u/StephanStS)\ **Post date:** [18 February 2025 17:28 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/4 "2025-02-18T17:28:28Z")
To have a running Ethernet connection is a good base to go on with the examination. Fine. The next steps I propose to do with `dietpi-config`. If this does not work, also the firstboot file configuration will assumable also not work. In `dietpi-config`, were you able to scan (and see) your WiFi network? In the network setting you can scan for WiFi networks: → 7 : Network Options: Adapters → WiFi → Scan → 0 : [Unused] Select to configure → Scan Do you then see your WiFi (SSID)? ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [18 February 2025 17:29 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/5 "2025-02-18T17:29:56Z")
My SSID does show up when running the scan It’s shown up every time I try to connect, but it never does ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [18 February 2025 17:54 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/6 "2025-02-18T17:54:09Z")
can you have a look into system log for relevant information ```auto journalctl -u ifup* ``` ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [18 February 2025 19:03 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/7 "2025-02-18T19:03:17Z")
[pi logs.txt](https://dietpi.com/forum/uploads/short-url/83bD0A9eiHPnoYzZPu4nV3jcimv.txt) (50.8 KB) ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [18 February 2025 20:38 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/8 "2025-02-18T20:38:04Z")
```auto Feb 18 17:46:36 DietPi wpa_supplicant[406]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=08:36:c9:58:a5:63 status_code=16 Feb 18 17:46:36 DietPi wpa_supplicant[406]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Miiiiine" auth_failures=1 duration=10 reason=CONN_FAILED ``` `So status_code=16` means auth failure. We ruled out DHCP, since you also tried via static IP. So if you are sure the password is correct and you don’t have MAC filtering or something similiar activated on the router, then I would guess it’s a incompatibility between the router and the Pi. I found similiar cases, where features of the router prevented the RPis to connect, for example `fast roaming`, see: [https://raspberrypi.stackexchange.com/questions/77144/rpi3-wireless-issue-ctrl-event-assoc-reject-status-code-16](https://raspberrypi.stackexchange.com/questions/77144/rpi3-wireless-issue-ctrl-event-assoc-reject-status-code-16) Since this is a trail and error approach, we can try to get more info, by connecting manually via `wpa_supplicant` with increased verbosity: ```auto sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -ddd ``` ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [18 February 2025 22:11 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/12 "2025-02-18T22:11:12Z")
```auto root@DietPi:~# sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -ddd wpa_supplicant v2.10 random: getrandom() support available Successfully initialized wpa_supplicant Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' country='GB' ctrl_interface='DIR=/run/wpa_supplicant GROUP=netdev' update_config=1 Line: 7 - start of a new network block ssid - hexdump_ascii(len=8): 4d 69 69 69 69 69 6e 65 Miiiiine scan_ssid=1 (0x1) key_mgmt: 0x2 PSK - hexdump(len=32): [REMOVED] Priority group 0 id=0 ssid='Miiiiine' nl80211: Using driver-based roaming nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported cipher 00-0f-ac:2 nl80211: Supported cipher 00-0f-ac:4 nl80211: Supported cipher 00-0f-ac:6 nl80211: Using driver-based off-channel TX nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1 nl80211: Use separate P2P group interface (driver advertised support) nl80211: Enable multi-channel concurrent (driver advertised support) nl80211: use P2P_DEVICE support nl80211: key_mgmt=0xd0f enc=0x10f auth=0x7 flags=0x20000003a04fac8 rrm_flags=0x0 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=5000 max_scan_ssids=10 nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211: Subscribe to mgmt frames with non-AP handle 0x55a58cb300 nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x55a58cb300 match=0300 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=176): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 03 00 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0104 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 01 04 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=040a multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 04 0a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=040b multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 04 0b nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=040c multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 04 0c nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=040d multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 04 0d nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=090a multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 09 0a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=090b multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 09 0b nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=090c multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 09 0c nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=090d multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 09 0d nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0409506f9a09 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=7f506f9a09 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0409506f9a1a multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 1a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0800 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 08 00 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0801 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 08 01 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=12 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=1): 12 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=06 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=1): 06 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0a07 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 0a 07 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0a11 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 0a 11 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0a0b multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 0a 0b nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0a1a multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 0a 1a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=1101 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 11 01 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=1102 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 11 02 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0505 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 05 05 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=0500 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 05 00 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=1301 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 13 01 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=1305 multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=2): 13 05 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55a58cb300 match=7e506f9a1a multicast=0 nl80211: kernel reports: Match already configured nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress) nl80211: Register frame match - hexdump(len=5): 7e 50 6f 9a 1a nl80211: Failed to register Action frame processing - ignore for now rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0 netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT) Add interface wlan0 to a new radio phy0 nl80211: Regulatory information - country=GB (DFS-ETSI) nl80211: 2400-2483 @ 40 MHz 20 mBm nl80211: 5150-5250 @ 80 MHz 23 mBm (no outdoor) nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS) nl80211: 5470-5730 @ 160 MHz 26 mBm (DFS) nl80211: 5725-5850 @ 80 MHz 23 mBm (no outdoor) nl80211: 5925-6425 @ 160 MHz 23 mBm (no outdoor) nl80211: 57000-71000 @ 2160 MHz 40 mBm nl80211: Added 802.11b mode based on 802.11g information nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED] nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED] wlan0: Own MAC address: 2c:cf:67:9e:52:16 wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0 key_flag=0x10 nl80211: DEL_KEY broadcast key wlan0: RSN: flushing PMKID list in the driver nl80211: Flush PMKIDs TDLS: TDLS operation not supported by driver TDLS: Driver uses internal link setup TDLS: Driver does not support TDLS channel switching wlan0: WPS: UUID based on MAC address: d14f1b81-68a1-5bfe-a2a8-7a90d4ff319a ENGINE: Loading builtin engines ENGINE: Loading builtin engines EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized nl80211: Skip set_supp_port(unauthorized) while not associated EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED Using existing control interface directory. ctrl_interface_group=106 (from group name 'netdev') ctrl_iface bind(PF_UNIX) failed: Address already in use ctrl_iface exists and seems to be in use - cannot override it Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore Failed to initialize control interface 'DIR=/run/wpa_supplicant GROUP=netdev'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again. Failed to add interface wlan0 nl80211: Getting wowlan status nl80211: Getting wowlan status failed wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=DISCONNECTED TDLS: Tear down peers nl80211: Data frame filter flags=0x0 wlan0: State: DISCONNECTED -> DISCONNECTED nl80211: Set wlan0 operstate 0->0 (DORMANT) netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT) EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 QM: Clear all active DSCP policies wlan0: CTRL-EVENT-DSCP-POLICY clear_all wlan0: WPA: Clear old PMK and PTK wlan0: Cancelling delayed sched scan wlan0: Cancelling scan request wlan0: Cancelling authentication timeout Off-channel: Clear pending Action frame TX (pending_action_tx=(nil) nl80211: Data frame filter flags=0x0 Off-channel: Action frame sequence done notification: pending_action_tx=(nil) drv_offchan_tx=1 action_tx_wait_time=0 off_channel_freq=0 roc_waiting_drv_freq=0 QM: Clear all active DSCP policies wlan0: CTRL-EVENT-DSCP-POLICY clear_all Remove interface wlan0 from radio phy0 Remove radio phy0 nl80211: deinit ifname=wlan0 disabled_11b_rates=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211: Unsubscribe mgmt frames handle 0x888888dd2d043b89 (mode change) ``` ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [19 February 2025 00:52 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/13 "2025-02-19T00:52:16Z")
This is the result of the link that was posted: ```auto root@DietPi:~# modprobe brcmfmac roamoff=1 feature_disable=0x82000 root@DietPi:~# wpa_supplicant -i wlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf Successfully initialized wpa_supplicant nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured ctrl_iface exists and seems to be in use - cannot override it Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore Failed to initialize control interface 'DIR=/run/wpa_supplicant GROUP=netdev'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again. wlan0: CTRL-EVENT-DSCP-POLICY clear_all wlan0: CTRL-EVENT-DSCP-POLICY clear_all nl80211: deinit ifname=wlan0 disabled_11b_rates=0 ``` ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [19 February 2025 13:39 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/14 "2025-02-19T13:39:12Z")
> [@krtdude](#): > > ```auto > You may have another wpa_supplicant process already running or the file was > left by an unclean termination of wpa_supplicant in which case you will need > to manually remove this file before starting wpa_supplicant again. > > ``` You need to kill the existing wpa\_supplicant process before trying to run it manually. ```auto sudo killall wpa_supplicant ``` ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [21 February 2025 17:02 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/16 "2025-02-21T17:02:45Z")
[PI\_Logs2.txt](https://dietpi.com/forum/uploads/short-url/zoj3oDie1nO1EiVFEkAaCj01QBN.txt) (368.8 KB) ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [22 February 2025 17:28 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/19 "2025-02-22T17:28:27Z")
Ok no other info, just again ```auto wlan0: CTRL-EVENT-ASSOC-REJECT bssid=08:36:c9:58:a5:63 status_code=16 ``` So idk whats wrong. I asked chatgpt and it came up with another idea: > **Wi-Fi Channel Interference** > > - If the router is set to **auto-channel selection** , try manually setting it to **a different channel** (e.g., **1, 6, or 11** for 2.4 GHz). ---
**Author:** ![yakkoTDI](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/y/c77e96/32.png) [@yakkoTDI](https://dietpi.com/forum/u/yakkoTDI)\ **Post date:** [22 February 2025 19:15 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/20 "2025-02-22T19:15:04Z")
After a reboot run these commands and see if you can connect to wireless. > sudo rmmod brcmfmac > sudo modprobe brcmfmac feature\_disable=0x82000 ---
**Author:** ![krtdude](https://dietpi.com/forum/user_avatar/dietpi.com/krtdude/32/7534_2.png) [@krtdude](https://dietpi.com/forum/u/krtdude)\ **Post date:** [23 February 2025 04:12 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/21 "2025-02-23T04:12:14Z")
I’ve already changed through all the channels that my router does. ---
**Author:** ![system](https://dietpi.com/forum/uploads/default/original/1X/7e1021de2213860bce185915ce2c1786e56490ec.png) [@system](https://dietpi.com/forum/u/system)\ **Post date:** [20 August 2025 16:12 UTC](https://dietpi.com/forum/t/zero-2-w-cannot-connect-to-wifi/22792/22 "2025-08-20T16:12:23Z")
This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.