public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail•com>
To: Paul Donohue <linux-kernel@PaulSD•com>
Cc: "David S. Miller" <davem@davemloft•net>,
	Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
	netdev@vger•kernel.org
Subject: Re: IPv6 L2TP issues related to 93531c67
Date: Tue, 16 Jul 2019 10:46:34 -0600	[thread overview]
Message-ID: <18b3d951-e1c2-d740-89cf-ee5f7f0ee504@gmail.com> (raw)
In-Reply-To: <20190716135646.GE2622@TopQuark.net>

On 7/16/19 7:56 AM, Paul Donohue wrote:
> After establishing an IPsec tunnel to carry the L2TP traffic, the first L2TP packet through the IPsec tunnel permanently breaks the associated L2TP tunnel.  Tearing down the IPsec tunnel does not restore functionality of the L2TP tunnel - I have to tear down and re-create the L2TP tunnel before it will work again.  In my real-world use case, I have two L2TP tunnels running over the same IPsec tunnel, and the first L2TP tunnel to send a packet after IPsec is established gets permanently broken, while the other L2TP tunnel works fine.
> 
> I've attached a modified version of the script which demonstrates this issue.

Thanks. I will take a look at get back to you.

  reply	other threads:[~2019-07-16 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 16:18 IPv6 L2TP issues related to 93531c67 Paul Donohue
2019-07-15 18:55 ` David Ahern
2019-07-16 13:56   ` Paul Donohue
2019-07-16 16:46     ` David Ahern [this message]
2019-07-17 11:11     ` David Ahern
2019-07-17 15:37       ` Paul Donohue

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=18b3d951-e1c2-d740-89cf-ee5f7f0ee504@gmail.com \
    --to=dsahern@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=kuznet@ms2$(echo .)inr.ac.ru \
    --cc=linux-kernel@PaulSD$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=yoshfuji@linux-ipv6$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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