All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Christophe Saout <christophe@saout.de>
Cc: netfilter-devel@lists.netfilter.org,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: 2.6.16-rc1-mm3 XFRM+NAT issue
Date: Sun, 29 Jan 2006 23:14:21 +0100	[thread overview]
Message-ID: <43DD3E3D.5070201@trash.net> (raw)
In-Reply-To: <1138568354.21229.1.camel@leto.intern.saout.de>

Christophe Saout wrote:
> Patrick McHardy wrote:
>
>>It should work just fine. Please add logging rules for both encrypted
>>and decrypted packets to all chains in the mangle table and enable
>>logging of invalid packets in connection tracking
>>(echo 255 > /proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid)
>>and post the results.
> 
> 
> I did, but it doesn't seem conclusive.
> 
> Trying to open a tcp connection: (note that there are no entries with
> IN=eth0 ???)
> 
> Jan 29 21:51:23 server IN= OUT=ppp0 SRC=<gateway pub ip> DST=<inet host> LEN=100 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=41 
> Jan 29 21:51:23 server IN= OUT=ppp0 SRC=<gateway pub ip> DST=<inet host> LEN=100 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=41 

41 is IPPROTO_IPV6, you seem to be talking to the remote side using IPv6
over sit, which is why NAT on the TCP packet doesn't work.

  reply	other threads:[~2006-01-29 22:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 19:41 2.6.16-rc1-mm3 XFRM+NAT issue Christophe Saout
2006-01-29 19:57 ` Patrick McHardy
2006-01-29 20:59   ` Christophe Saout
2006-01-29 22:14     ` Patrick McHardy [this message]
2006-01-29 22:30       ` Christophe Saout
2006-01-29 22:43         ` Patrick McHardy
2006-01-29 23:11           ` Christophe Saout
2006-01-29 22:59         ` Patrick McHardy
2006-01-29 23:24           ` Christophe Saout
2006-01-29 23:26             ` Patrick McHardy
2006-01-29 23:29               ` Patrick McHardy
2006-01-29 23:30               ` Christophe Saout
2006-02-03  1:16           ` David S. Miller
2006-02-03 10:24             ` Patrick McHardy

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=43DD3E3D.5070201@trash.net \
    --to=kaber@trash.net \
    --cc=christophe@saout.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=netfilter-devel@lists.netfilter.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.