TP-Link Archer C7 with wpa-supplicant error "Unknown event 37"

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi all,
I have a TP-Link Archer C7 v5. I managed to properly install OpenWRT v23.05.02.
I would like this router to connect to the wireless network of our offices and share connectivity with LAN devices. The Wi-Fi is protected with WPA2 Enterprise.
I did remove wpad and replace it by wpa_supplicant. I configure everything in LuCI but I can"t manage to establish a connection. It seems that the router is able to reach for the AP but the authentication is failing.

In the system logs, this is what I get.

Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: SME: Trying to authenticate with be:15:54:a8:8d:c2 (SSID='WOJO' freq=5260 MHz)
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.359768] phy0-sta0: authenticate with be:15:54:a8:8d:c2
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.374646] phy0-sta0: send auth to be:15:54:a8:8d:c2 (try 1/3)
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.382785] phy0-sta0: authenticated
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: Trying to associate with be:15:54:a8:8d:c2 (SSID='WOJO' freq=5260 MHz)
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.407131] phy0-sta0: associate with be:15:54:a8:8d:c2 (try 1/3)
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.415092] phy0-sta0: RX AssocResp from be:15:54:a8:8d:c2 (capab=0x1511 status=0 aid=4)
Thu Apr 11 16:46:26 2024 kern.warn kernel: [   52.425948] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Thu Apr 11 16:46:26 2024 kern.warn kernel: [   52.433263] ath10k_pci 0000:00:00.0: failed to enable peer stats info: -122
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.440624] phy0-sta0: associated
Thu Apr 11 16:46:26 2024 daemon.notice netifd: Network device 'phy0-sta0' link is up
Thu Apr 11 16:46:26 2024 daemon.notice netifd: Interface 'wwan' has link connectivity
Thu Apr 11 16:46:26 2024 daemon.notice netifd: Interface 'wwan' is setting up now
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: Associated with be:15:54:a8:8d:c2
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-EAP-STARTED EAP authentication started
Thu Apr 11 16:46:26 2024 kern.debug kernel: [   52.476302] phy0-sta0: Limiting TX power to 20 (23 - 3) dBm as advertised by be:15:54:a8:8d:c2
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: Unknown event 37
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: Unknown event 37
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Thu Apr 11 16:46:26 2024 daemon.notice netifd: wwan (2679): udhcpc: started, v1.36.1
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.640879] phy0-sta0: deauthenticated from be:15:54:a8:8d:c2 (Reason: 23=IEEE8021X_FAILED)
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.649604] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0  arvif->paused: 0x0
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-DISCONNECTED bssid=be:15:54:a8:8d:c2 reason=23
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: phy0-sta0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WOJO" auth_failures=1 duration=10 reason=AUTH_FAILED
Thu Apr 11 16:46:26 2024 daemon.notice wpa_supplicant[1495]: BSSID be:15:54:a8:8d:c2 ignore list count incremented to 2, ignoring for 10 seconds
Thu Apr 11 16:46:26 2024 kern.info kernel: [   52.689090] ath10k_pci 0000:00:00.0: mac flush null vif, drop 0 queues 0xffff
Thu Apr 11 16:46:26 2024 daemon.notice netifd: wwan (2679): udhcpc: broadcasting discover
Thu Apr 11 16:46:27 2024 daemon.notice netifd: Network device 'phy0-sta0' link is down
Thu Apr 11 16:46:27 2024 daemon.notice netifd: Interface 'wwan' has link connectivity loss

I can't find nor understand what "Unknown Event 37" means.

Does anyone has an idea?
Thanks in advance.

2

Event 37 means channel survey is in progress.
Particular Wave1 ath10k does not support background surveys, so it blocks wwan for that minute. One way out is to use fixed non-dfs channel in 5ghz or use 2.4ghz ath9k for wwan. Swapping -ct to non-ct kmod and firmware both at once may or may not help.

1 Like
3

Hi brada4,
Thanks a lot for your feedback.
I followed you until "Swapping -ct to non-ct..." :wink:
Does it mean I need to replace the Wireless driver? Removing the "-ct" one and replacing with the "normal" one?

image
image1016×221 17.6 KB

I'll try this right away :slight_smile:

Cheers.

4

It's a bad idea, doing it that way, you'll lose flash space.

Build a new image using https://firmware-selector.openwrt.org/, with the packages swapped out.

7

Very good point, I'm doing this right now :wink:

8

Or install attended sysupgrade and reclaim flash space with next major release using firmware selector :wink:

1 Like
9

Not only kmod but also ath10k-firmware-?????-ct -> no ct

1 Like
10

I'm currently travelling abroad. I'll test this when I'll be back at the office this Friday and keep you posted. Thanks :slight_smile:

11

I'm actually having this problem on a Comfast E314N running 23.05.1 in STA mode talking to an access point also running OpenWRT (unknown version, older). That hardware is 2.4 GHz. only, with Ath9K driver. Any thoughts?

12

The message says background radio survey by hostapd is running. Sometimes it is not that background... But message itself is harmless.

1 Like