So the present >OpenWrt< multicast_to_unicast_all
setting was renamed from multicast_to_unicast
. Refs:
- https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ab61232b0abe2158c346f9fbf17f34e64de5288a
- https://github.com/openwrt/luci/commit/6069f4f228305e3e0b59cb6deb9de9934aa68b6f
- https://github.com/openwrt/openwrt/commit/09ea1db93b53d2c1e4a081f20fbbddd4bffd451d
However, the OpenWrt multicast_to_unicast_all
setting is actually toggling the hostapd multicast_to_unicast
option. Based upon hostapd: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master/hostapd/hostapd.conf
(Sorry for the Android source link. Will try to find a different reference if possible.)
The default multicast_to_unicast
setting is '0':
# Multicast to unicast conversion
# Request that the AP will do multicast-to-unicast conversion for ARP, IPv4, and
# IPv6 frames (possibly within 802.1Q). If enabled, such frames are to be sent
# to each station separately, with the DA replaced by their own MAC address
# rather than the group address.
#
# Note that this may break certain expectations of the receiver, such as the
# ability to drop unicast IP packets received within multicast L2 frames, or the
# ability to not send ICMP destination unreachable messages for packets received
# in L2 multicast (which is required, but the receiver can't tell the difference
# if this new option is enabled).
#
# This also doesn't implement the 802.11 DMS (directed multicast service).
#
#multicast_to_unicast=0
Just to be very clear, the quoted selection of my previous post that you selected seems to indicate that I am generally suggesting this should be disabled. However, the larger context is that I have historically enabled this setting, but given the current issue it seems to play some part in (Mt798x-wmac 18000000.wifi: Message xxxxxxxx (seq 5) timeout - #6 by _FailSafe), I am recommending it be disabled until the root of the issue can be resolved. At least rule out this setting instead of disabling bridger + WED as a first-line-of-defense when client connectivity issues are presenting.