-
Notifications
You must be signed in to change notification settings - Fork 325
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
gluon-ebtables-filter-multicast: relax IPv6 multicast firewall rules #2209
gluon-ebtables-filter-multicast: relax IPv6 multicast firewall rules #2209
Conversation
This mark prevents a multicast packet being flooded through the whole mesh. The advantage of marking certain multicast packets via e.g. ebtables instead of dropping is then the following: This allows an administrator to let specific multicast packets pass as long as they are forwarded to a limited number of nodes only and are therefore creating no burdon to unrelated nodes. Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Allow the transmission of IPv6 multicast packets as long as they are not flooded through the whole mesh. Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Changelog compared to #1357:
Edit: updated batman-adv noflood-mark link, was wrongly pointing to batctl, too. |
These versions were rejected, but I don't see the reasoning in patchwork. Does that mean we have to carry them downstream for the forseeable future? |
I added this to the 2021.1 milestone, unless you want to push this back to 2021.2 because we just reenabled multicast optimiziations. |
Sorry, had the wrong link for the batman-adv patch. Updated that. I think @ecsv felt it was a bit too specific for our setup. And would have preferred a solution outside of batman-adv. But I'm not quite sure how that could look like yet. For his "tc" suggestion I think there are some issues as described on the list / in patchwork. I'm not 100% sure yet for which direction to go with upstream yet. We could add a more generic "disable broadcast flooding" patch to batman-adv, which would be easier to handle than packet marks. But then that would break respondd and alfred, which rely on flooding right now. On the other hand, there the workings of this patch a bit comparable to the "isolation mark" feature in batman-adv, so that could be a point in favor of getting it upstream in batman-adv. I'll need to talk a bit more about that with the other batman-adv developers. Also the patch is really small and minimal invasive. So rebasing it would be no issue. And I currently like with this approach that in Gluon it only needs three lines to enable and use it.
Sounds good to me. I think it'd actually be handy to have it in the same release as re-enabling multicast optimizations in batman-adv. If someone were running into issues with multicast they could then use multicast ICMPv6 echo requests to help with debugging. |
Let's give this a shot. |
What's the upstream status of the noflood flag support? I'd really like to get rid of non-upstream patches in Gluon as far as possible. |
Allow the transmission of IPv6 multicast packets as long as they are not flooded through the whole mesh.
This is achieved by adding a small "noflood mark" patch to batman-adv. With that multicast packets can be marked by iptables/ip6tables/ebtables as: "Please drop me, batman-adv, if I you'd flood me through the whole mesh."
That way it is now possible to send IPv6 packets with a link-local multicast if less than 16 nodes signed up for it (16 = batman-adv multicast fanout default).
This implements the remaining part of #1357.