Re: Problem with STA re-association when AP changes capabilities.

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

 



On Tue, 2019-02-19 at 14:41 -0800, Ben Greear wrote:

> If I then quickly restart the AP configured for /n mode, I would expect that the STA would
> then connect with HT enabled.  However, what I notice is that it stays at /a rates.  Probably
> this is because it did not rescan.  Here is an iw event log of this:

[snip]

> So, is it OK that the station did not re-scan the AP and/or automatically refresh its beacon
> info with the new capabilities?

I'd argue that's a case of "don't do that, then" :-)

How often would we expect that to happen in the real world? The spec
sort of assumes that capabilities etc. are static, so changing them
within a few hundred milliseconds or so is not something that would be
expected.

Just give it a new BSSID when you do this?

johannes


_______________________________________________
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