All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix NAT for domU checksum offload
Date: Fri, 14 Oct 2005 18:16:10 -0500	[thread overview]
Message-ID: <20051014231610.GD11252@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E3C9@liverpoolst.ad.cl.cam.ac.uk>

On Sat, Oct 15, 2005 at 12:09:36AM +0100, Ian Pratt wrote:
> > Below is a fix for the current problem of checksum offload 
> > not working in a NAT'ed network.  The cause is the 
> > NAT/iptables code incorrectly modifying the TCP/UDP checksum 
> > (for the checksum offload case).  The original code assumes a 
> > valid checksum, which is not the case for checksum offload 
> > packets (which has a complimented, partial checksum for the 
> > hardware to use).  The fix is to compliment the new address 
> > and not compliment the old address (which is complimented in 
> > the partial checksum), and roll that with the 
> > ip_nat_cheat_check function.
> 
> Thanks for looking into this -- this issue has been nagging away for a
> long time.

Sorry it took me so long.  Hopefully, I can knock out the IPSec one
faster.

> > There are two "versions" of the patch below.  The first 
> > version is a diff to show the actual changes made to the 
> > ip_nat_proto_udp.c and ip_nat_proto_tcp.c file (as it is 
> > difficult/impossible to tell from the second patch).  The 
> > second version is the one to commit to the tree (which 
> > creates 2 new files in the sparse directory).
> 
> Would we be better off committing the first patch to the patches
> directory rather than adding to the sparse tree.

You are right.  Patch to follow.

> Do you think you could send this upstream via davem?

I can send this to DaveM, but it is very Xen specific.  Should we wait
for the big Xen/Linux merge for this, or is he currently going through
the changes?

> [Today has been a good day for vanquishing bugs. We're working on a few
> save/restore fixes and have a list of tools issues, but 32bit isn't in
> too bad shape right now.]
> 
> Ian
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

  reply	other threads:[~2005-10-14 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 23:09 [PATCH] Fix NAT for domU checksum offload Ian Pratt
2005-10-14 23:16 ` Jon Mason [this message]
2005-10-14 23:49 ` Jon Mason
2005-10-15  7:24   ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-10-15  9:31 Ian Pratt
2005-10-14 22:32 Jon Mason

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=20051014231610.GD11252@us.ibm.com \
    --to=jdmason@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.