How to correctly manage VLANs on Mikrotik?

Question

Computer networks

Good evening everyone.

I have an absolute understanding of how VLANs work on Cisco switches, D-Link, etc.
That is, the port can be Access, Tagged or Trunk.

But in Mikrotik I'm completely confused.

VLAN can be created on the Bridge, VLAN interface can be created on the physical interface.

And here I don’t understand:
If I add VLAN 15 to Bridge, and in the same window I specify the Tagged Ether1 port, then tagged traffic will go from the Ether1 port.

But all of a sudden I can add VLAN 15 to the Ether1 interface in the interfaces menu.

Well, what will happen? What for? What if VLAN 15 in the bridge menu points to Ether1 as Untagged, and I add tag 15 to the Ether1 interface in the interfaces menu?

Actually, it's kind of crazy. Why are there several ways to add VLANs, also in different menus, and also the created VLANs can contradict each other?

Answer 1

So here it is - Miroktik) Like a Swiss knife!
If you look at the circuit diagram, you will notice that between the processor and the ports there is a separate chip that takes on the role of a switch. So, if you configure VLAN in the switch section, then you will configure this switch chip. If configured in the bridge, then work with the VLAN will take place in the processor with all the consequences.
If it is necessary to drive traffic in VLAN between ports of Mikrotik, then it is more correct to do it in switch, then transit traffic will not load the CPU.
If Mikrotik needs to route traffic in this VLAN, then your path is bridge.

Answer 2

I have an absolute understanding of how VLANs work on Cisco switches, D-Link, etc.

The key word here is on switches. On routers, even cisco or Linux, there are also a different number of options to create a vlan. And also through the bridge, and to the physical interface. See how to add vlans to the Cisco 6500, then you will understand the logic. If we draw an analogy, then a bridge is an L3 interface on a vlan. And the physical port is an L3 interface on the physical interface, adding a vlan to which makes it possible to differentiate traffic on the trunk.