[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJieiUim2XLMGAomb3S5AeWfYqjxV_raetedWcA_PBiaGPRHWg@mail.gmail.com>
Date: Mon, 2 Oct 2017 07:49:09 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: "davem@...emloft.net" <davem@...emloft.net>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
"stephen@...workplumber.org" <stephen@...workplumber.org>,
bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next 0/3] bridge: neigh msg proxy and flood
suppression support
On Sun, Oct 1, 2017 at 9:36 PM, Roopa Prabhu <roopa@...ulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> 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.
Powered by blists - more mailing lists