Wireless with client mode using peap will lost link an hour later

[fengchen_ow]

Sat Jul  4 22:00:57 2020 daemon.notice wpa_supplicant[1213]: wlan0: WPA: Group rekeying completed with b0:6e:**:9b:19:bc [GTK=CCMP]
Sat Jul  4 22:04:39 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Sat Jul  4 22:04:39 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
Sat Jul  4 22:04:39 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
Sat Jul  4 22:04:40 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='C=FR, ST=Radius, O=Example Inc., CN=Example Server Certificate/emailAddress=admin@example.org' hash=799c714a9acf1f8bee97a77e8cfa224a6f272af423444ce05da83713e4e7c253
Sat Jul  4 22:04:40 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='C=FR, ST=Radius, L=Somewhere, O=Example Inc., CN=Example Certificate Authority/emailAddress=admin@example.org' hash=513349321e2f34aff30fba4cde36632ee3148b33595fa71c95c46d98fb8bde38
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: EAP-MSCHAPV2: Authentication succeeded
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: wlan0: PMKSA-CACHE-REMOVED b0:6e:**:9b:19:bc 0
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: wlan0: PMKSA-CACHE-ADDED b0:6e:**:9b:19:bc 0
Sat Jul  4 22:04:42 2020 daemon.notice wpa_supplicant[1213]: wlan0: WPA: Key negotiation completed with b0:6e:**:9b:19:bc [PTK=CCMP GTK=CCMP]
Sat Jul  4 22:04:42 2020 kern.warn kernel: [ 8344.733132] Rekeying PTK for STA b0:6e:**:9b:19:bc but driver can't safely do that.
Sat Jul  4 22:04:42 2020 kern.info kernel: [ 8344.733232] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0  arvif->paused: 0x0
Sat Jul  4 22:04:46 2020 kern.info kernel: [ 8348.765918] wlan0: disassociated from b0:6e:**:9b:19:bc (Reason: 2=PREV_AUTH_NOT_VALID)
Sat Jul  4 22:04:46 2020 daemon.notice netifd: Network device 'wlan0' link is down
Sat Jul  4 22:04:46 2020 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sat Jul  4 22:04:46 2020 kern.info kernel: [ 8348.778048] ath10k_pci 0000:00:00.0: mac flush null vif, drop 0 queues 0xffff
Sat Jul  4 22:04:46 2020 daemon.notice wpa_supplicant[1213]: wlan0: CTRL-EVENT-DISCONNECTED bssid=b0:6e:**:9b:19:bc reason=2

[fengchen_ow]

Sat Jul  4 19:40:32 2020 kern.info kernel: [   13.614355] ath10k 5.1 driver, optimized for CT firmware, probing pci device: 0x3c.
Sat Jul  4 19:40:32 2020 user.info kernel: [   13.626261] urngd: v1.0.2 started.
Sat Jul  4 19:40:32 2020 kern.info kernel: [   13.635909] ath10k_pci 0000:00:00.0: enabling device (0000 -> 0002)
Sat Jul  4 19:40:32 2020 kern.info kernel: [   13.642444] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
Sat Jul  4 19:40:32 2020 kern.err kernel: [   14.340046] firmware ath10k!fwcfg-pci-0000:00:00.0.txt: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   14.780138] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   15.115743] firmware ath10k!QCA988X!hw2.0!ct-firmware-5.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   15.329540] firmware ath10k!QCA988X!hw2.0!ct-firmware-2.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   15.543622] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   15.757088] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   15.972262] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.err kernel: [   16.186254] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.info kernel: [   16.198954] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Sat Jul  4 19:40:32 2020 kern.info kernel: [   16.208354] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Sat Jul  4 19:40:32 2020 kern.info kernel: [   16.220794] ath10k_pci 0000:00:00.0: firmware ver 10.1-ct-8x-__fW-022-538f0906 api 2 features wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT crc32 e1c91a74
Sat Jul  4 19:40:32 2020 kern.err kernel: [   16.468867] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
Sat Jul  4 19:40:32 2020 kern.info kernel: [   16.478172] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Sat Jul  4 19:40:32 2020 kern.warn kernel: [   17.422276] ath10k_pci 0000:00:00.0: unsupported HTC service id: 1536
Sat Jul  4 19:40:32 2020 kern.warn kernel: [   17.429115] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sat Jul  4 19:40:32 2020 kern.info kernel: [   17.446719] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
Sat Jul  4 19:40:32 2020 kern.info kernel: [   17.453064] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
Sat Jul  4 19:40:32 2020 kern.info kernel: [   17.461218] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 20984 iram: 25656'
Sat Jul  4 19:40:32 2020 kern.info kernel: [   17.515039] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 2 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
Sat Jul  4 19:40:32 2020 kern.info kernel: [   17.529314] ath10k_pci 0000:00:00.0: NOTE:  Firmware DBGLOG output disabled in debug_mask: 0x10000000
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.638484] ath: EEPROM regdomain sanitized
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.638493] ath: EEPROM regdomain: 0x64
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.638496] ath: EEPROM indicates we should expect a direct regpair map
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.638514] ath: Country alpha2 being used: 00
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.638518] ath: Regpair used: 0x64
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.727524] ath: EEPROM regdomain sanitized
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.727534] ath: EEPROM regdomain: 0x64
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.727538] ath: EEPROM indicates we should expect a direct regpair map
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.727557] ath: Country alpha2 being used: 00
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.727560] ath: Regpair used: 0x64
Sat Jul  4 19:40:32 2020 kern.debug kernel: [   17.744736] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'

[Ramon]

This is a known bug. "Rekeying PTK for STA XX:XX:XX:XX:XX:XX but driver can't safely do that."
If you send "high volume" of traffic while rekeying the keys get messed up and the wrong keys get used for decoding/encoding, resulting in a lock-up until the next rekeying. With low/no traffic it will go ok.

See:

Rekeying Issue - "driver can't safely do that."

You are next to sure using WPA-EAP (WPA Enterprise) which is by default re-authenticating every hour. If not you must have set wpa_pair_rekey=3600 or the connected stations must have such a setting, both not very likely. It has nothing to do with 802.11[w,r]. The warning can only be triggered wen installing a PTK for a station (MAC) which already has a PTK active. Setting eap_reauth_period=0 is probably the proper work around for now when you are not sure all devices (AP and all connecting STA…

[alexw65500]

Ath10k cards are still triggering the warning but at least my r7800 router is handling PTK0 rekeys correctly. When the Wlan stops working around the rekey warning it's next to sure a PTK rekey problem but equally sure it's not the ath10k card. So I would expect your client to use a broken card/driver.

That said (trying) to disable rekeying on the AP is still your best bet. When the client STA is running Linux there may be a way to fix it - especially when up the card is using mac80211 - but if not you are at the mercy of the vendor to fix the driver/card.

[Ramon]

I also sometimes get the warning. I set the time to zero to disable rekeying, but apparently my android phone still requests rekeying. Not sure if it can potentially still freeze the communication. (I have 2x r7800).