From: Patrick McHardy <kaber@trash.net>
To: lists@naasa.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.10 with IPSEC problems?
Date: Sun, 26 Dec 2004 16:39:23 +0100 [thread overview]
Message-ID: <41CEDB2B.7080309@trash.net> (raw)
In-Reply-To: <200412261553.24178.lists@naasa.net>
Joerg Platte wrote:
> Hi!
>
> After an upgrade from 2.6.9 to 2.6.10 my IPSEC tunnel does not work as usual.
> My computer and the VPN-gateway can negotiate and build a tunnel and packets
> can use the tunnel. But then packets which must be routed get lost somewhere
> inside the kernel. tcpdump shows them first encrypted in ESP packets and then
> the unencrypted payload on the same interface. But they do not leave the
> kernel on the destination interface. Only packets with my computer as
> destination are processed. I did not change my IPSEC configuration and the
> kernel was configured using "make oldconfig".
>
> Is there a problem in the routing layer somewhere inside the kernel or an
> internal change which requires a configuration change on my side? How can I
> determine, where and why the packets inside the kernel are thrown away?
>
> To verify the problem I build a 2.6.10 kernel on the VPN gateway. And this
> kernel seems to have the same problem. Previously encrypted packets are not
> routed to th destination.
>
> Downgrading to 2.6.9 solved the problem in both cases...
Since Linux 2.6.10-rcX. packets from a tunnel-mode SA are dropped if
no policy exists. You most likely only have an input policy, but no
forward policy. If you use setkey to configure your policies,
duplicate the input policy and replace "-P in" with "-P fwd". If you
let racoon generate the policy you need to upgrade to the latest
version. pluto should already get it right.
Regards
Patrick
>
> Regards,
> Jörg
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-12-26 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 14:53 Kernel 2.6.10 with IPSEC problems? Joerg Platte
2004-12-26 15:39 ` Patrick McHardy [this message]
2004-12-26 18:15 ` Joerg Platte
2004-12-26 18:42 ` 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=41CEDB2B.7080309@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@naasa.net \
/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