Moving to linux-net because it's more appropriate there, don't you think? it works fine for me. Maybe you can give some more info on just exactly what you're doing and what's failing? # uname -r 2.4.16 # netstat -rn|grep 0.0.0.0 (edited :) 0.0.0.0 172.22.1.1 0.0.0.0 UG 40 0 0 eth0 # arp 172.22.1.1 Address HWtype HWaddress Flags Mask Iface 172.22.1.1 ether 00:60:97:05:91:3A C eth0 # ping 172.22.1.1 PING 172.22.1.1 (172.22.1.1): 56 octets data 64 octets from 172.22.1.1: icmp_seq=0 ttl=255 time=0.4 ms --- 172.22.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 0.4/0.4/0.4 ms > -----Original Message----- > From: Alex [mailto:mail_ker@xarch.tu-graz.ac.at] > Sent: December 21, 2001 08:43 > To: linux-kernel@vger.kernel.org > Subject: conclusion: arp.c *must* be (still) defective > > > > Dear Mailing List, > > I'm having great problems with ARP. Frankly, kernel 2.4.16 > never gets the > proper arp address of the next-hop-router, no matter what I try. > > My equipment: > > Suse 7.3 , kernel upgraded to 2.4.16 > 3com 3c509-b tx isapnp ethcard eth0 > msi-something geforce2mx 200 > sb16 isapnp > thunderbird 1.2 ghz > gigabyte 7ixe4 motherboard > 512 mb ram @ 100 mhz fsb > > I can only ping the IP of the network card itself. > > Whenever I ping my nexthop router (ip: x.x.x.1) i get a pause of a few > seconds, then a whole sequence of "Destination unreachable". > Looking at the arp cache using "arp -a", I see that the arp cache is > always incomplete (always KEEPS being incomplete). > > Any clue is greatly appreciated, but I do suspect that the > kernel 2.4.16's > ARP code is buggy since Win98 , win2k etc works flawlessly. > > Yours > > Alex > > > - > : send the line "unsubscribe > linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
