From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lamparter Subject: Re: [RFC] bridge: add netfilter hook for forwarding 802.1D group addresses Date: Mon, 22 Aug 2011 15:59:29 +0200 Message-ID: <20110822135929.GA611458@jupiter.n2.diac24.net> References: <20110812154545.79d8313f@nehalam.ftrdhcpuser.net> <20110815150501.3a6cc432@nehalam.ftrdhcpuser.net> <20110818081019.4b9bb79e@nehalam.ftrdhcpuser.net> <20110818093941.5ebf716b@nehalam.ftrdhcpuser.net> <20110819022731.GC180151@jupiter.n2.diac24.net> <20110819135810.1a529ab2@nehalam.ftrdhcpuser.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Lamparter , Nick Carter , Ed Swierk , netdev@vger.kernel.org, bridge@linux-foundation.org, netfilter-devel@vger.kernel.org, David Miller To: Stephen Hemminger Return-path: Received: from spaceboyz.net ([87.106.131.203]:58809 "EHLO spaceboyz.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751788Ab1HVN7r (ORCPT ); Mon, 22 Aug 2011 09:59:47 -0400 Content-Disposition: inline In-Reply-To: <20110819135810.1a529ab2@nehalam.ftrdhcpuser.net> Sender: netdev-owner@vger.kernel.org List-ID: 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