From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yves-Alexis Perez <corsac@debian.org>
Subject: Re: Regression for ip6-in-ip4 IPsec tunnel in 4.14.16
Date: Thu, 08 Feb 2018 13:40:24 +0100
Message-ID: <1518093624.2997.10.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>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256";
        protocol="application/pgp-signature"; boundary="=-1M+ItS7DYMfiUOkz2pVV"
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>
To: Mike Maloney <maloneykernel@gmail.com>
Return-path: <stable-owner@vger.kernel.org>
In-Reply-To: <1518032786.4024.1.camel@debian.org>
Sender: stable-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org


--=-1M+ItS7DYMfiUOkz2pVV
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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)
>=20
> f=C3=A9vr. 07 20:44:01 scapa kernel: mtu: 1266
>=20
> 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 O=
K.

Unfortunately I have the feeling that debugging this will be a bit tricky f=
or
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,
--=20
Yves-Alexis
--=-1M+ItS7DYMfiUOkz2pVV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlp8RTgACgkQ3rYcyPpX
RFti+wgA4Fcde2WJ7DWd4poQv9UdVn2ecwdr5s8klsNVdXAypInq1gTqublhulT6
2sV365q1LDYbTyTbHJn0brxVPNRX50xsUiRXkfrc3hB6lN8ZPya0ZUwq7ICP5Ot4
HZvaId0ZyHhOgFSO4oap3VSHXEL2S0F0xq/nanTXwfj+tMCCCf1T+BKEdOyuBLF7
OugVaRSzPWBe2jl+dQPT1u+8EhE6o1CY7wIl4Do9ybI7aXWfaC5SGYpoM6e4wd7W
nrUDA5cgRJLH8Tnl8uTGeeXDcDtiTVLXZEd+B+so0TwvqDRHgPSNPirsSlUcMtkN
tDB+A1oWnzzrb85JwWhL2HMbJri6gQ==
=CI3S
-----END PGP SIGNATURE-----

--=-1M+ItS7DYMfiUOkz2pVV--