[v2] hostapd: avoid unnecessary beacon update for co-location

[Jouni Malinen]

On Wed, Nov 01, 2023 at 05:00:00PM +0800, Michael-CY Lee wrote:
> When it comes to set some BSS's beacon, there are two reasons to
> update the beacon of co-located hostapd_iface(s) at the same time:
> 1. 6 GHz out-of-band discovery
> 2. MLD operational parameters update
> 
> BSS load update is unrelated with the above two reasons, and therefore
> is not the case to update beacon for co-location.
> Moreover, updating beacon for co-location when BSS load update makes
> hostapd set beacon too frequently, which makes hostapd busy setting
> beacon in a multi-BSS case.
> 
> This patch adds an new function to update beacon only for current BSS
> and uses the function during BSS load update.

Thanks, applied.

> v2: We did not notice that the FILS discovery frame is update during
> the beacon update. Also, RNR element is included in the FILS discovery
> frame only when the BSS is 6 GHz standalone.
> (BTW, we did not see this constraint about RNR in the FILS discovery frame
> in 802.11 Standard, so perhaps it can be refactored.)

I'm open to other changes or cleanup in this area as long as the
functionality remains valid for all the use cases.
 
-- 
Jouni Malinen                                            PGP id EFC895FA