From: David Ahern <dsa@cumulusnetworks•com>
To: "Eric W. Biederman" <ebiederm@xmission•com>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH net-next v2] net: Add support for filtering neigh dump by master device
Date: Fri, 2 Oct 2015 13:51:15 -0600 [thread overview]
Message-ID: <560EE033.3040300@cumulusnetworks.com> (raw)
In-Reply-To: <87h9m9tchw.fsf@x220.int.ebiederm.org>
On 10/2/15 11:18 AM, Eric W. Biederman wrote:
> What is the thinking here because it sure looks like you are busily
> adding layer two functionality you swore you did not want.
Interfaces are enslaved to a VRF device, but neighbor entries are
installed with a reference to the actual interface not the VRF device.
This patch (plus the iproute2 one) fills a gap for usability and
debugging. I have one more patch to go and then I will send an update to
the documentation, but here is a preview (documentation update has more
detail via examples):
Using iproute2 for VRFs
1. Create a VRF
ip link add dev NAME type vrf table ID
2. List VRFs
ip [-d] link show type vrf
--> -d is needed to show table id
3. Assign a Network Interface to a VRF
ip link set dev NAME master VRF-NAME
4. Show Devices Assigned to a VRF
ip [-br] link show master VRF-NAME
5. Show Neighbor Entries for a VRF
ip [-6] neigh show master VRF-NAME
(This patch is what makes this command work efficiently.)
6. Show Addresses Assigned to Interfaces in a VRF
ip [-br][-6] addr show master VRF-NAME
7. Show Routes for a VRF
ip [-6] route show table ID
8. Route Lookup for a VRF
ip [-6] route get oif VRF-NAME ADDRESS
(This one needs a kernel patch to display the correct entry.)
David
prev parent reply other threads:[~2015-10-02 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:32 [PATCH net-next v2] net: Add support for filtering neigh dump by master device David Ahern
2015-09-30 4:28 ` roopa
2015-09-30 4:34 ` David Miller
2015-10-02 17:18 ` Eric W. Biederman
2015-10-02 19:51 ` David Ahern [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560EE033.3040300@cumulusnetworks.com \
--to=dsa@cumulusnetworks$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox