> root@dSC:/digital# ping 198.162.0.100 -c 25
> PING 198.162.0.100 (198.162.0.100): 56 data bytes
> --- 198.162.0.100 ping statistics ---
> 25 packets transmitted, 0 packets received, 100% packet loss
>
> Which kinda made me curious. So, I ran tcpdump -i eth0
> and... viola.. I got these results
>
> root@dSC:~# tcpdump -i eth0
> tcpdump: listening on eth0
> 10:31:39.887117 arp who-has 198.162.0.100 tell 198.162.0.50
> 10:31:44.883816 arp who-has 198.162.0.100 tell 198.162.0.50
> 10:31:49.883810 arp who-has 198.162.0.100 tell 198.162.0.50
> 10:31:54.883820 arp who-has 198.162.0.100 tell 198.162.0.50
> 10:32:35.596246 b5:0:2f:0:20:0 ad:0:11:0:26:0 ef00 60:
> 4300 5600 5400 2600 f000 7200 b300 9900
> fd00 ffff ffff ffff ffff ffff ffff ffff
> ffff ffff ffff ffff ffff ffff ffff
Looks like a multicast packet; is that "ad:0:" address the windoze or
Linux machine's card?
Hmm. Can you try both the following:
a) Try pinging the Linux box from the windoze box while running
tcpdump on the Linux box, and see if it's seeing anything on the wire?
Just to make sure windoze is at least trying to run IP over the
ethernet...
b) Give Linux a permanent arp entry for the windoze machine's ethernet
hardware address, and then see if you can ping to it then...
Good luck...
Adam
-- Things look so bad everywhere Adam D. Bradley artdodge@cs.bu.edu In this whole world what is fair Boston University Computer Science We walk blind and we try to see Ph.D. student and Linux hacker Falling behind in what could be ----> Bring me a Higher Love ----> <><