Removing Babel VLAN on ethernet interfaces inside br-lan#1210
Open
AguTrachta wants to merge 8 commits intolibremesh:masterfrom
Open
Removing Babel VLAN on ethernet interfaces inside br-lan#1210AguTrachta wants to merge 8 commits intolibremesh:masterfrom
AguTrachta wants to merge 8 commits intolibremesh:masterfrom
Conversation
Ensure nftables netdev/ingress hooks are available at runtime. This module is required for the netdev table used to guard bat0 against Babel flooding (UDP/6696 + multicast) before bridging.
Configure Babel to run on br-lan with type=wired to enable wired optimizations
This simplifies the topology and aligns with running Babel on br-lan.
When kmod-batman-adv is installed, deploy a small nftables ruleset and fw4 include to drop Babel traffic arriving on bat0 before it reaches the bridge
Contributor
|
Hi, thanks for this work Some minor changes:
[0] https://wiki.nftables.org/wiki-nftables/index.php/Netfilter_hooks#Hooks_by_family_and_chain_type |
Contributor
Author
|
Thanks for the corrections @a-gave ! I tested it in my routers and works great, please let me know if I need to change anything else |
ilario
reviewed
Aug 23, 2025
packages/lime-proto-babeld/Makefile
Outdated
| CATEGORY:=LibreMesh | ||
| TITLE:=LiMe babeld proto support | ||
| DEPENDS:=+babeld +lime-system +luci-lib-nixio | ||
| DEPENDS:=+babeld +lime-system +luci-lib-nixio |
Member
There was a problem hiding this comment.
there is a leftover whitespace here
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a replace of #631
This PR removes the legacy "VLAN-on-wlan" approach in
lime-proto-babeldand runs Babel directly on the base interfaces and on the LAN bridgebr-lan(marked astype=wired) for modern DSA devices.During validation, a side-effect (ghost neighbor) caused by bridging
bat0intobr-lanappeared; the PR also ships a nftables netdev/ingress guard onbat0to prevent L2 flooding of Babel traffic.br-lanwithtype=wiredgives wired links the expected low metric and behavior.bat0is bridged intobr-lan, L2 multicast flooding of Babel (UDP/6696) can trick peers into thinking a remote node is a direct wired neighbor. The netdev/ingress guard drops those frames atbat0before the bridge floods them.Two nodes, no cable (Wi‑Fi only)
Node LiMe-d5d63f:
No wired neighbor; costs reflect Wi‑Fi links only.
Plug Ethernet between the nodes
Same node LiMe-d5d63f:
Wired neighbor appears on
br-lanwith canonical cost 96 and becomes preferred.Guard counters
The guard actively drops Babel over
bat0before the bridge floods it.To activate the
babeldproto in LibreMesh (so the new behavior takes effect), addbabeld:0to the protocol list inlime-nodelike:IMPORTANT: This new changes does not support
swconfig, only routers withDSA, I can't test the first one, so you're invited to implement that part :)