From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] neighbour: support for NTF_EXT_LEARNED flag Date: Wed, 25 Apr 2018 13:20:58 -0400 (EDT) Message-ID: <20180425.132058.208675778907308410.davem@davemloft.net> References: <1524602974-11476-1-git-send-email-roopa@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, nikolay@cumulusnetworks.com, dsa@cumulusnetworks.com To: roopa@cumulusnetworks.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:52514 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755203AbeDYRVA (ORCPT ); Wed, 25 Apr 2018 13:21:00 -0400 In-Reply-To: <1524602974-11476-1-git-send-email-roopa@cumulusnetworks.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Roopa Prabhu Date: Tue, 24 Apr 2018 13:49:34 -0700 > From: Roopa Prabhu > > This patch extends NTF_EXT_LEARNED support to the neighbour system. > Example use-case: An Ethernet VPN implementation (eg in FRR routing suite) > can use this flag to add dynamic reachable external neigh entires > learned via control plane. The use of neigh NTF_EXT_LEARNED in this > patch is consistent with its use with bridge and vxlan fdb entries. > > Signed-off-by: Roopa Prabhu No objection to the patch or the facility, so applied, thanks. What exactly is the name of this VPN technology in the FRR routing suite?