All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Pick <jim@jimpick.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Masquerading problems - XenU 3.0 on x86_64
Date: Sat, 08 Apr 2006 17:01:30 -0700	[thread overview]
Message-ID: <44384EDA.2080106@jimpick.com> (raw)

Hi,

I'm trying to migrate my Xen sessions installed on 32-bit Xen 2.0 server 
to a 64-bit Xen 3.0 server.

On the Xen 2.0 server (32-bit), I built a DomU kernel with masquerading, 
and I use that to do NAT for some private networks running on the same 
box.

When I tried to do it with Xen 3.0 (64-bit), I couldn't get it to work. 
  I had to build a custom DomU kernel (from xen-3.0-testing.hg, 2.6.16, 
2 days ago) in order to include the netfilter/iptables code.  ICMP 
works.  TCP doesn't.  Non-masquerading traffic is OK.  I had the same 
problems with the 2.6.12 kernel from Xen 3.0.1.

I captured some of the traffic, and ethereal is showing that the 
masqueraded traffic being output has bad TCP checksums.

I'm going to have to do some debugging to try to figure out what's going 
wrong.

Has anybody else encountered this?  Also, if it's already been fixed 
somewhere, I'd love to know.  Any Netfilter debugging tips would also be 
appreciated.

Cheers,

  - Jim

             reply	other threads:[~2006-04-09  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09  0:01 Jim Pick [this message]
2006-04-09  7:46 ` Masquerading problems - XenU 3.0 on x86_64 Keir Fraser
2006-04-09 20:18   ` Jim Pick
2006-04-10  8:22     ` Keir Fraser
2006-04-10 19:43       ` Jim Pick

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=44384EDA.2080106@jimpick.com \
    --to=jim@jimpick.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --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.