> Could you do trace and sniffer at the same time? According to the trace > there was no authentication frame from the AP. In the sniffer capture it > _is_ there, of course, but I'd like to look at the timing. Ok, I did another capture. 1. iwd only knows credentials for a single SSID: kepler_test 2. kepler_test is the only SSID broadcasting on 6GHz channel 37 (or any 6GHz channel) 3. I captured 802.11 frames using a second device 4. I did a trace on the client in question 5. I captured dmesg and iwd logs 6. All captures were done simultaneously All attached to capture2.tar. Contents: capture2/dmesg2.txt : dmesg capture2/iwd_log2.txt : iwd log using IWD_SAE_DEBUG=1 capture2/trace2.dat : trace-cmd (iwlwifi, mac80211, cfg80211, iwlwifi_msg) capture2/iwd_main.conf : iwd config (/etc/iwd/main.conf) capture2/kepler_test.psk : ssid config for iwd (/var/lib/kepler_test.psk) capture2/capture2.pcapng : the external 802.11 frame capture I disabled 5Ghz via BandModifier5GHz=0.0 (couldn't disable 2.4GHz as iwd then complains about not being able to disable both) One note about the client: It's running an Intel N100, so it's probably on the lower end of devices that will be running a modern wifi 6e card. So this increases the chances that the AP will send it's confirm before the client will. Best Regards Jan
Attachment:
capture2.tar
Description: Unix tar archive
