From: Nick Carter <ncarter100@gmail.com>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org, "Michał Mirosław" <mirqus@gmail.com>,
"Stephen Hemminger" <shemminger@linux-foundation.org>,
davem@davemloft.net
Subject: Re: [PATCH] bridge: mask forwarding of IEEE 802 local multicast groups
Date: Sun, 3 Jul 2011 19:30:33 +0100 [thread overview]
Message-ID: <CAEJpZP10QCbKjk3sp7s7LuFHB8VMRwbpaamXwmFH3vH_NpmfMQ@mail.gmail.com> (raw)
In-Reply-To: <20110701223756.GG2613105@jupiter.n2.diac24.net>
On 1 July 2011 23:37, David Lamparter <equinox@diac24.net> wrote:
> On Fri, Jul 01, 2011 at 10:21:44PM +0100, Nick Carter wrote:
>> Introduce sysfs ../bridge/group_fwd_mask attribute so users can
>> configure which group mac addresses are forwarded.
>>
>> These diffs do not change the default behaviour of bridge.ko. By
>> changing the group_fwd_mask value users can select any combination of
>> the 01-80-C2-00-00-00 - 01-80-C2-00-00-0F addresses to be forwarded.
>>
>> Signed-off-by: Nick Carter <ncarter100@gmail.com>
>
> Hm. Makes it very easy to shoot yourself in the foot, but...
>
>> + br->group_fwd_mask = 0;
>
> ... but the default is safe, so we're following the unix philosophy of
> handing out the gun to shoot yourself :)
>
> Reviewed-by: David Lamparter <equinox@diac24.net>
>
>
> PS:
>> @@ -166,6 +166,9 @@ struct sk_buff *br_handle_frame(struct sk_buff *skb)
>> if (p->br->stp_enabled == BR_NO_STP && dest[5] == 0)
>> goto forward;
>
> Not sure if we still need the STP one when we have the mask, it should
> probably go away for consistency. It would change existing behaviour
> though... either way it can be a separate patch.
Yes I agree. Probably best to wait until the user space tools are
updated to support the new mask, so users can easily configure a
workaround to the change in behaviour. I'm happy to update brctl to
support the mask, I pretty much have the diffs already.
Nick
>
>> + if (p->br->group_fwd_mask & (1 << dest[5]))
>> + goto forward;
>> +
>> if (NF_HOOK(NFPROTO_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
>> NULL, br_handle_local_finish))
>> return NULL; /* frame consumed by filter */
>
next prev parent reply other threads:[~2011-07-03 18:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 21:21 [PATCH] bridge: mask forwarding of IEEE 802 local multicast groups Nick Carter
2011-07-01 22:37 ` David Lamparter
2011-07-03 18:30 ` Nick Carter [this message]
2011-07-10 16:04 ` Nick Carter
2011-07-11 15:27 ` Stephen Hemminger
2011-07-12 11:36 ` David Lamparter
2011-07-15 15:44 ` Nick Carter
2011-07-15 16:03 ` David Lamparter
2011-07-15 16:33 ` David Lamparter
2011-07-27 11:17 ` David Lamparter
2011-07-28 15:41 ` Stephen Hemminger
2011-08-15 16:27 ` Nick Carter
2011-08-15 18:25 ` Stephen Hemminger
2011-08-31 20:41 ` Nick Carter
2011-08-31 20:49 ` Stephen Hemminger
2011-08-31 22:00 ` Ed Swierk
2011-09-01 0:16 ` David Lamparter
2011-09-13 19:29 ` Benjamin Poirier
[not found] <CAF5U64C+WgQhfJL3zfVnvzE7p=G61humQCObHGUxAvY2-MGAFQ@mail.gmail.com>
2011-08-12 22:37 ` Ed Swierk
2011-08-12 22:45 ` Stephen Hemminger
2011-08-13 5:43 ` Ed Swierk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEJpZP10QCbKjk3sp7s7LuFHB8VMRwbpaamXwmFH3vH_NpmfMQ@mail.gmail.com \
--to=ncarter100@gmail.com \
--cc=davem@davemloft.net \
--cc=equinox@diac24.net \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).