[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110822135929.GA611458@jupiter.n2.diac24.net>
Date: Mon, 22 Aug 2011 15:59:29 +0200
From: David Lamparter <equinox@...c24.net>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: David Lamparter <equinox@...c24.net>,
Nick Carter <ncarter100@...il.com>,
Ed Swierk <eswierk@...switch.com>, netdev@...r.kernel.org,
bridge@...ux-foundation.org, netfilter-devel@...r.kernel.org,
David Miller <davem@...emloft.net>
Subject: Re: [RFC] bridge: add netfilter hook for forwarding 802.1D group
addresses
On Fri, Aug 19, 2011 at 01:58:10PM -0700, Stephen Hemminger wrote:
> The IEEE standard expects that link local multicast packets will not
> be forwarded by a bridge. But there are cases like 802.1X which may
> require that packets be forwarded. For maximum flexibilty implement
> this via netfilter.
>
> The netfilter chain is slightly different from other chains in that
> if packet is ACCEPTED by the chain, it means it should be forwarded.
> And if the packet verdict result is DROP, the packet is processed
> as a local packet.
Exactly this functionality already exists by way of the BROUTING chain
in the broute table. Currently, link-local packets are hardcodedly
treated as local before they even reach that chain. Nick's patch, in
conjunction with BROUTING, provides exactly what you're trying to do.
Now, without bridge netfilter, your patch becomes rather useless while
Nick's patch still allows per-group (and therefore per-protocol)
control.
Further, Nick's patch is considerably less intrusive.
I would therefore ask for Nick's patch to be merged.
-David
P.S.: this whole issue is starting to get rather annoying
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists