Hello everyone,

I've been pulling my hair out trying to get my VLAN working with Unraid (specifically for containers). While I'm able to get other things working on my VLAN, I'm unable to even get arping to work from a container on unraid. Note that my vlan 30 is on 10.10.30.0/24 with a gateway address (router) of 10.10.30.1.

Possible issues:

• bridge vlan show only shows VLAN 1 on br2 and br2.30

• vlan_filtering is 0 on br2 and br2.30

• Ping from container to 10.10.30.1 fails with no responses

• ARP from container to 10.10.30.1 fails with no responses

• After assigning static IP to Unraid host to test if it even works from there, ARP and ping gives 0 responses over both eth2.30 and br2.30

• MikroTik Switch hosts table never showed a VLAN 30 entry with the unraid host MAC, confirming tagged frames never left Unraid host

• ip route get 10.10.30.1 showed host routing through LAN 192 subnet on br2. When adding a route table entry with no static assignment, this changed to a different subnet of 10.11.12.x which I use only for DAC cable between two servers

I've confirmed many things based on other forum posts:

• VLANs enabled in network settings

• VLAN 30 configured with IPv4 assignment None

• eth2.30@eth2 UP with LOWER_UP and master br2.30

• br2.30 UP with LOWER_UP

• Docker custom network br2.30 (not to be confused with the master interface) has correct subnet 10.10.30.0/24 , gateway 10.10.30.1, ipvlan, parent interface br2.30.

• Host access to custom networks disabled

• Container gets correct IP 10.10.30.2 and default route via 10.10.30.1

Changes attempted but failed to resolve the problem:

• Static route added for 10.10.30.0/24 via br2.30 in GUI routing table

• Temporarily enabled vlan_filtering on br2.30 via ip link set br2.30 type bridge vlan_filtering 1

• Temporarily added IP 10.10.30.254 assigned to br2.30 on host

• Temporarily added IP 10.10.30.254 assigned to eth2.30 on host

• Static MAC entry added to Mikrotik hosts table for Unraid MAC on VLAN 30

• Restarted docker service many times to recreate br2.30

• Disabling all firewall rules for VLAN interface in OPNSense

7: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br2 state UP
13: eth2.40@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br2.40 state UP
14: eth2.30@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br2.30 state UP
15: eth2.20@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br2.20 state UP
16: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
17: br2.40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
18: br2.30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
19: br2.20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

Screenshots:

Docker custom network interfaces:

Network config:

Routing table:

Should work out of the box without additional configuration on the Unraid side.

I'd be looking at the mikrotik's port configuration... noting that you are running tagged and untagged traffic on br2 which likely needs additional configuration.

Quick check and I think most your founding should be normal, because vlan 20,30 IP assign are "none", I also setting in this way as I want my router do all routing work for me.

If this not your planning, then you should assign IP or setting IP on those interface.

And don't setting same subnet 192.168.1.0/24 for br0 br2.

Edited April 1Apr 1 by Vr2Io

On 4/1/2026 at 11:41 AM, tjb_altf4 said:

Should work out of the box without additional configuration on the Unraid side.

I'd be looking at the mikrotik's port configuration... noting that you are running tagged and untagged traffic on br2 which likely needs additional configuration.

That'd be my guess too, it's strange that it can't see the tagged traffic though.. (the mikrotik only has the default vlan automatically discovered).

On 4/1/2026 at 4:30 PM, Vr2Io said:

Quick check and I think most your founding should be normal, because vlan 20,30 IP assign are "none", I also setting in this way as I want my router do all routing work for me.

If this not your planning, then you should assign IP or setting IP on those interface.

And don't setting same subnet 192.168.1.0/24 for br0 br2.

Thanks - that is the plan, I want my router to handle everything else. I will work on updating my config to not include br0, the catch is that I wanted to have a back up connection in case one of my NICs failed but if this is a problem I can find a different solution (like vlans, if I could get them to work). Do you know if having two NICs on the same subnet could cause this issue, or why it's not recommended?

Forgot to follow up on this, the problem was my Mikrotik switch not allowing multiple tags per port (which I had to enable in settings). After that, it started to work right away.

15 hours ago, tekcor said:

Forgot to follow up on this, the problem was my Mikrotik switch not allowing multiple tags per port (which I had to enable in settings). After that, it started to work right away.

I also use Mikrotik SWOS, no problem for multiple tag vlan per port as usual.

Edited May 10May 10 by Vr2Io