[PATCH] hostapd: add check for overlapping legacy BSS
Mon May 12 08:28:26 PDT 2014
On Sat, May 03, 2014 at 07:56:07PM +0530, Rajkumar Manoharan wrote:
> Before bringing up 20/40 MHz BSS, a scan is triggered to identify
> overlapping BSS. If there is any legacy BSS present within the affected
> range, then 40 MHz operation should be rejected and BSS should start
> with 20 MHz.
Why would we do that? What's so different about legacy (as in "non-HT"
in this case) BSS and HT 20 MHz BSS that would justify such difference?
Can you please point me to the rule in the IEEE Std 802.11-2012 20/40
coex requirements that this patch implements?
Jouni Malinen PGP id EFC895FA
More information about the Hostap