From: Steffen Klassert <steffen.klassert@secunet.com>
To: Kevin Locke <kevin@kevinlocke.name>, <netdev@vger.kernel.org>
Subject: Re: Bisected 4.14 Regression: IPsec transport mode breakage
Date: Fri, 17 Nov 2017 11:03:46 +0100 [thread overview]
Message-ID: <20171117100346.32zc6mv7bc2faamx@gauss3.secunet.de> (raw)
In-Reply-To: <20171115164619.jm45l5n3pbuabu5q@kevinolos>
On Wed, Nov 15, 2017 at 09:46:19AM -0700, Kevin Locke wrote:
> Hi all,
>
> I am using an L2TP/IPsec (transport mode) VPN connection from a client
> behind a NAT running Debian with strongswan 5.6.0-2 and xl2tpd
> 1.3.10-1 to a Cisco Meraki MX60 with a public IP. The connection
> works with kernel 4.13 but not with kernel 4.14. With 4.14 the IPsec
> connection appears to be established correctly but xl2tpd is unable to
> establish the L2TP connection. The relevant error from syslog is:
>
> charon: 09[KNL] creating acquire job for policy 192.168.21.10/32[udp/l2f] === X.X.X.X/32[udp/l2f] with reqid {1}
> charon: 12[CFG] trap not found, unable to acquire reqid 1
>
> I have bisected the issue to commit c9f3f813d462. I have attached the
> client ipsec.conf as well as the syslog during the connection attempt
> for both c9f3f813d462 (bad) and cf3796675174 (good). Meraki IPs have
> been redacted to protect the innocent.
>
> I'd appreciate any assistance in fixing the issue. Let me know if
> there's anything else I can do to help troubleshoot or test.
The offending commit is already reverted in the 'net' tree
and will be available in mainline soon.
Thanks for the report!
next prev parent reply other threads:[~2017-11-17 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 16:46 Bisected 4.14 Regression: IPsec transport mode breakage Kevin Locke
2017-11-17 10:03 ` Steffen Klassert [this message]
2017-11-17 17:46 ` Kevin Locke
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=20171117100346.32zc6mv7bc2faamx@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=kevin@kevinlocke.name \
--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