Hoi,
On 18.02.2026 09:54, Stanislav Zaikin via lists.fd.io wrote:
Hoi Pim,
I assume it's just because the flooding is implemented via
L2INPUT_FEAT that is applied only on ingress :)
Yes, it makes sense that L2INPUT_FEAT operates only on ingress.
Considering the situation in which there are two tunnels between the
same two hosts) is very rare, and the system does do the right thing
(drop on the remote side, even though the copy happens on the source
side), there is no bug.
I agree with you that egress flooding on non-flood interface makes
little sense (and we even have a separate knob to disable it in our
custom fork).
If you're willing to share implementation notes with me (privately is
fine), I'd appreciate it. It seems that in l2-flood, looking at the
destination interfaces' L2INPUT_FEAT would do the trick without
additional CPU cycles spent, although it may leave future readers of the
codebase wondering 'why would you do it that way'. Adding an
L2OUTPUT_FEAT for l2-flood-out for the sole purposes of this esoteric
corner case, feels like a bad solution.
Perhaps I'll just leave it alone.
groet,
Pim
--
Pim van Pelt <[email protected]>
PBVP1-RIPE https://ipng.ch/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#26828): https://lists.fd.io/g/vpp-dev/message/26828
Mute This Topic: https://lists.fd.io/mt/117860165/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
