It looks like some parts of the documentation are not updated to include the new RDS2216. Is there an official Mikrotik support on this forum who could answer if:
MAC-based VLANs will only work properly between switch ports and not between switch ports and CPU. When a packet is being forwarded to the CPU, the pvid property for the bridge port will be always used instead of new-vlan-id from ACL rules.
Thanks!
Do you mean MACVLAN? https://help.mikrotik.com/docs/spaces/ROS/pages/217874440/MACVLAN
You’d add MACVLAN to bridge, and then tag it as needed in bridge vlan settings. But AFAIK it will use CPU.
Nope I mean the switch chip feature that would add VLAN tag based on the MAC address https://help.mikrotik.com/docs/spaces/ROS/pages/30474317/CRS3xx+CRS5xx+CCR2116+CCR2216+switch+chip+features#CRS3xx%2CCRS5xx%2CCCR2116%2CCCR2216switchchipfeatures-MACBasedVLAN
100% agree that docs are all of switching features are “messy” and incomplete (i.e. switching page does not mention RDS). Now given the 98DX4310 chip is used by RDS, and that chip is covered in docs…
On the doc comment: “MAC-based VLANs will only work properly between switch ports and not between switch ports and CPU.” – that only come up if the RDS is the router for the VLAN (i.e. if your switching VLANs on RDS). Assuming the VLAN needs to be routable (thus via CPU), given there are no chipset “exceptions”, I’d presume it apply to RDS.
But agree a ticket to Mikrotik be a good path, the docs on switching do suck.
The primary reason I’m looking for this feature (assigning VLAN based on MAC) in CPU direction is that I want per-VLAN DHCP to work (plus a couple similar container-related cases).
My reading is it would go via the CPU, but cannot say for sure.
Now on the RDS, the CPU is pretty powerful, so how much that effect actual traffic if you used bridge filters is unknown.