Re: Regression for ip6-in-ip4 IPsec tunnel in 4.14.16
- To: Mike Maloney <maloneykernel@gmail.com>
- Cc: Mike Maloney <maloney@google.com>, "David S. Miller" <davem@davemloft.net>, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>, Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>, netdev <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org, debian-kernel@lists.debian.org, Tobias Brunner <tobias@strongswan.org>
- Subject: Re: Regression for ip6-in-ip4 IPsec tunnel in 4.14.16
- From: Yves-Alexis Perez <corsac@debian.org>
- Date: Thu, 08 Feb 2018 13:40:24 +0100
- Message-id: <[🔎] 1518093624.2997.10.camel@debian.org>
- In-reply-to: <[🔎] 1518032786.4024.1.camel@debian.org>
- References: <[🔎] 1518021487.2100.2.camel@debian.org> <[🔎] 1518023139.2100.7.camel@debian.org> <[🔎] 1518024182.2136.3.camel@debian.org> <[🔎] CAJegeYkqg97ZyiJRe9ZZAk_C_KX_NrcmuK9SRrEbLzHMXfdv1Q@mail.gmail.com> <[🔎] 1518032786.4024.1.camel@debian.org>
On Wed, 2018-02-07 at 20:46 +0100, Yves-Alexis Perez wrote:
> Maybe. I tried with removing the MTU setting, and I get (on ping again)
>
> févr. 07 20:44:01 scapa kernel: mtu: 1266
>
> which means I would get -EINVAL on standards kernels, which is not really good
> either.
Actually after rebooting on the Debian 4.14.17 kernel, with the outter MTU
unset (or set to 1360), I don't get the -EINVAL anymore, so maybe it'd be OK.
Unfortunately I have the feeling that debugging this will be a bit tricky for
other people. MTU tuning for tunnels are always a bit confusing, but having
the kernel return EINVAL on a ping doesn't really help narrowing it down to
that MTU setting. Not sure if some kind of logging could be added to help?
Regards,
--
Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part
Reply to: