Re: "ip neigh show" not showing arp cache entries?
On Wed, Dec 19, 2007 at 08:28:49AM -0600, Chris Friesen wrote: > > I've included the traces below, they're pretty long. I don't know > enough about the netlink format to trace the responses, but I did notice > one interesting thing. > > In the "ip neigh show" case the "bond2" entry isn't printed out, but I > can see the string "bond2" in the recvmsg() call so it looks like the Actually bond2 isn't in the recvmsg, it's just that strace is printing out the complete content of the buffer which happenes to include bond2. I've verified that the first recvmsg indeed does not contain the bond2 address at all. Instead of the first 3 IPv4 records it has 3 IPv6 records. So we seem to have a kernel problem here. However, too many changes have been made in this area since 2.6.14 for it to be worthwhile for me to debug this any further until you manage to reproduce it with the current kernel. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
On Tue, Dec 18, 2007 at 08:52:01AM -0600, Chris Friesen wrote: > > Looks like that did it. Why does specifying the family make a difference? Because this is the only parameter that changes kernel behaviour. Next step is to strace both commands with -s 16384 to see exactly what the kernel reply looks like to determine the problem. BTW my emails to you are bouncing so you might want to fix that. Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Herbert Xu wrote: Chris Friesen <[EMAIL PROTECTED]> wrote: However, if I specifically try to print out one of the missing entries, it shows up: [EMAIL PROTECTED]:/root> /tmp/ip neigh show 192.168.24.81 192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE What about ip -4 neigh show Looks like that did it. Why does specifying the family make a difference? [EMAIL PROTECTED]:/root> ip neigh show 10.41.18.1 dev eth6 lladdr 00:00:5e:00:01:01 STALE 172.24.137.0 dev bond0 lladdr 00:c0:8b:08:e4:88 REACHABLE 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 [EMAIL PROTECTED]:/root> ip -4 neigh show 192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE 172.24.132.2 dev bond0 FAILED 172.24.136.0 dev bond0 lladdr 00:c0:8b:07:b3:7e REACHABLE 10.41.18.1 dev eth6 lladdr 00:00:5e:00:01:01 STALE 172.24.137.0 dev bond0 lladdr 00:c0:8b:08:e4:88 REACHABLE 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 Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Chris Friesen <[EMAIL PROTECTED]> wrote: > > However, if I specifically try to print out one of the missing entries, > it shows up: > > [EMAIL PROTECTED]:/root> /tmp/ip neigh show 192.168.24.81 > 192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE What about ip -4 neigh show Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Thomas Graf wrote: * Patrick McHardy <[EMAIL PROTECTED]> 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 " does show the missing entries, and in case of neighbour entries all filtering is done in userspace. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
* Patrick McHardy <[EMAIL PROTECTED]> 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. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
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. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
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". Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Chris Friesen wrote: The original "ip" command and the new one ("/tmp/ip") both give the same results--some of the entries are missing. [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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: [EMAIL PROTECTED]:/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? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
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: [EMAIL PROTECTED]:/root> arp -n Address HWtype HWaddress Flags MaskIface 192.168.24.81ether 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. [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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: [EMAIL PROTECTED]:/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 netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
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. --yoshfuji -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Eric Dumazet wrote: And what is the version of "ip" command you have on this machine ? ip -V iproute2-ss051107 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? Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Chris Friesen a écrit : Eric Dumazet wrote: Chris Friesen a écrit : Is this expected behaviour? Probably not... Still a 2.6.14 kernel ? Yep. Embedded hardware, so I'm unable to test with a more recent kernel. And what is the version of "ip" command you have on this machine ? ip -V You may try other versions of this command http://devresources.linux-foundation.org/dev/iproute2/download/ -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Eric Dumazet wrote: Chris Friesen a écrit : Is this expected behaviour? Probably not... Still a 2.6.14 kernel ? Yep. Embedded hardware, so I'm unable to test with a more recent kernel. Could you send the result of : strace ip neigh show I've attached two strace runs, one of "ip neigh show" and one of "ip neigh show 10.41.18.101". Chris [EMAIL PROTECTED]:/tftpboot/cnp/0-0-5-0/0-0-5-0> strace ip neigh show execve("/sbin/ip", ["ip", "neigh", "show"], [/* 14 vars */]) = 0 uname({sys="Linux", node="typhoon-base-unit0", ...}) = 0 brk(0) = 0x806b000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=58478, ...}) = 0 mmap2(NULL, 58478, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f56000 close(3)= 0 open("/lib/libresolv.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\"\0"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=75541, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f55000 mmap2(NULL, 71816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f43000 mmap2(0xb7f51000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe) = 0xb7f51000 mmap2(0xb7f53000, 6280, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f53000 close(3)= 0 open("/lib/libc.so.6", O_RDONLY)= 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\216O\1"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1407983, ...}) = 0 mmap2(NULL, 1146076, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e2b000 mmap2(0xb7f39000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x10d) = 0xb7f39000 mmap2(0xb7f41000, 7388, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f41000 close(3)= 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e2a000 mprotect(0xb7f39000, 20480, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e2a6b0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0xb7f56000, 58478) = 0 socket(PF_NETLINK, SOCK_RAW, 0) = 3 setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0 setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0 bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0 getsockname(3, {sa_family=AF_NETLINK, pid=6150, groups=}, [12]) = 0 time(NULL) = 1197465643 sendto(3, "\24\0\0\0\22\0\1\3,\340_G\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=}, msg_iov(1)=[{"\364\0\0\0\20\0\2\0,\340_G\6\30\0\0\0\0\1\0\1\0\0\0C\30"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 3544 brk(0) = 0x806b000 brk(0x808c000) = 0x808c000 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0,\340_G\6\30\0\0\0\0\0\0\1\0\0\0C\30\0"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 20 sendto(3, "\24\0\0\0\36\0\1\3-\340_G\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=}, msg_iov(1)=[{"[EMAIL PROTECTED]"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 264 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=}, msg_iov(1)=[{"[EMAIL PROTECTED]"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 20 exit_group(0) = ? Process 6150 detached [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/tftpboot/cnp/0-0-5-0/0-0-5-0> strace ip neigh show 10.41.18.101 execve("/sbin/ip", ["ip", "neigh", "show", "10.41.18.101"], [/* 14 vars */]) = 0 uname({sys="Linux", node="typhoon-base-unit0", ...}) = 0 brk(0) = 0x806b000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=58478, ...}) = 0 mmap2(NULL, 58478, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fd5000 close(3)= 0 open("/lib/libresolv.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\"\0"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=75541, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7fd4000 mmap2(NULL, 71816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7fc2000 mmap2(0xb7fd, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,
Re: "ip neigh show" not showing arp cache entries?
Chris Friesen a écrit : I retested it on an x86 machine and am seeing similar problems. First, "arp" gives the arp table as expected: [EMAIL PROTECTED]:/tftpboot/cnp/0-0-5-0/0-0-5-0> arp -n Address HWtype HWaddress Flags MaskIface 172.24.0.9 ether 00:03:CC:51:06:5E Cbond0 10.41.18.101 ether 00:0E:0C:5E:95:BD Ceth6 172.24.137.0 ether 00:C0:8B:08:E4:88 Cbond0 172.24.136.0 ether 00:C0:8B:07:B3:7E Cbond0 10.41.18.1 ether 00:00:5E:00:01:01 Ceth6 172.24.0.5 ether 00:01:AF:15:E0:6A Cbond0 172.24.0.13 ether 00:0E:0C:85:FD:D2 Cbond0 172.24.0.3 ether 00:01:AF:14:C8:CC Cbond0 172.24.132.1 ether 00:01:AF:14:E9:88 Cbond0 172.24.0.7 ether 00:07:E9:41:4B:B4 Cbond0 192.168.24.81ether 00:01:AF:14:E9:8A Cbond2 "ip neigh show" gives nothing, but if I search for specific addresses from the arp table listing they show up: [EMAIL PROTECTED]:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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? Probably not... Still a 2.6.14 kernel ? Could you send the result of : strace ip neigh show -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
I retested it on an x86 machine and am seeing similar problems. First, "arp" gives the arp table as expected: [EMAIL PROTECTED]:/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.81ether 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: [EMAIL PROTECTED]:/tftpboot/cnp/0-0-5-0/0-0-5-0> ip neigh show [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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 netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: "ip neigh show" not showing arp cache entries?
Chris Friesen wrote: I'm seeing some strange behaviour on a 2.6.14 ppc64 system. If I run "ip neigh show" it prints out nothing, but if I run "arp" then I see the other nodes on the local network. [EMAIL PROTECTED]:/root> ip neigh show [EMAIL PROTECTED]:/root> arp -n Address HWtype HWaddress Flags MaskIface 172.24.132.0 ether 00:01:AF:14:E8:DA Cbond0 172.24.132.1 (incomplete)bond0 172.24.136.0 ether 00:C0:8B:07:B3:7E Cbond0 172.24.132.4 ether 00:01:AF:14:E8:DA Cbond0 172.24.132.2 ether 00:01:AF:14:E8:DA Cbond0 Any ideas what's going on here? I've got some further information. If I look for a specific address, it seems to work: [EMAIL PROTECTED]:/root> ip neigh show 172.24.136.0 172.24.136.0 dev bond0 lladdr 00:c0:8b:07:b3:7e REACHABLE In the above scenario, the arp cache lists the device as reachable via bond0. If I search the arp cache to see whether the address is reachable from one of bond0's slave devices, should it come back positive or negative? Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html