Looking at the Omnia block diagram, there are two CPU ports, eth0 and eth1 that connect to an internal switch on ports 5 and 6. The lan0-4 ports also connect to this switch.
The common default configuration with guest network enabled results in two bridges:
config device 'br_guest_turris'
option name 'br-guest-turris'
option type 'bridge'
option bridge_empty '1'
config device 'br_lan'
option name 'br-lan'
option type 'bridge'
list ports 'lan0'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
Interface eth1 is up, eth0 is down, so eth1 is used by the CPU to reach lan0-4. Why are ethx ports not needed in the bridges?
The reason why I am asking is that I want a VLAN configured for a second AP (trunk lan0). I understand there are two ways to do this in DSA:
- Delete br-guest-turris, Enable vlan filtering for br-lan, tagged lan0 with two VIDs, enable local for both. This will create br-lan.vid1 and br-lan.vid2 bridges. Assign these vlan bridges to the lan and guest_turris interfaces respectively.
- Keep two bridges, but replace lan0 with lan0.vid1 in br-lan and add lan0.vid2 to br-guest-turris.
The second option seems almost magical, but how would the Omnia figure out that eth1 (the CPU ports) should also be a trunk port? Are eth1.vid1 and eth1.vid2 added to the bridge implictly?