[B.A.T.M.A.N.] [PATCH] batman-adv: introduce "noflood" broadcast flood prevention option

Marek Lindner mareklindner at neomailbox.ch
Fri Apr 26 23:56:03 CEST 2019

On Saturday, 27 April 2019 01:12:31 HKT Linus L├╝ssing wrote:
> With DAT DHCP snooping, the gateway feature and multicast optimizations
> in place in some scenarios broadcast flooding might not be strictly
> necessary anymore to be able to establish IPv4/IPv6 communication.
> Therefore this patch adds an option to disable broadcast flooding.
> Larger mesh networks typically filter a variety of multicast packets via
> ebtables/netfilter to clamp on overhead. With this option such firewall
> rules can be relaxed so that such multicast packets are only dropped
> if they cannot be handled by multicast-to-unicast, for instance.

Could you outline the use-case for this specific noflood option in more detail ?
The description above is not entirely clear to me. Especially, the 'might not 
be strictly necessary anymore' to 'firewall rules can be relaxed'. How are 
these things connected ? Is this option implemented only, so that some firewall 
rules don't need to be set anymore ?
What happens if a user enables 'noflood' but does not fall into the 'might not 
be strictly necessary anymore' category ?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/attachments/20190427/428cecfe/attachment-0001.sig>

More information about the B.A.T.M.A.N mailing list