Re: "ip neigh show" not showing arp cache entries?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



YOSHIFUJI Hideaki / 吉藤英明 wrote:
In article <[email protected]> (at Wed, 12 Dec 2007
15:57:08 -0600), "Chris Friesen" <[email protected]> says:

You may try other versions of this command

http://devresources.linux-foundation.org/dev/iproute2/download/

They appear to be numbered by kernel version, and the above version
is the most recent one for 2.6.14.  Will more recent ones (for
newer kernels) work with my kernel?

It should work; if it doesn't, please make a report.  Thanks.

I downloaded iproute2-2.6.23 and built it for my kernel.

I'm compiling for a different kernel than is actually running on the build system, so I had to add a line defining KERNEL_INCLUDE to the Makefile, and I had to add "-I${KERNEL_INCLUDE}" to the CFLAGS definition. Someone might want to do something about that...

Anyways, the arp entry issue is still there. The "arp" command gives a bunch of entries:

root@typhoon-base-unit0:/root> arp -n
Address          HWtype  HWaddress           Flags Mask            Iface
192.168.24.81    ether   00:01:AF:14:E9:8A   C                     bond2
172.24.132.2             (incomplete)                              bond0
172.24.136.0     ether   00:C0:8B:07:B3:7E   C                     bond0
172.24.137.0             (incomplete)                              bond0
172.24.0.9       ether   00:07:E9:41:4B:B4   C                     bond0
10.41.18.101     ether   00:0E:0C:5E:95:BD   C                     eth6
172.24.0.11      ether   00:03:CC:51:06:5E   C                     bond0
172.24.132.1     ether   00:01:AF:14:E9:88   C                     bond0
172.24.0.15      ether   00:0E:0C:85:FD:D2   C                     bond0
172.24.0.3       ether   00:01:AF:14:C8:CC   C                     bond0
172.24.0.5       ether   00:01:AF:15:E0:6A   C                     bond0

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


Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux