From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 19 Aug 2011 15:24:15 -0700 From: Stephen Hemminger Message-ID: <20110819152415.00e1c795@nehalam.ftrdhcpuser.net> In-Reply-To: <184D23435BECB444AB6B9D4630C8EC830258A300@XMB-RCD-303.cisco.com> 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> <184D23435BECB444AB6B9D4630C8EC830258A300@XMB-RCD-303.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [RFC] bridge: add netfilter hook for forwarding 802.1D group addresses List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Christian Benvenuti (benve)" Cc: bridge@linux-foundation.org, Ed Swierk , Nick Carter , netfilter-devel@vger.kernel.org, netdev@vger.kernel.org, David Lamparter On Fri, 19 Aug 2011 17:18:04 -0500 "Christian Benvenuti (benve)" wrote: > The patch description and the code are clearly saying that STP is > an exception, but I am just worried about the users. > Maybe a proper description in the iptables help is sufficient. > > Users may otherwise try to use this new hook for STP too > (for example to generate logs or produce statistics/counters > or divert STP traffic to userspace, etc). STP traffic already goes to userspace. And gets processed by the LOCAL_IN chain. So I don't think it is needed. > Out of curiosity, ... if this gets accepted, shouldn't you provide > NF_BR_LINK_LOCAL_OUT too? > Or maybe you should call it NF_BR_LINK_LOCAL_FWD instead of > NF_BR_LINK_LOCAL_IN? Thanks, that is a better name, I'll change it in next version.