From: Andrew Morton <akpm@osdl.org>
To: bugme-daemon@bugzilla.kernel.org
Cc: astier.raphael@free.fr, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6430] New: ipsec tunnel : reply is not forwarded
Date: Sun, 23 Apr 2006 12:53:42 -0700 [thread overview]
Message-ID: <20060423125342.71a6e0d5.akpm@osdl.org> (raw)
In-Reply-To: <200604231526.k3NFQ5dO010175@fire-2.osdl.org>
bugme-daemon@bugzilla.kernel.org wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6430
>
> Summary: ipsec tunnel : reply is not forwarded
> Kernel Version: 2.6.14.5
> Status: NEW
> Severity: normal
> Owner: shemminger@osdl.org
> Submitter: astier.raphael@free.fr
>
>
> Most recent kernel where this bug did not occur: 2.6.14
> Distribution: debian sarge 3.1
> Hardware Environment:
> Software Environment: isakmpd
> Problem Description:
> The situation is the following :
> hostA -- GW1 <==> GW2 -- hostB, with an ipsec tunnel between GW1 and GW2.
> Encryption : des-cbc, Auth : hmac-md5, and automatic keyring with isakmpd
> on GW1 and GW2.
> The tunnel is correctly mounted, with symmetrical spi on both sides GW1 and GW2.
> (I have verified with setkey)
> When hostA ping hostB, packets are correctly send to hostB, and returns
> to GW1, and are decrypted here, but are not forwarded to hostA.
> (Symmetrically when hostB ping hostA packet returned on GW2 are not
> forwarded to hostB). I have verified with tcpdump.
> I have try exactly the same configuration with standard kernel 2.6.8 from
> sarge distrib. and it works perfectly.
> I also try to echo 0 > /proc/...eth0/rp_filter where eth0 is the interface on
> GW2 "connected" to GW1 but result is the same.
> I have also try replacing GW2 by a Cisco PIX, and I have same result
> on linux (2.6.14.5) GW1.
>
> Steps to reproduce:
> Configure an ipsec tunnel between GW1 and GW2 as described above. I have done
> it with isakmpd, and with standard support of ipsec in kernel, not with
> freeswan.
>
That's quite an old kernel. Are you able to test 2.6.16?
next parent reply other threads:[~2006-04-23 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604231526.k3NFQ5dO010175@fire-2.osdl.org>
2006-04-23 19:53 ` Andrew Morton [this message]
2006-06-28 8:02 ` [Bugme-new] [Bug 6430] New: ipsec tunnel : reply is not forwarded Raphael Astier
2006-07-13 12:10 ` Herbert Xu
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=20060423125342.71a6e0d5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=astier.raphael@free.fr \
--cc=bugme-daemon@bugzilla.kernel.org \
--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).