diff options
| author | Matthias Schiffer <mschiffer@universe-factory.net> | 2017-05-13 16:17:44 +0200 |
|---|---|---|
| committer | Jo-Philipp Wich <jo@mein.io> | 2017-05-27 14:24:13 +0200 |
| commit | 4bd3b8f8b0bc97cb7de4242b4f67c57ea8296de5 (patch) | |
| tree | 36e3029732e75497c50fc1bd22fdb3263f1c78fe /BSDmakefile | |
| parent | e194e1b3c838a301178effb639804c28fe67354d (diff) | |
| download | mtk-20170518-4bd3b8f8b0bc97cb7de4242b4f67c57ea8296de5.zip mtk-20170518-4bd3b8f8b0bc97cb7de4242b4f67c57ea8296de5.tar.gz mtk-20170518-4bd3b8f8b0bc97cb7de4242b4f67c57ea8296de5.tar.bz2 | |
mac80211, hostapd: always explicitly set beacon interval
One of the latest mac80211 updates added sanity checks, requiring the
beacon intervals of all VIFs of the same radio to match. This often broke
AP+11s setups, as these modes use different default intervals, at least in
some configurations (observed on ath9k).
Instead of relying on driver or hostapd defaults, change the scripts to
always explicitly set the beacon interval, defaulting to 100. This also
applies the beacon interval to 11s interfaces, which had been forgotten
before. VIF-specific beacon_int setting is removed from hostapd.sh.
Fixes FS#619.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Diffstat (limited to 'BSDmakefile')
0 files changed, 0 insertions, 0 deletions