From 4003dd53ba760827bf87553659d26f4be5454ba8 Mon Sep 17 00:00:00 2001 From: Thomas Quinot Date: Thu, 2 Nov 2023 16:50:29 +0100 Subject: [PATCH] LeLoft-iot SSID --- _source/_posts/2023-11-01-homeassistant-homekit-docker.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_source/_posts/2023-11-01-homeassistant-homekit-docker.markdown b/_source/_posts/2023-11-01-homeassistant-homekit-docker.markdown index 5de093d..6f45e4e 100644 --- a/_source/_posts/2023-11-01-homeassistant-homekit-docker.markdown +++ b/_source/_posts/2023-11-01-homeassistant-homekit-docker.markdown @@ -33,3 +33,5 @@ When using host networking, Traefik will connect to the container on the host's # Mikrotik setup I am assigning a separate IoT VLAN to the gateway through a Mikrotik wireless access list. By default, the device will only see multicast frames sent to the [default VLAN of the interface](https://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#Vlan_tag_override) (not to the overridden VLAN from the access list). In order for it to get the multicast frames of its ACL-assigned VLAN, the `multicast-helper=full` option must be enabled on the wifi interface ([doc](https://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#General_interface_properties)). + +(Actually I ended up creating a separate virtual SSID for all things IoT instead, so that I do not need to manually maintain the access list).