I had this experience and on researching it learned that the drivers
for gigabit ethernet setups defer the checksum calculation to
hardware. So when your software tells it to send a packet, the driver
does not compute the checksum, the chip does. Problem is that when
you use a capture utility like ethereal it sees the packet before the
chip does and reports the error. That is why it is "normal" to see
this.
I would believe that netstat queries the hardware and that is why the
hardware reports no errors.
On 4/21/06, Tony Wasson <
ajwasson@gmail.com> wrote:
> On 4/21/06, Shawn Badger <sbadger@cskauto.com> wrote:
> > I am seeing TCP checksum errors on one of my servers via Ethereal. I
> > have Googled looking for ways diagnose and correct the problem, but I
> > have found none. I checked with "netstat -a -i eth0" and saw no RX
> > errors, so I am left to wonder if it is the network, the multiple
> > servers I get the errors from or the server I am monitoring. So I am
> > hoping someone out there can point me in the right direction.
> >
>
> If you are doing your packet capture from your server, this is normal.
> http://www.ethereal.com/faq.html#q11.1
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
--
Nothing is really work unless you would rather be doing something else.
- James M. Barrie
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss