diff options
| author | Jan Hoffmann <jan@3e8.eu> | 2023-05-06 19:28:54 +0200 |
|---|---|---|
| committer | Sander Vanheule <sander@svanheule.net> | 2023-05-07 19:07:34 +0200 |
| commit | 5d34fc92eccc7d8f3fd35fd5841c110ca1aefc13 (patch) | |
| tree | c8d92333fa6a590daeaaa6d85c8ff6ae34b93499 /target/Makefile | |
| parent | 4c0a1667f3e752d31b22ca699a9a3fda5eb47dc7 (diff) | |
| download | upstream-5d34fc92eccc7d8f3fd35fd5841c110ca1aefc13.tar.gz upstream-5d34fc92eccc7d8f3fd35fd5841c110ca1aefc13.tar.bz2 upstream-5d34fc92eccc7d8f3fd35fd5841c110ca1aefc13.zip | |
realtek: fix standalone ports in presence of static fdb entries
The registers L2_PORT_STATIC_MV_ACT seem to specify the action to take
when the source address of a packet exists as a static fdb entry on
another port. By default the configured action is to drop such packets.
For standalone ports, this behaviour is undesired, as all traffic should
be forwarded to the CPU. So change the action to forward on standalone
ports.
A situation where this issue can occur is when a non-offloaded bond
interface is part of a bridge. In that case, the CPU port will have fdb
entries for devices connected to the bond interface, which are managed
by the assisted learning feature.
For now, this is only implemented for RTL838x/RTL839x, as the available
set of registers differs for the other devices.
Signed-off-by: Jan Hoffmann <jan@3e8.eu>
Diffstat (limited to 'target/Makefile')
0 files changed, 0 insertions, 0 deletions