From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=XrzCwVrtEX9x0THn4fYV5Kz9vwxRpEBYKWI4W7K8u3I=; b=xcHuBFUI5k335gGr4TiRo733QpFVghbsfJ7lF5B2kF3gduX95P9/bOi6mzRLNGU6is g633nPfar6guQQi6sSfvL7WQTb8P58c+OA6QBMbDuwGcPYw1MIfKCxRI0KnGHAI3KpyR WvkOm3uab9RCJmkkLGKNZSUvJ8Tf8P9Seg717W8P85xNuJ9CBf2ZJN4TBjxcXLrrst51 GqOaSj6uMl0kzQVfJv02PX0bOLAbDWdCF4hqWWf57WCz3Aguowj7rJwf0Bitfjhui1fX p2ug3xWDnXAfipbJI9l7Rrifju+XtZVwz/+XNj8hzS2gBl80F9XBcy3UqtRhRPVqTeiT VAGw== Date: Mon, 2 Oct 2017 11:02:24 -0700 From: Stephen Hemminger Message-ID: <20171002110224.4d789600@xeon-e3> In-Reply-To: References: <1506919018-27875-1-git-send-email-roopa@cumulusnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH net-next 0/3] bridge: neigh msg proxy and flood suppression support List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Roopa Prabhu Cc: Nikolay Aleksandrov , "netdev@vger.kernel.org" , bridge@lists.linux-foundation.org, "davem@davemloft.net" On Mon, 2 Oct 2017 07:49:09 -0700 Roopa Prabhu wrote: > On Sun, Oct 1, 2017 at 9:36 PM, Roopa Prabhu wrote: > > From: Roopa Prabhu > > > > This series implements arp and nd suppression in the bridge > > driver for ethernet vpns. It implements rfc7432, section 10 > > https://tools.ietf.org/html/rfc7432#section-10 > > for ethernet VPN deployments. It is similar to the existing > > BR_ARP_PROXY flag but has a few semantic differences to conform > > to EVPN standard. In case of EVPN, it is mainly used to avoid flooding to > > tunnel ports like vxlan/mpls. Unlike the existing flags it suppresses flood > > of all neigh discovery packets (arp, nd) to tunnel ports. > > > > Roopa Prabhu (3): > > bridge: add new BR_NEIGH_SUPPRESS port flag to suppress arp and nd > > flood > > neigh arp suppress first > > bridge: suppress nd messages from going to BR_NEIGH_SUPPRESS ports > > > > pls ignore, shows conflict applying over recent net-next bridge > changes. Will rebase and submit v2. Ok, but the concept looks good. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH net-next 0/3] bridge: neigh msg proxy and flood suppression support Date: Mon, 2 Oct 2017 11:02:24 -0700 Message-ID: <20171002110224.4d789600@xeon-e3> References: <1506919018-27875-1-git-send-email-roopa@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "davem@davemloft.net" , "netdev@vger.kernel.org" , Nikolay Aleksandrov , bridge@lists.linux-foundation.org To: Roopa Prabhu Return-path: Received: from mail-pf0-f177.google.com ([209.85.192.177]:43444 "EHLO mail-pf0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751236AbdJBSCc (ORCPT ); Mon, 2 Oct 2017 14:02:32 -0400 Received: by mail-pf0-f177.google.com with SMTP id d2so72533pfh.0 for ; Mon, 02 Oct 2017 11:02:32 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Mon, 2 Oct 2017 07:49:09 -0700 Roopa Prabhu wrote: > On Sun, Oct 1, 2017 at 9:36 PM, Roopa Prabhu wrote: > > From: Roopa Prabhu > > > > This series implements arp and nd suppression in the bridge > > driver for ethernet vpns. It implements rfc7432, section 10 > > https://tools.ietf.org/html/rfc7432#section-10 > > for ethernet VPN deployments. It is similar to the existing > > BR_ARP_PROXY flag but has a few semantic differences to conform > > to EVPN standard. In case of EVPN, it is mainly used to avoid flooding to > > tunnel ports like vxlan/mpls. Unlike the existing flags it suppresses flood > > of all neigh discovery packets (arp, nd) to tunnel ports. > > > > Roopa Prabhu (3): > > bridge: add new BR_NEIGH_SUPPRESS port flag to suppress arp and nd > > flood > > neigh arp suppress first > > bridge: suppress nd messages from going to BR_NEIGH_SUPPRESS ports > > > > pls ignore, shows conflict applying over recent net-next bridge > changes. Will rebase and submit v2. Ok, but the concept looks good.