VLAN tutorial - Understanding menu "/interface bridge vlan"

[moveik]

You dont if there is no difference in the paths of all the tagged vlans… so yes on one line

As @anav noted, it is perfectly fine to group lines per VLAN. There’s a gotcha: some VLAN ID can only be referred to in single line. So this construct is not possible:

/interface bridge vlan
add bridge=BR1 tagged=BR1 vlans=10,20,30
add bridge=BR1 tagged=BR1,ether1 vlans=10

this one is fine though:

/interface bridge vlan
add bridge=BR1 tagged=BR1 vlans=20,30
add bridge=BR1 tagged=BR1,ether1 vlans=10

Having VLANs grouped initially brings another drawback. This construct doesn’t work:

/interface bridge vlan
add bridge=BR1 tagged=BR1 vlans=10,20,30
# after a few moths one perhaps wants to execute the following line
set [ find where vlans=10 ] tagged=BR1,ether1

I understand.
So it is mainly a programming convenience.

For the scenario of “Router-Switch-AP (all in one)” (as written in this comment):

Why would we need to have these “/interface bridge vlan” commands:

# egress behavior, handled automatically

# L3 switching so Bridge must be a tagged member
/interface bridge vlan
add bridge=BR1 tagged=BR1 vlan-ids=10
add bridge=BR1 tagged=BR1 vlan-ids=20
add bridge=BR1 tagged=BR1 vlan-ids=99

?
As I noted earlier, these commands add tagging of the VLAN id to the packets which leave the bridge.

Specifically for the scenario of “Router-Switch-AP (all in one)”, we don’t need the packets which leave our device to have VLAN tagging.
Their VLAN tagging is redundant, because only the clients will read it (and do nothing with it).