On Sat, 7 Jun 2003, James P. Roberts wrote:
> > problem solved...I replaced the NIC...working fine now...
> >
> > what actually led me to replace this NIC was:
> >
> > while monitoring the packets on my RH with tcpdump, I pinged from RH; I
> watched requests go to the windows box, and watched replies come back to RH,
> but ping never reported that any got received; while pinging from windows box,
> I watched requests come into RH, but no replies were ever sent back, and thus,
> the windows ping also reported 100% packet loss...
> >
> > I don't quite understand how tcpdump was recording the acceptance of packets
> while ping wasn't?! If anyone can explain this phenomena, please do!
> >
>
> Kevin:
>
> I had a similar problem a while back, after a power failure. Same symptoms,
> which was that I could do a "partial" ping, as you described. Same solution,
> too. Replaced the NIC card. Wish I had an explanation, but I do not. But I
> thought you'd appreciate knowing you were not alone in your experience.
>
> If anyone else has an explanation for us, please share!
>
Since tcpdump puts the NIC in promiscuous mode, it would accept
everything even if something were wrong with the part of its circuitry
that normally decides if packets are for your own IP.
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/seawolf-list
