#
✕ nick:DannyB
#asahi-alt · 2023-11-29 16:43
DannyB * to be processed in frame_xchg_tx_cb if we were
#asahi-alt · 2023-11-29 16:43
DannyB * called before it (happens on brcmfmac).
#asahi-alt · 2023-11-29 16:43
DannyB * Save the information about the frame's ACK status
#asahi-alt · 2023-11-29 16:43
DannyB" /*
#asahi-alt · 2023-11-29 16:43
DannyB */
#asahi-alt · 2023-11-29 16:43
DannyBfor brcmfmac
#asahi-alt · 2023-11-29 16:42
DannyBI also note the exact sequence in the log seems to be special cased in a weird way in iwd
#asahi-alt · 2023-11-29 16:34
DannyBthat i cna write patches for and see what happens
#asahi-alt · 2023-11-29 16:34
DannyBSo this log helps, or at least gives issues to run down
#asahi-alt · 2023-11-29 16:30
DannyBha
#asahi-alt · 2023-11-29 13:39
DannyB(they actually went backwards in firmware versions - they are now shipping an older branch than they were before, so maybe they found this bug?)
#asahi-alt · 2023-11-29 13:39
DannyBthat i can give you to try
#asahi-alt · 2023-11-29 13:38
DannyBapple also has newer firmware for all of these chips than we are shipping
#asahi-alt · 2023-11-29 13:38
DannyBt
#asahi-alt · 2023-11-29 13:37
DannyBcan you generate logs with iwd -d the next time you can reproduce?
#asahi-alt · 2023-11-29 13:36
DannyBso either the caps are wrong (which is one of the patches above), or the supplicant gets a weird result from the driver it's not telling us about
#asahi-alt · 2023-11-29 13:36
DannyBand can't get my wifi to disconnect the same way ;(
#asahi-alt · 2023-11-29 13:36
DannyBI have tried this on 4 different brands of wifi networks, with fast roaming enabled/disabled, neighbor reporting, you name it
#asahi-alt · 2023-11-29 13:35
DannyBbut it's not obvious at all why
#asahi-alt · 2023-11-29 13:35
DannyBand we do
#asahi-alt · 2023-11-29 13:35
DannyBIE the auth and connect is suceeding, it reports success to supplicant, and then the supplicant says "okay please deauth and disconnect"
#asahi-alt · 2023-11-29 13:35
DannyBbut if so, it's not obvious from the logs we have
#asahi-alt · 2023-11-29 13:35
DannyBit may be the driver is telling it something weird in one case but not the other
#asahi-alt · 2023-11-29 13:34
DannyBThe weird thing is that in all cases this is connecting, and then the supplicant decides to disconnect. It would be good to try to get enough supplicant debugging to see why it tries to disconnect
#asahi-alt · 2023-11-29 13:26
DannyBWhen using hardware roam a349ce depends on the station reporting the right caps to determine if the port is authorized
#asahi-alt · 2023-11-29 13:24
DannyBI can believe fast roaming is broken somehow, if so, reverting a349c should fix it
#asahi-alt · 2023-11-29 13:23
DannyBand never have been
#asahi-alt · 2023-11-29 13:23
DannyBInterestingly the code paths aren't different for these chips
#asahi-alt · 2023-11-29 13:22
DannyB4388/4
#asahi-alt · 2023-11-29 13:20
DannyBdriver identifies as using SAE offload, daemon shows point as WPA3-SAE
#asahi-alt · 2023-11-29 13:20
DannyBIt's WPA3-Personal (IE SAE and not PSK)
#asahi-alt · 2023-11-29 13:15
DannyBand maybe 38b690940fe07348f64bd8507b8a32d01a5edbae
#asahi-alt · 2023-11-29 13:14
DannyB4c411956766690f31c5b65d8fe24235d311b8595
#asahi-alt · 2023-11-29 13:13
DannyBa349ce53cd28d51059ccda826ba133af52995982
#asahi-alt · 2023-11-29 13:13
DannyBand testing
#asahi-alt · 2023-11-29 13:13
DannyBi would try reverting the following patches from asahi-wip
#asahi-alt · 2023-11-29 13:12
DannyBIn all of these logs the supplicant is the thing requesting the disconnect, which is weird
#asahi-alt · 2023-11-29 13:12
DannyBI can connect to a 2.4ghz, 5hgz, and 6ghz wpa-3 only point, a wpa-2/wpa-3 mixed point, and a wpa-2 only point.
#asahi-alt · 2023-11-28 20:16
DannyBI can't see anything wrong in the driver logs - we are setting the key right, we are authing and reporting success, etc
#asahi-alt · 2023-11-28 20:15
DannyBSupplicant asks us to deauth and disconnect
#asahi-alt · 2023-11-28 20:15
DannyBSupplicant asks us to change station
#asahi-alt · 2023-11-28 20:15
DannyB...
#asahi-alt · 2023-11-28 20:15
DannyBSupplicant reports connect success
#asahi-alt · 2023-11-28 20:15
DannyBsupplicant tells driver to auth
#asahi-alt · 2023-11-28 20:15
DannyBdriver auth and report success
#asahi-alt · 2023-11-28 20:15
DannyBthe exact sequence of events post-patches is:
#asahi-alt · 2023-11-28 20:13
DannyBbecause i doubt there are local patches tof edora that affect this
#asahi-alt · 2023-11-28 20:12
DannyBso it's extra weird
#asahi-alt · 2023-11-28 20:12
DannyBjanneg: There is nothing obvious in why the wpa_supplicant is choosing to disconnect in his case. With the patches (except the last one), it connects successfully, we report a successful connection, then the *suppllicant* decides to disconnect us anyway and we disconnect. it is not the driver deciding to disconnect on its own. The reason it gives us "DEAUTH_LEAVING" - IE it is choosing to leave this BSS for some other
#asahi-alt · 2023-11-28 19:01
DannyBhttps://gist.github.com/dberlin/3cd1f07383d98b6fd7e5eb97f4e1faaa

plus ›