netdev - Re: [PATCH iproute2] bridge: make mcast

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190220113510.GB26057@t480s.localdomain>
Date:   Wed, 20 Feb 2019 11:35:10 -0500
From:   Vivien Didelot <vivien.didelot@...il.com>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     netdev@...r.kernel.org, stephen@...workplumber.org
Subject: Re: [PATCH iproute2] bridge: make mcast_flood description consistent

Hi Russell,

On Wed, 20 Feb 2019 00:05:29 +0000, Russell King - ARM Linux admin <linux@...linux.org.uk> wrote:
> I'm not sure if it's in the current iproute2, but there is a
> discrepency between the arguments for 'bridge' stated in the man page
> and the description thereof:
> 
>        bridge link set dev DEV  [ cost COST ] [ priority PRIO ] [ state STATE
> ...
>                } ] [ learning_sync { on | off } ] [ flood { on | off } ] [
>                                                     ^^^^^^^^^^^^^^^^^^
> 
> vs
> 
>        flooding on or flooding off
>               Controls whether a given port will flood unicast traffic for
>               which there is no FDB entry. By default this flag is on.
> 
> vs the command actually accepting "flood" not "flooding".  I spotted
> that in iproute2-4.20.0.  I haven't had a chance to generate a patch
> that yet and work out how to submit it, but thanks for leading the
> way!

You are correct! I've sent a v2.


Thank you,

	Vivien