From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ido Schimmel Subject: Re: [PATCH 1/1] bridge: remove BR_GROUPFWD_RESTRICTED for arbitrary forwarding of reserved addresses Date: Mon, 1 Oct 2018 22:04:33 +0300 Message-ID: <20181001190433.GA29874@splinter> References: <1420505776-26827-1-git-send-email-bernhard.thaler@wvnet.at> <2327925.x0GQ7AZp12@blindfold> <20181001184821.GA29148@splinter> <2473404.DTJdS9eVm5@blindfold> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stephen Hemminger , Florian Fainelli , bernhard.thaler@wvnet.at, "David S. Miller" , bridge@lists.linux-foundation.org, netdev@vger.kernel.org, David Gstir , nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com To: Richard Weinberger Return-path: Received: from out3-smtp.messagingengine.com ([66.111.4.27]:59843 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725958AbeJBBnt (ORCPT ); Mon, 1 Oct 2018 21:43:49 -0400 Content-Disposition: inline In-Reply-To: <2473404.DTJdS9eVm5@blindfold> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Oct 01, 2018 at 08:54:08PM +0200, Richard Weinberger wrote: > So the only option is having a bridge and transport STP via tc-mirred > or patching the bridge code (what we do right now). And I vote for the first option. I understand it involves more typing, but I see no reason to push more complexity into the kernel - and break standards - when you can relatively easily accomplish the same thing in other ways. Adding Nik and Roopa who now maintain the bridge code and should eventually decide about this.