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

[Marek Lindner <mareklindner@neomailbox.ch>]

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

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 ?

Thanks,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]