On Mon, Jan 02, 2023 at 11:17:26AM +0200, Andrei Otcheretianski wrote: > The flags that indicate that a channel is allowed for 80/160MHz usage > are divided according to the position of the control channel (e.g., > HOSTAPD_CHAN_VHT_10_70, HOSTAPD_CHAN_VHT_30_50 etc.). > > However, the position of the control channel does not add any extra > regulatory information because when trying to use a 80/160MHz channel > all the desired bandwidth has to be allowed for 80/160MHz usage, > regardless of the control channel position. > > In addition, these flags are set only if the driver reports one > regulatory rule that allows the entire 80/160MHz bandwidth. > However, even when a 80/160MHz channel is allowed, in some cases the > bandwidth will be split into several regulatory rules because > different segments of the bandwidth differ in other flags (that don't > affect the use of the bandwidth for VHT channels). So, in such cases > these flags will not be set, although VHT channels are allowed. > > As the result, VHT channels will not be used although they are allowed > by the regulatory domain. > > Fix this by introducing new flags that indicate if a 20MHz channel is > allowed to be used as part of a wider (80/160MHz) channel. > The new flags are set for each 20MHz channel independently and thus > will be set even if the regulatory rules for the bandwidth are split. > > A 80/160MHz channel is allowed if all its 20MHz sub-channels are > allowed for 80/160MHz usage. Thanks, applied. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
