On Tue, Nov 20, 2018 at 7:42 AM Jouni Malinen <j@xxxxx> wrote: > > On Thu, Nov 15, 2018 at 12:58:45PM -0600, Jared Bents wrote: > > Update to add ability to force ht via a hostapd config option > > and thus bypass the result of the HT_SCAN. > > What is the use case for this? IEEE 802.11 standard mandates certain > 20/40 MHz co-existence requirements and this patch seems to be providing > a mechanism to not comply with those requirements. I'm not planning on > applying changes to be non-compliant with those rules. Furthermore, this > description is not really accurate since HT can be enabled on a 20 MHz > channel. I'd assume this was supposed to say force HT40 while ignoring > what is operating on neighboring channels. > > -- > Jouni Malinen PGP id EFC895FA Hi Jouni, The use case was for a test environment where it was impossible to have the HT_SCAN pass while needing to test with 40 MHz bandwidth. Which is why I was adding it as an option that is off by default so that if the user really needs to use it but can't get a clean enough environment, they can without having to patch hostapd to bypass the results of the HT_SCAN. Thank you, Jared _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
