netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Gnome42 Gnome42 <gnome42@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: IPSec broken in 2.6.18-rc4-mm3
Date: Fri, 08 Sep 2006 21:52:33 +0200	[thread overview]
Message-ID: <4501CA01.3050904@trash.net> (raw)
In-Reply-To: <fa4052ef0609080926j5bbae070mccb9699f0e5eb1fb@mail.gmail.com>

Gnome42 Gnome42 wrote:
> IPSec got broken in 2.6.18-rc4-mm3+, 2.6.18-rc4-mm2 works and
> 2.6.18-rc5 also works.
> 
> The tunnel looks like its established correctly in the racoon logs and
> the traffic is encrypted on the wire. However, the other side does not
> decrypt the traffic it just seems to disappear.

Can you see the decrypted packets on the incoming interface on the
other side?

> I have confirmed this problem exists between two linux boxen and a
> Netopia router as well.
> 
> The git-net.patch increased in size by about 50% between
> 2.6.18-rc4-mm2 and 2.6.18-rc4-mm3 (likely suspect?), but i was unable
> to simply patch -R it cleanly.
> 
> Suggestions?

Please post your policies and related SAs from both sides.
Are you using NAT, iptables or anything like that?


  reply	other threads:[~2006-09-08 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 16:26 IPSec broken in 2.6.18-rc4-mm3 Gnome42 Gnome42
2006-09-08 19:52 ` Patrick McHardy [this message]
2006-09-08 20:32   ` Gnome42 Gnome42
2006-09-09 13:56     ` Patrick McHardy
2006-09-09 14:35       ` Gnome42
2006-09-09 16:22         ` Patrick McHardy
2006-09-09 17:39           ` Gnome42
2006-09-10  1:09             ` Gnome42
2006-09-10  1:12               ` 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=4501CA01.3050904@trash.net \
    --to=kaber@trash.net \
    --cc=gnome42@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).