From: Patrick McHardy <kaber@trash.net>
To: Chris Friesen <cfriesen@nortel.com>
Cc: yoshfuji@linux-ipv6.org, dada1@cosmosbay.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: "ip neigh show" not showing arp cache entries?
Date: Mon, 17 Dec 2007 19:02:05 +0100 [thread overview]
Message-ID: <4766B99D.8060408@trash.net> (raw)
In-Reply-To: <476696A5.1010101@nortel.com>
Chris Friesen wrote:
> The original "ip" command and the new one ("/tmp/ip") both give the same
> results--some of the entries are missing.
>
> root@typhoon-base-unit0:/root> ip neigh show all
> 172.24.137.0 dev bond0 FAILED
> 172.24.0.9 dev bond0 lladdr 00:07:e9:41:4b:b4 REACHABLE
> 10.41.18.101 dev eth6 lladdr 00:0e:0c:5e:95:bd REACHABLE
> 172.24.0.11 dev bond0 lladdr 00:03:cc:51:06:5e STALE
> 172.24.132.1 dev bond0 lladdr 00:01:af:14:e9:88 REACHABLE
> 172.24.0.15 dev bond0 lladdr 00:0e:0c:85:fd:d2 STALE
> 172.24.0.3 dev bond0 lladdr 00:01:af:14:c8:cc REACHABLE
> 172.24.0.5 dev bond0 lladdr 00:01:af:15:e0:6a STALE
>
> root@typhoon-base-unit0:/root> /tmp/ip neigh show all
> 172.24.137.0 dev bond0 FAILED
> 172.24.0.9 dev bond0 lladdr 00:07:e9:41:4b:b4 REACHABLE
> 10.41.18.101 dev eth6 lladdr 00:0e:0c:5e:95:bd REACHABLE
> 172.24.0.11 dev bond0 lladdr 00:03:cc:51:06:5e STALE
> 172.24.132.1 dev bond0 lladdr 00:01:af:14:e9:88 REACHABLE
> 172.24.0.15 dev bond0 lladdr 00:0e:0c:85:fd:d2 STALE
> 172.24.0.3 dev bond0 lladdr 00:01:af:14:c8:cc REACHABLE
> 172.24.0.5 dev bond0 lladdr 00:01:af:15:e0:6a STALE
>
>
> However, if I specifically try to print out one of the missing entries,
> it shows up:
>
> root@typhoon-base-unit0:/root> /tmp/ip neigh show 192.168.24.81
> 192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE
From a kernel perspective there are only complete dumps, the
filtering is done by iproute. So the fact that it shows them
when querying specifically implies there is a bug in the
iproute neighbour filter. Does it work if you omit "all"
from the ip neigh show command?
next prev parent reply other threads:[~2007-12-17 18:02 UTC|newest]
Thread overview: 19+ 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
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 [this message]
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-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=4766B99D.8060408@trash.net \
--to=kaber@trash.net \
--cc=cfriesen@nortel.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).