-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Servicing interfaces that are created ad-hoc (L2TP multitap) #86
Comments
The way we deal with this when using Tunneldigger is to stick all the L2TP interfaces in a bridge (that has forwarding between bridge ports disabled using ebtables/nftables, so nodes don't think they are connected to each other directly) and put mesh-announce on that bridge. That bridge is then attached to the batman interface. |
Just switched some of our gateways to fastd with multitap and the same approach works there as well. It's pretty much a drop in replacement for Tunneldigger at that point. |
I recommend using |
Neat! I did not know this. Thanks! |
Since this seems to be resolved, I'm closing the issue. Feel free to re-open if you see the need for a solution inside mesh-announce. |
With fastd's L2TP multitap feature (coming in Gluon 2022.1) we're seeing one interface per L2TP peer and I don't see a way for mesh-announce to work on links that are created in an ad-hoc fashion.
I think we need to brainstorm a way for mesh-announce to work on these kinds of links in multidomain setups.
The text was updated successfully, but these errors were encountered: