On Sat, 13 Jul 2002, Ian Douglas wrote:
The thing that immediately strikes me is that it is the RX and TX packet count on lo rather than eth0 that is incrementing after each ping.
If I look at /var/log/messages I see the following message repeated several times:
Jul 13 22:59:52 chocchip kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 13 22:59:52 chocchip kernel: eth0: Tx queue start entry 4 dirty entry 0. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 0 is 00002000. (queue head) Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 1 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 2 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 3 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
Can someone more knowledgeable than myself suggest what is going on?
Hi,
Do you have any other machines on your network?
One thing you could try is ping -b 192.168.255.255
This will ping the broadcast address, so if other machines are talking you should get a response. WARNING: DO NOT TRY THIS ON BIG NETWORKS AS IT DOES CAUSE LOTS OF PROBLEMS, BUT ON A SMALL HOME NETWORK YOU CAN GET AWAY WITH IT.
Are the lights on on the hub saying the machine is connected?
try running
tcpdump -i eth0
on one virtual terminal and then pinging from a different one, and see what you get back.
Are you sure you're using the correct driver for your ethernet card?
Hope that helps
Chris