netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: Chris Friesen <cfriesen@nortel.com>,
	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: Tue, 18 Dec 2007 01:35:39 +0100	[thread overview]
Message-ID: <476715DB.6050808@trash.net> (raw)
In-Reply-To: <20071218003312.GR11220@postel.suug.ch>

Thomas Graf wrote:
> * Patrick McHardy <kaber@trash.net> 2007-12-18 00:51
>> Chris Friesen wrote:
>>> Patrick McHardy wrote:
>>>
>>>> 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?
>>>
>>> Omitting "all" gives identical results.  It is still missing entries 
>>> when compared with the output of "arp".
>>
>> In that case the easiest way to debug this is probably if you
>> add some debugging to ip/ipneigh.c:print_neigh() since I'm
>> unable to reproduce this problem. A printf for all the filter
>> conditions (=> return 0) at the top should do.
> 
> Alternatively, you can download libnl and run
> 
> 	NLCB=debug src/nl-neigh-dump brief
> 
> and check if the netlink message is sent by the kenrel for the
> neighbour in question. 


It should be, according to Chris, "ip neigh show <ip>" does
show the missing entries, and in case of neighbour entries
all filtering is done in userspace.



  reply	other threads:[~2007-12-18  0:35 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
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 [this message]
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=476715DB.6050808@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=tgraf@suug.ch \
    --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).