Adding container to bridge in VRF: "port is already slave"

RouterOS Containers
1

I wanted to add a container to a bridge that's part of a VRF (RB4011 running 7.23.2):

/interface veth
add name=veth5
/interface bridge
add name=bridge-test
/interface bridge port
add bridge=bridge-test interface=veth5
/ip vrf
add interfaces=veth5,bridge-test name=test
/container/set 3 interface=veth5

As soon as I issue these commands (the order isn't relevant, it happens whenever all three conditions are met: 1. veth5 is in a VRF; 2. veth5 is in a bridge; 3. veth5 is assigned to a running container), the error "port is already a slave" is shown in the bridge ports list:

image
image472×152 17.9 KB

veth5 is not part of any other bridge, and as soon as the container is stopped, the error vanishes. I wasn't able to find any documentation regarding the combination of containers and VRFs, but I guess this is a bug, and if the combo is supposed to be unsupported, it would be great to have an error message along the lines of "containers are not supported inside VRFs"

2

Your config is incorrect. If veth5 is a part of the bridge, only the bridge should be an interface of the vrf.

If you correct this, do you still get the error?

3

Wow, thanks! Indeed, removing veth5 from the VRF solves the issue and the bridge works as expected. I expected to have to put all the interfaces belonging to the VRF into its config, so didn't even consider not adding veth5 a viable option!

4

You may still wish to write a support request, because the error message is less than clear... Maybe it could be improved.