From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode Date: Thu, 2 May 2013 21:37:58 +0300 Message-ID: <20130502183758.GA16031@redhat.com> References: <1366404770-28523-1-git-send-email-vyasevic@redhat.com> <20130502102331.43728912@nehalam.linuxnetplumber.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Vlad Yasevich , netdev@vger.kernel.org, bridge@lists.linux-foundation.org To: Stephen Hemminger Return-path: Content-Disposition: inline In-Reply-To: <20130502102331.43728912@nehalam.linuxnetplumber.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: bridge-bounces@lists.linux-foundation.org Errors-To: bridge-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org On Thu, May 02, 2013 at 10:23:31AM -0700, Stephen Hemminger wrote: > Doing research on another problem, I noticed that this would > break user mode spanning tree (RSTP) code. > > The daemon assumes that bridge is promicious mode and therefore > will receive all link-level multicast packets. Since you have to play with the new learning/flooding options to get the non promisc behaviour, can't we just say "don't do it then" short term, and fix applcations long term?