Trunk Port with all VLANS

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi,
is there a way to set a physical port to a trunk port without defining every single vlans?
f.e.:

Thanks in advance!

2

No, not that I'm aware of. You have to add the port to each vlan-bridge.

Edit: to use proper wording: add the tagged port to each config bridge-vlan stanza.

2 Likes
3

Hi,
thanks for answering. Ok, I thought so. :confused:

Can you tell me whats the difference in using vlan filtering on the bridge instead of just adding a 802.1q interface on the specific interface and bridge it?

Does this have any performance impact or anything else?

f.e.:

VLAN filter on bridge:

image
image888×340 19 KB

Thanks!

VLAN interface and bridge:

image
image897×631 31.4 KB

image
image759×341 19.6 KB

4

I think this depends on personal preferences... using multiple bridges (one for each vlan) comes from a time when we did not had vlan-aware bridges (if memory serves me well, it got into Linux around 2018 or so).

I don't know/doubt that there is any difference in "speed" or "performance", but I find it more appealing to have a single vlan-aware bridge (on DSA capable devices or "proper" x86 machines with "real" NIC).

# Config snippets from a DSA switch; using a single vlan-aware bridge
# This switch used as an "access"-switch; lan8 is my "uplink-trunk"
config device
        option  name            'switch'
        option  type            'bridge'
        list    ports           'lan1'
        list    ports           'lan2'
        list    ports           'lan3'
        list    ports           'lan4'
        list    ports           'lan5'
        list    ports           'lan6'
        list    ports           'lan7'
        list    ports           'lan8'
        list    ports           'lan9'
        list    ports           'lan10'

config bridge-vlan
        option  device          'switch'
        option  vlan            '24'
        list    ports           'lan6'
        list    ports           'lan7'
        list    ports           'lan8:t'

config bridge-vlan
        option  device          'switch'
        option  vlan            '64'
        list    ports           'lan2'
        list    ports           'lan3'
        list    ports           'lan8:t'

config interface 'vlan24'
        option  device          'switch.24'
        option  proto           'none'

config interface 'vlan64'
        option  device          'switch.64'
        option  proto           'none'
1 Like
5

When the device has a hardware switch with DSA, you have to use the bridge-vlans method. This will result in hardware accelerated switching.

3 Likes
6

Yes you're right but if I remember right there are also "vlan-aware" bridges which transport all vlans - like in Proxmox for example. So I guess this is implemented in the kernel.

7

Do you have an example on hand, because I could not find anything related. Only that assign just all vlans to the bridge. But a range of vlans can not be set up with UCI...

8

This example is from Proxmox (Kernel 5.15.60, Debian 11.5):

auto vmbr1
iface vmbr1 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
        mtu 1504

Maybe it's just missing in UCI. :thinking:

1 Like
9

Ah ok, that's what I've found, too. that a range needs to be specified anyway.

10

Yeah, but defining a range in UCI is missing, right?