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
--
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]
