aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/combined-ext-image.sh
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@nbd.name>2022-09-06 12:12:12 +0200
committerFelix Fietkau <nbd@nbd.name>2022-09-06 12:18:52 +0200
commitab61232b0abe2158c346f9fbf17f34e64de5288a (patch)
tree4feb9cd2271b8749466c0c7e7500dac6e809148b /scripts/combined-ext-image.sh
parent39c115028ac5293037f58a5b6751574a1f951d8c (diff)
downloadupstream-ab61232b0abe2158c346f9fbf17f34e64de5288a.tar.gz
upstream-ab61232b0abe2158c346f9fbf17f34e64de5288a.tar.bz2
upstream-ab61232b0abe2158c346f9fbf17f34e64de5288a.zip
hostapd: rename hostapd multicast_to_unicast option to multicast_to_unicast_all
There are two feature currently altered by the multicast_to_unicast option. 1. bridge level multicast_to_unicast via IGMP snooping 2. hostapd/mac80211 config multicast_to_unicast setting The hostapd/mac80211 setting has the side effect of converting *all* multicast or broadcast traffic into per-station duplicated unicast traffic, which can in some cases break expectations of various protocols. It also has been observed to cause ARP lookup failure between stations connected to the same interface. The bridge level feature is much more useful, since it only covers actual multicast traffic managed by IGMP, and it implicitly defaults to 1 already. Renaming the hostapd/mac80211 option to multicast_to_unicast_all should avoid unintentionally enabling this feature Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 09ea1db93b53d2c1e4a081f20fbbddd4bffd451d)
Diffstat (limited to 'scripts/combined-ext-image.sh')
0 files changed, 0 insertions, 0 deletions