You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that multicast_to_unicast and hairpin_mode are not set on the dynamically created wlan interfaces, and the wireless ap is not running in isolate mode. This is because these interfaces are created by hostapd, unlike other wlan interfaces which are created from netifd/system-linux.
The attached patch fixes this:
it sets ap_isolate for the hostapd interface, if the interface is using dynamic vlan
it sets multicast_to_unicast and hairpin_mode after the dynamic interface is created
I haven't handled the case where the isolate option is not set for the wifi interface, or where multicast_to_unicast is not set on the bridge, since this requires passing additional information to hostapd, and I wasn't sure what the preferred way to do this would be. I'd probably overload the ap_isolate option to have value 2 mean that multicast_to_unicast and hairpin_mode should be set.
The text was updated successfully, but these errors were encountered:
chrislimpach:
I noticed that multicast_to_unicast and hairpin_mode are not set on the dynamically created wlan interfaces, and the wireless ap is not running in isolate mode. This is because these interfaces are created by hostapd, unlike other wlan interfaces which are created from netifd/system-linux.
The attached patch fixes this:
I haven't handled the case where the isolate option is not set for the wifi interface, or where multicast_to_unicast is not set on the bridge, since this requires passing additional information to hostapd, and I wasn't sure what the preferred way to do this would be. I'd probably overload the ap_isolate option to have value 2 mean that multicast_to_unicast and hairpin_mode should be set.
The text was updated successfully, but these errors were encountered: