Is there any way to allow a VLAN to have a final egress translation out to multiple ports on a CRS125?
I’m trying to migrate a bunch of offices’ private DHCP servers (each office has their own WAN IP and private DHCP) up to a single Mikrotik device, instead of each office having DHCP on their last hop. I want a more powerful core Mikrotik device to have the individual office DHCP servers on individual VLANs.
Right now I have 6x DHCP bridges/LANs on 24 ports on a CRS (4x wired ports per DHCP), with the sfp1 port being the switched uplink. The CPU on the CRSes can’t handle gigabit speeds doing DHCP down at that level, so I need to consolidate all of the DHCPs up (6x4 per CRS,) to a master cloud core router.
I was hoping I could put the DHCP bridges up on the cloud core and then send VLANs down so that if someone plugs into ether1-ether4 of one CRS, they get DHCP1 from the master CCR, and ether5-ether8 of the same CRS they get DHCP2, but this is turning out harder to actually do than I thought.
However, it looks like the VLAN egress code only allows for one vlan per port, and not multiple ports:
/interface ethernet switch ingress-vlan-translation
add ports=ether1 customer-vid=0 new-customer-vid=55 sa-learning=yes # works
add ports=ether2 customer-vid=0 new-customer-vid=55 sa-learning=yes # error
add ports=ether3 customer-vid=0 new-customer-vid=55 sa-learning=yes # error
add ports=ether4 customer-vid=0 new-customer-vid=55 sa-learning=yes # error
/interface ethernet switch egress-vlan-tag
add tagged-ports=sfp1 vlan-id=55
/interface ethernet switch vlan
add ports=sfp1,ether1 vlan-id=55 learn=yes # works
add ports=sfp1,ether2 vlan-id=55 learn=yes # error
add ports=sfp1,ether3 vlan-id=55 learn=yes # error
add ports=sfp1,ether4 vlan-id=55 learn=yes # error
Any way around this? Or do I just have to make a VLAN551, VLAN552, VLAN553,VLAN554 that leads back to the same bridge on the uplink CCR to emulate what I’d like to get done?