From: Rick Jones <rick.jones2@hp.com>
To: Gaurav Aggarwal <grv.aggarwal@gmail.com>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
davidsen@tmr.com
Subject: Re: Bad TCP checksum error
Date: Fri, 26 Oct 2007 09:59:16 -0700 [thread overview]
Message-ID: <47221CE4.70103@hp.com> (raw)
In-Reply-To: <1a41e0840710260903w33516f62kc53e5eb56e424d69@mail.gmail.com>
Checksum Offload on the NIC(s) can complicate things. First, if you are tracing
on the sender, the tracepoint is before the NIC has computed the full checksum.
IIRC only a partial checksum is passed-down to the NIC when CKO is in use.
So, making certain your trace is from the "wire" or the receiver rather than the
sender would be a good thing, and trying again with CKO disabled on the
interface(s) (via ethtool) might be something worth looking at. Ultimately,
doing the partial checksum modificiations in a CKO-friendly manner might be a
good thing.
rick jones
prev parent reply other threads:[~2007-10-26 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 7:41 Bad TCP checksum error Gaurav Aggarwal
2007-10-26 16:03 ` Gaurav Aggarwal
2007-10-26 16:59 ` Rick Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47221CE4.70103@hp.com \
--to=rick.jones2@hp.com \
--cc=davidsen@tmr.com \
--cc=grv.aggarwal@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.