thomas
/
labnotes
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

LeLoft-iot SSID
continuous-integration/drone Build is failing Details

Browse Source
main
Thomas Quinot 1 year ago
parent 68d0b70835
commit 4003dd53ba
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File

2
_source/_posts/2023-11-01-homeassistant-homekit-docker.markdown
Unescape Escape View File

@ -33,3 +33,5 @@ When using host networking, Traefik will connect to the container on the host's
# Mikrotik setup # 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)). 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).

Write Preview
Loading…
Cancel
Save