2 ways to associate bridge and VLAN

No. Looking at https://help.mikrotik.com/docs/display/ROS/Packet+Flow+in+RouterOS#PacketFlowinRouterOS-OverallPacketflowDiagram and with /interface vlan interface=ether1 name=vlan2-ether1 vlan-id=2 as an example:

When a packet tagged with VLAN ID 2 arrives via ether1 the flow is
In-interface bridge port? No
MPLS traffic? No
IPv4 or IPv6 traffic? No
Decapsulate? Yes
At this point as the packet matches interface=ether1 and vlan-id=2 the tag is removed from the packet and presented on the logical interface vlan2-ether1 at which point the packet flow processing begins again.

I don’t think that diagram you linked in your post has anything to do with vlan interfaces. These are pretty simple without too much logic.

Let’s consider a simple scenario: we’re looking at router on a stick with single interface (e.g. ether1) connected to VLAN-enabled switch. So RJ45-side of interface will carry multiple tagged VLANs (a trunk port if you wish).

Now, for the router to interact with all of VLANs we need a few vlan interfaces, created like this:

/interface vlan
add interface=ether1 name=e1v13 vlan-id=13
add interface=ether1 name=e1v42 vlan-id=42
...

Yes, what I’m calling tagged end is in example above ether1 and the untagged end are e1v13 and e1v42 and … And in this particular scenario, we would assign IP address (or bind DHCP client or …) to those untagged ends.


BTW, the linux parallel is even simpler … if we have an ethernet interface e.g. enp192 which is used as trunk port connected to VLAN-enabled switch, then we configure virtual interfaces with names enp192.13 and enp192.42 etc. These interfaces are exactly the same as vlan interfaces in ROS, only that the names are pretty much pre-defined.

[edit] corrected linux interface names.

Probably, i used a wrong diagram indeed… :smiley:
Thanks @tdw and @mkx for answering…
I was more confused with the terminology Tagged and Untagged Ends the way they were used, but i think i got it…