I was pinged about bug report on OpenWRT [0] about b43 not setting beacon interval for AP mode when restarting hostapd. You can see my comment in this bug report for some details. It seems that starting hostapd calls: ieee80211_ops->start In normal situation this is followed by: ieee80211_ops->bss_info_changed with BSS_CHANGED_BEACON_INT However I suspect that if device was already used earlier (so this is restart, not cold start), driver does not receive BSS_CHANGED_BEACON_INT or bss_info_changed is not called at all. Is this possible mac80211 caches beacon interval and does not flush it on hardware restart? I suspect this part of code to do the caching: http://lxr.free-electrons.com/source/net/mac80211/cfg.c#L452 How does it work? BSS_CHANGED_BEACON_INT is passed only: if (params->interval && (sdata->vif.bss_conf.beacon_int != params->interval)) Performing: grep "\.interval" ./net/mac80211/* grep "\->interval" ./net/mac80211/* does not give anything interesting. It seems nl80211.c is involved here. Cold someone take a look at this? [0] https://dev.openwrt.org/ticket/8033 -- RafaÅ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
