diff options
| author | Felix Fietkau <nbd@nbd.name> | 2022-09-06 12:12:12 +0200 |
|---|---|---|
| committer | Felix Fietkau <nbd@nbd.name> | 2022-09-06 12:15:48 +0200 |
| commit | 09ea1db93b53d2c1e4a081f20fbbddd4bffd451d (patch) | |
| tree | b95668cb06ff1e4357250d5a44dd45b4e101c01a /tools/mtools | |
| parent | 88c9056a70901577489ecdc7a25207a9b7576d6e (diff) | |
| download | upstream-09ea1db93b53d2c1e4a081f20fbbddd4bffd451d.tar.gz upstream-09ea1db93b53d2c1e4a081f20fbbddd4bffd451d.tar.bz2 upstream-09ea1db93b53d2c1e4a081f20fbbddd4bffd451d.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>
Diffstat (limited to 'tools/mtools')
0 files changed, 0 insertions, 0 deletions