From another provider I get multiple VLANs on the same wire. These I need to bridge into different VLANs going out on another wire.
Ether2: T10, T20, T30, T40
Ether3: T222, T333
Then I would like to bridge these interfaces like this:
br222:
ether2.10
ether2.20
ether3.222
br333:
ether2.30
ether2.40
ether3.333
Can this be achieved using Mikrotik? I can only get it to bridge the same VLAN ID together.
In Linux I can do it with bridgeutils like this:
vconfig add eth2 10
vconfig add eth2 20
vconfig add eth3 222
brctl addbr br222
brctl addif br222 eth2.10
brctl addif br222 eth2.20
brctl addif br222 eth3.222
As you can see configuration commands are 1:1 from your linux example. Adding vlan interface requires explicitly defined interface name (in linux it’s implicitly .), the rest is pretty much the same.
The description and requirements as stated in obscure linux config talk makes no sense to me.
He asked or stated wants some vlans to turn into DIFFERENT VLANS??? what the heck does that mean
Where are the different vlans. Something seem missing either in the answer or initial confusing poorly worded requirements.
What does it mean vlans from another provider… are they coming in on a WAN port, or a LAN connection??
Lets say they all came in on ether1 (all the vlans noted below)
Lets assume they are not originating on the router then and they dont need IP address, dhcp server, ip pool, dhcp server network, they just need to be identified.
Thus simple
ONE BRIDGE vlan-flltering=yes
/interface bridge ports
add bridge=bridgesimple etherport=1 ingress filtering=yes only allowed tagged frames
add bridge=bridgesimple etherport=2 ingress filtering=yes only allowed tagged frames
add bridge=bridgesimple etherport=3 ingress filtering=yes only allowed tagged frames
I assume OP knows pretty much exactly what he wants and linux commands make sense in context of what he wrote. So essentially OP needed a linux2ROS translator … not something we expect you to be
In the context of what OP asked, your suggestion of
Thus simple
ONE BRIDGE vlan-flltering=yes
doesn’t make much sense and since OP wants to use CCR1036 to do the job, everything will pass CPU regardless of how he configures it. Plus your suggestion doesn’t get OP’s job done, VLAN 10 on ether2 is still not bridged to VLAN 222 on ether3.
mkx thanks, it works, even with QinQ which is what I really need. Only problem was STP was interfering with my lab switch, but disabled it and everything was running stable.
