Pls Help: Setting up VLAN tagging on Orbi RBR50/RBS50 running Voxel firmware

[todeshorn]

First and foremost, I want to express my sincere gratitude for all the incredible work Voxel has done to provide a powerful alternative to the limited stock firmware. I also deeply appreciate the time and effort the community volunteers put into supporting Voxel users—your dedication doesn’t go unnoticed.​

​

I'm trying to pass VLAN tagged traffic between my Proxmox server and OPNsense router through my Orbi mesh network (RBR50 router and RBS50 satellite running Voxel firmware), but having no luck.

My setup:​

• Proxmox Server connected to Orbi RBR50 (router)
• Orbi RBS50 (satellite) connected to OPNsense router
• Both Orbi devices running Voxel firmware
• Need to pass VLAN 20 tagged traffic between Proxmox and OPNsense

What I've tried:​

1. Confirmed VLAN support is already enabled in the router config:

   [/LIST]
   [HEADING=2]From /etc/config/network:[/HEADING]
   config switchoption name 'switch0'option reset '1'option enable_vlan '1'

   1. Tried adding VLAN 20 configuration using swconfig:

      swconfig dev switch0 set enable_vlan 1swconfig dev switch0 vlan 20 set ports "0t 1t 2t 3t 4t 5t 6t 7t 8t"

      This failed with the error: "failed"
   2. Examined switch capabilities with swconfig dev switch0 help:

      switch0: QCA AR8327 AR8337(QCA AR8327 AR8337), ports: 7 (cpu @ 0), vlans: 128

   3. Modified /overlay/etc/config/network on both Orbi devices to add:

      config switch_vlanoption device 'switch0'option vlan '20'option ports '0t 1t 2t 3t 4t 5t'
      [/LIST]
      config interface 'vlan20'option ifname 'eth1.20'option proto 'none'option type 'bridge'

      1. The changes to the config file are visible after reboot, but VLAN tagging still isn't working.
         Current network config:

      config switch_vlanoption device 'switch0'option vlan '1'option ports '0t 2 3 4 5'config switch_vlanoption device 'switch0'option vlan '2'option ports '0t 1'

      
      The bridge configuration shows:

      bridge name    bridge id        STP enabled    interfacesbr0        8000.78d294aa4df8    yes        ath0ath01ath02ath1ath11ath2eth0eth1

      
      Anyone had success with VLAN tagging through Orbi mesh? Could the satellite be stripping VLAN tags? Any special configuration needed?
      
      Thanks in advance for any help!

 

[Digilog]

To pass through a vlan, its also assigned to the WAN port as well a LAN port

 

[todeshorn]

Thank you for your input. Just to clarify, I’m not using the WAN port in my setup. Here’s a diagram to illustrate the current configuration:

[OPNsense]
     |
[TP-Link SG108E]
     |
 [Orbi RBR50] ))))))) Wi‑Fi Backhaul ((((((( [Orbi RBS50]
                                                    |
                                             [Proxmox Server]
                                                   |        |__________
                                                 VM1 (vlan20)       |
                                                                    |
                                                                 VM2 (vlan30)

The issue I’m facing is that VLAN-tagged traffic isn’t being preserved over the Wi‑Fi backhaul. I tested this by temporarily removing the RBK50 (Wi‑Fi backhaul) and replacing it with an Ethernet cable, and in that case, all VLAN-tagged packets reach their destinations as expected.

It appears that when using the Wi‑Fi backhaul, all VLAN tags (except for VLAN1) are stripped from the packets. Ideally, I’d like the backhaul to function as a trunk interface, allowing all VLAN-tagged traffic to pass through intact between both sides. If that isn’t feasible, I’m prepared to modify the configuration files on each Orbi device for each VLAN I want to support.

Any insights or suggestions on how to achieve a true trunk over the Wi‑Fi backhaul would be greatly appreciated.

 

[Digilog]

Any insights or suggestions on how to achieve a true trunk over the Wi‑Fi backhaul would be greatly appreciated.

well, the switch0 is usually after an interface like eth1 and the wifi is on a different interface like eth0
which you need VLAN

so in the /etc/config network you would need something like this:

config 'switch_vlan'
   option 'vlan'       '20'
   option 'device'     'eth1'
   option 'ports'      '3 5t'

then where the wifi interface that will have a heading like config 'eth0'
you add:

option 'vlan'       '20'

But I don't know which interface is wifi or the wired interface (eth0,eth1). Because this is not labeled universally. Switch is just on the wired interface so that is why wifi doesn't pass through, because its a different interface.

Also remember on most consumer wifi routers there is usually only 3 interfaces at the most. 1 for WAN 1 for WIFI and 1 for the wired network that a hardware or in this case, a software controlled hardware switch is deployed.