From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: how to display proxy arp addresses using "ip neigh" from iproute2
Date: Tue, 19 Jun 2001 11:08:10 -0400 [thread overview]
Message-ID: <3B2F6ADA.C2AD0304@nortelnetworks.com> (raw)
In-Reply-To: <3B2A0F05.6050902@niisi.msk.ru> <3B2A538A.BA62148A@linuxjedi.org> <3B2F5282.30602@niisi.msk.ru> <3B2F5BEC.A94F33A3@linuxjedi.org>
I have a small question. I have an explicit proxy arp address added to the arp
cache using the command "ip neigh add proxy 47.129.82.116 dev eth1"
Using the old-style "arp -n" command I get the following output:
Address HWtype HWaddress Flags Mask Iface
47.129.82.1 ether 00:E0:16:6C:79:42 C eth0
47.129.82.95 ether 00:20:78:07:E6:A0 C eth0
47.129.82.116 * * MP eth0
However, if I use the new-style command "ip neigh show" I get:
47.129.82.1 dev eth0 lladdr 00:e0:16:6c:79:42 nud reachable
47.129.82.95 dev eth0 lladdr 00:20:78:07:e6:a0 nud delay
How can I see what I've got set for proxy arps using the "ip neigh" command?
Help!
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2001-06-19 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 13:35 Using cramfs as root filesystem on diskless machine Alexandr Andreev
[not found] ` <14506.992621390@redhat.com>
2001-06-15 17:16 ` Alexandr Andreev
2001-06-15 18:27 ` David L. Parsley
2001-06-19 13:24 ` Alexandr Andreev
2001-06-19 14:04 ` David L. Parsley
2001-06-19 15:08 ` Christopher Friesen [this message]
2001-06-21 5:16 ` how to display proxy arp addresses using "ip neigh" from iproute2 Bernd Eckenfels
2001-06-19 15:44 ` Using cramfs as root filesystem on diskless machine Alexandr Andreev
2001-06-19 16:36 ` Stephane Casset
2001-06-17 16:28 ` Pavel Machek
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=3B2F6ADA.C2AD0304@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).