Re: [PATCH] wnm_ap: optional disassociation for bss_tm_req

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 30, 2024 at 10:20:17PM +0100, Nils Hendrik Rottgardt wrote:
> To give controllers like usteer or DAWN the opportunity to disassociate
> with the right reason code and also avoid a disassociation if it is
> not neccessary.

For the "right reason code" part, I would prefer to have an option for
such external components to provide that reason code with the command to
send the BSS Transition Management Request frame instead of expecting
them to handle the timeout.

For the "avoid a disassociation part", why would the AP send a
notification of imminent disassociation if it is not going to
disassociate the STA? If I remember correctly, the disassociation is
actually required to happen at least for some cases, so it would be good
to understand why there would be desire to avoid that.

Furthermore, this patch does not actually provide any means for using
this proposed functionality since nothing here calls
wnm_send_bss_tm_req_disassoc() with disassoc = false. Even if such
option were added, it should also be noted that set_disassoc_timer()
does two things: removes a cached PMKSA for the STA (to force new
association) and starts a timer to disassociate the STA. Is there really
need to skip that first part as well?

-- 
Jouni Malinen                                            PGP id EFC895FA

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux