summaryrefslogtreecommitdiff
path: root/target/linux/mvebu/patches-4.9
diff options
context:
space:
mode:
authorMatthias Schiffer <mschiffer@universe-factory.net>2017-05-13 16:17:44 +0200
committerMatthias Schiffer <mschiffer@universe-factory.net>2017-05-13 17:12:54 +0200
commit1a16cb9c67f0d2c530914aec31c721b75f03a908 (patch)
tree7bb379b72b5d34cfdf950c98a312ec56d62f95e4 /target/linux/mvebu/patches-4.9
parent5e481881d7abd814abbf40a046be90cbaf835e72 (diff)
downloadmtk-20170518-1a16cb9c67f0d2c530914aec31c721b75f03a908.zip
mtk-20170518-1a16cb9c67f0d2c530914aec31c721b75f03a908.tar.gz
mtk-20170518-1a16cb9c67f0d2c530914aec31c721b75f03a908.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 'target/linux/mvebu/patches-4.9')
0 files changed, 0 insertions, 0 deletions