Ok here are the tcpdumps....the one labeled tcpdump_on_my_eth0.txt is the tcpdump which was monitoring my pcs eth0 (the one which isnt working). The other one was loaded on my gateways eth0. During both dumps I was ping from both sides.
I don really think there is much useful info in them, but I posted them just for a complete picture Adam Hewitt wrote: > The thing is though, if I revert back to 2.2.17 kernel, everything > works fine...so its not cabling, and its not the other computers... > > I will tcpdump and see if the packets are actually leaving the > interface... > > btw when I said I can ping my IP address and my loopback address, I > meant I was able to do it from the same machine as the problem...if > that changes anything... > > James Gregory wrote: > >> It looks like the driver has loaded fine and that ifconfig has >> attached eth0 to that driver. If you can ping the ethernet address >> then the problem is quite likely not actually in your computer. Bring >> the interface down and up, check cables, check other machines can >> ping other machines. Try a broadcast ping and see what you can see >> and maybe try tcpdump to see if the interface can see anything at all. >> >> HTH, >> >> James. >> >> Adam Hewitt wrote: >>
01:13:35.947668 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:36.942752 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:37.942745 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:38.942848 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:39.942743 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:40.942744 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:41.942817 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:42.942742 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:43.942742 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:44.942792 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:45.942743 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:46.942755 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:47.942828 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:50.643510 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:50.643521 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:50.942883 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:51.942746 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:52.942745 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:53.942813 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:54.942744 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:55.942747 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:56.942808 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:57.942745 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:58.942743 arp who-has 192.168.0.1 tell wolverine.Mshome 01:13:59.942806 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:00.942746 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:01.942746 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:02.942814 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:03.942745 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:04.942746 arp who-has 192.168.0.1 tell wolverine.Mshome 01:14:05.942836 arp who-has 192.168.0.1 tell wolverine.Mshome
23:14:25.772039 arp who-has Gateway tell superbox 23:14:26.768932 arp who-has Gateway tell superbox 23:14:27.768929 arp who-has Gateway tell superbox 23:14:28.769141 arp who-has Gateway tell superbox 23:14:29.768932 arp who-has Gateway tell superbox 23:14:30.768923 arp who-has Gateway tell superbox 23:14:31.769098 arp who-has Gateway tell superbox 23:14:32.768922 arp who-has Gateway tell superbox 23:14:33.768921 arp who-has Gateway tell superbox 23:14:34.769091 arp who-has Gateway tell superbox 23:14:35.768923 arp who-has Gateway tell superbox 23:14:36.768921 arp who-has Gateway tell superbox 23:14:37.769084 arp who-has Gateway tell superbox 23:14:38.768924 arp who-has Gateway tell superbox 23:14:39.768926 arp who-has Gateway tell superbox
