Total obsolete VLAN documentation

with

the kernel advises the DSA driver that kernel has management control over the 802.1Q tags on the DSA interfaces. That in consequence leads to this sort of routing and processing of 802.1Q tagged packages on the Lan segment (Lan port just picked randomly)


Letting instead DSA manage control over the 802.1Q tags on the DSA interfaces the traffic on the Lan segments stays within the swtich fabric instead


This is just for the TO. Now If you go with Mox and one or tow of the E modules one would likely prefer any 802.1Q tagged traffic to remain with the switch fabric and not being bounced up and down to the CPU for processing.

3 Likes

Thas old doc and yes I have registration there at https://wiki.turris.cz/doc/en/start but I had new one on my mind which is here https://docs.turris.cz/ and it is obviously on different platform and I dont see login there. Is it really the same ?

No,

This is reserved for the (new) documentation provided by the manufacturer only and sans community section.

I thought it is like that and could not find where to register for new docs.

@anon82920800 Hi, I have a question then, not clear here for me.

Does use Turris Omnia DSA and chip switching when i use

config interface 'lan'
        option type 'bridge'
        option vlan '1'
        option proto 'static'
        option netmask '255.255.255.0'
        option ipaddr '192.168.1.1'
        option bridge_empty '1'
        list ifname 'lan0.10'
        list ifname 'lan1'
................

Or not ? If not, can I get HW Offloading for switching on the Omnia ?

Thank you.

Just to ensure, because that has not been asked before (or maybe I haven’t noticed):

  1. When wanting VLAN-ID 10 tagged on WAN should I use
bridge vlan add dev eth2 vid 10 master

as eth2 has slaves wan/sfp or

bridge vlan add dev wan vid 10 master

because DSA uses directly slave interfaces?

  1. The benefits of hardware-offloading are clear to me. But does using DSA (bridge/ip) provide any benefit over kernel activities, when I only have one interface?
    Example 1: MOX with only one ethernet-jack at all available (eth0)
    Example 2: Turris Omnia with only one connected ethernet cable in lan4

As no one answered I will answer the question myself: There is very low to no benefit in invoking hardware offloading, if TO or MOX is only used as an access point and therefore only connected via 1 single ehternet cable.
Reason: The traffic is in this scenario always directly adressed to or comes from the router and needs then to pass CPU (as it has to be processed).
Therefore in this case the existing VLAN documentation (which can be found here: https://docs.turris.cz/basics/luci/vlan/luci-vlan/) shows everything needed to create an VLAN.