| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <29a9c85b-8f5a-2b85-2c7d-9b7ca0a6cb41@gmx.net>
Date: Thu, 9 Jul 2020 11:32:00 +0000
From: ѽ҉ᶬḳ℠ <vtol@....net>
To: netdev@...r.kernel.org
Subject: [DSA] L2 Forwarding Offload not working
"kernel":"5.4.50", "system":"ARMv7 Processor rev 1
(v7l)","model":"Turris
Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"OpenWrt","version":"SNAPSHOT","revision":"r13719-66e04abbb6","target":"mvebu/cortexa9","}
CPU Marvell Armada 385 88F6820 | Switch Marvell 88E6176
soft bridge br-lan enslaving DSA ports lan0 lan1 lan2
DSA master device eth1 (subsequent ip l exhibits slaves as lanX@...1)
----------
After perusal of
https://www.kernel.org/doc/Documentation/networking/switchdev.txt it is
my understanding that offloading works only for static FDB entries,
though not clear to me:
* what the logic is behind, and
* why DSA ports are not static FDB entries by default (would only seem
logical)
That said queried bridge fdb for lan2 (as example here), producing:
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self
then went ahead with
bridge fdb add 44:8a:5b:47:0b:c2 dev lan2 vlan 1 self
resulting in
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self static
So it is static now but nothing about offload still. Next up
ip l s br-lan ty bridge vlan_filtering 1
checking again bridge fdb and now exhibiting
44:8a:5b:47:0b:c2 dev lan2 vlan 1 master br-lan
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self static
Do I suffer some sort of misconception of how to get it working, missing
something?
Powered by blists - more mailing lists