On Wed, Jul 17, 2019 at 05:11:21AM -0600, David Ahern wrote:
> This fixes the test script (whitespace damaged but simple enough to
> manually patch). See if it fixes the problem with your more complex
> setup. If so I will send a formal patch.
Yes! I applied this on top of f632a8170a6b667ee4e3f552
On 7/16/19 7:56 AM, Paul Donohue wrote:
>
> Unfortunately, I have a fairly complicated setup, so it took me a while to
> figure out which pieces were relevant ... But I think I've finally got it.
> The missing piece was IPsec.
>
> After establishing an IPsec tunnel to carry the L2TP traffic, t
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
On Mon, Jul 15, 2019 at 12:55:48PM -0600, David Ahern wrote:
> As an FYI, gmail thinks your emails are spam.
Ugh. Thanks for letting me know. I'll look into it.
> On 7/15/19 10:18 AM, Paul Donohue wrote:
> > Reverting commit 93531c6743157d7e8c5792f8ed1a57641149d62c (identified by
> > bisection)
Hi Paul:
As an FYI, gmail thinks your emails are spam.
On 7/15/19 10:18 AM, Paul Donohue wrote:
> I have a system that establishes four L2TP over IPv6 tunnels using site-local
> addresses via the following:
...
>
> These tunnels worked fine on kernel 4.4. On kernel 4.15, there was a bug
> th
I have a system that establishes four L2TP over IPv6 tunnels using site-local
addresses via the following:
ip l2tp add tunnel tunnel_id 1233 peer_tunnel_id 1233 encap ip local
fd23:2355:accd::2:4 remote fd23:2355:accd::2:3
ip l2tp add session name net_l2tp1 tunnel_id 1233 session_id 1233
peer_se
