Re: [PATCH 5/6] AP: Add support for co-located AP configuration

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

 



On 6/19/19 5:49 AM, Andrei Otcheretianski wrote:
> +               if (!h || !h->started || !h->iface->current_mode || h == hapd)
> +                       continue;

Hi Andrei, a few questions on when RnR element should be added:
- it should only be added to 2.4GHz and 5GHz BSS frames as far as I know.
- shouldn't we only add RnR for 6Ghz interfaces that are beaconing? That 
is, should we trace when interface start or stop beaconing (I believe 
!h->started is not enough)
- should we track channel changes? Update RnR if interface switches away 
from 6GHz channel, or switches to 6Ghz from other band.
- would it make sense for hostapd to automatically add RnR elements for 
any beaconing 6GHz BSS to any 2.4GHz and 5GHz IEs so that user won't 
have to specify co0located interfaces in configuration? What does spec 
says, is RnR element mandatory in co-located configuration, or it is 
optional?
_______________________________________________
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