Hi All
The reason code from deauth/dis-assoc frames are sent over DBUS as a
part of "PropertiesChanged" DBUS signal but not the status code
(especially failure ones) from assoc response.
I am working on some changes in connman to take care of enterprise
roaming case (when AP is denying association with reason code 17
hoping client would move to a different AP). This is for load
balancing and/or band steering. Idea is that connman gets the reason
code as a part of disconnect notification and acts differently.
Is there any objection in not sending the assoc response status code
over DBUS. I was thinking of adding something like this in
ASSOC_REJECT handler:
@@ -2496,6 +2496,8 @@ void wpa_supplicant_event(void *ctx, enum
wpa_event_type event,
wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_ASSOC_REJECT
"status_code=%u",
data->assoc_reject.status_code);
+ wpa_s->disconnect_reason = data->assoc_reject.status_code;
+ wpas_notify_disconnect_reason(wpa_s);
if (wpa_s->drv_flags & WPA_DRIVER_FLAGS_SME)
sme_event_assoc_reject(wpa_s, data);
else {
Regards
Naveen
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
