more vlan trunks on CRS125 ?

RouterOS General
1

I followed https://wiki.mikrotik.com/wiki/Manual:CRS1xx/2xx_series_switches_examples , expecially inter-vlan routing

On my CRS125 ports 1-21-22 are trunks carrying tagged vlans to three switches , ports 23 and 24 are WANs, the remaining ports (2 to 20) are members of VLAN10 untagged.

As per wiki I started binding all ports but wans to bridge1, despite they are tagged or not

/interface bridge
add name=bridge1 igmp-snooping=no  protocol-mode=none
/interface bridge port
add bridge=bridge1 interface=ether1 hw=yes
...
...
add bridge=bridge1 interface=ether22 hw=yes

I set vlan tagging on cpu port for inter-vlan routing:

/interface ethernet switch egress-vlan-tag
add tagged-ports=switch1-cpu vlan-id=10
add tagged-ports=switch1-cpu vlan-id=20
add tagged-ports=switch1-cpu vlan-id=30

I added ingress vlan translation for access ports (2 to 20):

/interface ethernet switch ingress-vlan-translation
add ports=ether2 customer-vid=0 new-customer-vid=10 sa-learning=yes
....
....
add ports=ether20 customer-vid=0 new-customer-vid=10 sa-learning=yes

Now comes the problem :
Wiki says:

For routing add VLAN interfaces on master-port because it connects with CPU port and add IP addresses to created VLAN interfaces.

/interface vlan
add name=vlan200 interface=ether2 vlan-id=200
add name=vlan300 interface=ether2 vlan-id=300
add name=vlan400 interface=ether2 vlan-id=400

But master-port is no more present from 6.41 on (ether2 in wiki example), should I use bridge created before ???

Next , as I need ports 1, 21 and 22 as vlan trunks to respective switches , where should I declare they are tagged vlan and relative membership ??

Thank you for any help.

2

It seems you found an imperfection in the Wiki guide.
Before 6.41 you should have created the VLAN interface on top of the master-port interface, but after 6.41 the VLAN interface should be created on top of the bridge interface.
This is actually a common mistake that has been studied here:
https://wiki.mikrotik.com/wiki/Manual:Layer2_misconfiguration#VLAN_interface_on_a_slave_interface

Wiki has been updated, thank you for pointing this out!

3

Thank you for link

In wiki , switch1-cpu port is added to /interface ethernet switch egress-vlan-tag in each desired vlan

Should I do the same for all ethernet ports intended to be vlan trunks carrying tagged vlans to other switches ?

Should those ethernet ports be added to bridge anyway ?

Thanks

4

All ports that are involved into switching MUST be added to a bridge.

Trunk ports must be specified in /interface ethernet switch egress-vlan-tag:

/interface ethernet switch egress-vlan-tag
add tagged-ports=ether1,ether21,ether22,switch1-cpu vlan-id=10
add tagged-ports=ether1,ether21,ether22,switch1-cpu vlan-id=20
add tagged-ports=ether1,ether21,ether22,switch1-cpu vlan-id=30
5

Thank you Artz,

One thing is not clear to me from that wiki, look at “Port based VLAN” and “InterVLAN Routing” examples:

The bridge, the ingress-vlan-translation and the egress-vlan-tag are the same.
They differ in Vlan membership declaration.

Port based VLAN uses “/interface ethernet switch vlan”
Inter VLAN Routing uses “/interface vlan”

Why is this ?
Because Inter VLAN need to assign an IP address to vlan interface ? so /interface ethernet switch vlan , is not really an interface ?