[Openswan Users] Any known problems with NAT Traversal with Linux 2.4.26/2.6.7?

[Herbert Xu]

On Wed, Jul 21, 2004 at 02:31:24PM +0100, Toby Corkindale wrote:
> 
> How immediate is "immediately"?
> A couple of minutes later, I still see this present:
> udp      17 161 src=193.30.123.243 dst=123.158.235.14 sport=4500 dport=4500 src=123.158.235.14 dst=193.30.123.243 sport=4500 dport=4500 [ASSURED] use=1
> 
> (That was after grepping for the remote IP (193.30.123.243)- I have removed
> the rest, which I believe are unrelated lines, as the server is quite busy and
> ip_conntrack is quite long)

What if you grep for 192.168?
 
> If it's useful to know:
> This server is running kernel 2.4.26 w/OpenSwan KLIPS 2.1.4, and includes the
> NAT-T kernel patch.

Since you don't have any NAT rules, this looks like a kernel bug.
Would it be possible to try running 2.6 or 2.4.26+26sec on the server?
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert at gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt