On Fri, 2005-05-06 at 11:37 -0400, James Knott wrote:
Ken Schneider wrote:
On Fri, 2005-05-06 at 10:39 -0400, James Knott wrote:
Check your routing setup.
What routing? The computer is receiving the "Neighbor Solicitation" request, but not responding. The computers are sitting on my desk, with only the switch between them.
Here's the ifconfig for both systems.
eth0 Link encap:Ethernet HWaddr 00:05:5D:F6:04:CE inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::205:5dff:fef6:4ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:603728 errors:0 dropped:0 overruns:0 frame:0 TX packets:656548 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:274969413 (262.2 Mb) TX bytes:135805308 (129.5 Mb) Interrupt:10 Base address:0xa800
eth0 Link encap:Ethernet HWaddr 00:00:E2:8A:26:AA inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::200:e2ff:fe8a:26aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5332 (5.2 Kb) TX bytes:5133 (5.0 Kb)
And /proc/net/ipv6_route shows
00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000002a 80200001 lo fe8000000000000002055dfffef604ce 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 0000009b 80200001 lo fe800000000000000000000000000000 40 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 ff000000000000000000000000000000 08 00000000000000000000000000000000 00 00000000000000000000000000000000 00000100 00000000 00000000 00000001 eth0 00000000000000000000000000000000 00 00000000000000000000000000000000 00 00000000000000000000000000000000 ffffffff 00000001 00000006 00200200 lo
I don't see any route command info on IPv6.
Still every computer needs a "default" route if it on a network and on linux every machine has two interfaces (if it has a network card or modem), in your case eth0 and lo (the loopback interface). Since the machine can only ping itself it is probably using the lo interface. Just type route -n (as root) for the routing table. The most likely reason that computer "A" can only ping itself but answer ping requests is that the requests will return on the same interface the request was received on but doesn't know where to send the initial request. This is just my guess. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge