On Wed, Sep 08, 2021 at 05:18:55PM +0800, Ryder Lee wrote: > Enhance the possible values for he_bss_color. Anything greater than 63 will > make hostapd choose a random color. What's the use case for this? Isn't the initial BSS color supposed to be selected based on what BSS colors are in use by neighboring OBSSs (see IEEE Std 802.11ax-2021, 26.17.3.2)? If that more complete implementation looking at neighboring OBSSs is not added, would the automatic initialization to a random value be sufficient for now? https://w1.fi/cgit/hostap/commit/src?id=41ec97cd09486a6bda21f5f5b89e5242e6ade2a2 > -# he_bss_color: BSS color (1-63) > +# he_bss_color: > +# 0 = disable > +# 1-63 = pre-defined color > +# 64+ = random color > #he_bss_color=1 Is it really expected to be possible to configure the BSS color to be hardcoded to be disabled? In addition, that use of multiple different values to indicate a random color feels quite strange. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
