gluon-ebtables-filter-multicast: block packets with Gluon VXLAN multicast destination #3477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An incorrectly connected node may send wired-mesh packets to another
node's client port. For raw batman-adv, such frames are filtered by
batman-adv, but this does not work with VXLAN encapsulation.
While such packets are not flooded through the mesh because of the
batman-adv noflood flag, they may still reach another node that is
connected in the same incorrect way, which could result in loops and
other connectivity issues.
Filter out packets sent to our VXLAN multicast group address to avoid
such problems.
Fixes #3025
Completely untested, but seems straightforward enough.
Another point for discussion: Do we want to remove some protocols from the gluon-ebtables-filter-multicast allowlist? Running Babel, OSPF or RIP-NG over a regular mesh seems like a bad idea, and unusual enough that requiring to disable the filter may be justified.