From: "Chris Friesen" <cfriesen@nortel.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: "ip neigh show" not showing arp cache entries?
Date: Wed, 12 Dec 2007 10:21:02 -0600 [thread overview]
Message-ID: <47600A6E.8000202@nortel.com> (raw)
In-Reply-To: <475D7D70.5030502@nortel.com>
I retested it on an x86 machine and am seeing similar problems.
First, "arp" gives the arp table as expected:
root@typhoon-base-unit0:/tftpboot/cnp/0-0-5-0/0-0-5-0> arp -n
Address HWtype HWaddress Flags Mask
Iface
172.24.0.9 ether 00:03:CC:51:06:5E C
bond0
10.41.18.101 ether 00:0E:0C:5E:95:BD C
eth6
172.24.137.0 ether 00:C0:8B:08:E4:88 C
bond0
172.24.136.0 ether 00:C0:8B:07:B3:7E C
bond0
10.41.18.1 ether 00:00:5E:00:01:01 C
eth6
172.24.0.5 ether 00:01:AF:15:E0:6A C
bond0
172.24.0.13 ether 00:0E:0C:85:FD:D2 C
bond0
172.24.0.3 ether 00:01:AF:14:C8:CC C
bond0
172.24.132.1 ether 00:01:AF:14:E9:88 C
bond0
172.24.0.7 ether 00:07:E9:41:4B:B4 C
bond0
192.168.24.81 ether 00:01:AF:14:E9:8A C
bond2
"ip neigh show" gives nothing, but if I search for specific addresses
from the arp table listing they show up:
root@typhoon-base-unit0:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show
root@typhoon-base-unit0:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show
172.24.0.9
172.24.0.9 dev bond0 lladdr 00:03:cc:51:06:5e DELAY
root@typhoon-base-unit0:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show
10.41.18.101
10.41.18.101 dev eth6 lladdr 00:0e:0c:5e:95:bd REACHABLE
root@typhoon-base-unit0:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show
172.24.137.0
172.24.137.0 dev bond0 lladdr 00:c0:8b:08:e4:88 REACHABLE
Is this expected behaviour?
Thanks,
Chris
next prev parent reply other threads:[~2007-12-12 16:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 17:36 "ip neigh show" not showing arp cache entries? Chris Friesen
2007-12-10 17:54 ` Chris Friesen
2007-12-12 16:21 ` Chris Friesen [this message]
2007-12-12 16:46 ` Eric Dumazet
2007-12-12 18:25 ` Chris Friesen
2007-12-12 18:52 ` Eric Dumazet
2007-12-12 21:57 ` Chris Friesen
2007-12-12 22:06 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-17 15:32 ` Chris Friesen
2007-12-17 18:02 ` Patrick McHardy
2007-12-17 19:47 ` Chris Friesen
2007-12-17 23:51 ` Patrick McHardy
2007-12-18 0:33 ` Thomas Graf
2007-12-18 0:35 ` Patrick McHardy
2007-12-18 3:33 ` Herbert Xu
2007-12-18 14:52 ` Chris Friesen
2007-12-19 1:14 ` Herbert Xu
2007-12-19 14:28 ` Chris Friesen
2007-12-19 14:28 ` Chris Friesen
2007-12-25 1:06 ` Herbert Xu
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=47600A6E.8000202@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.