From mboxrd@z Thu Jan  1 00:00:00 1970
From: valdis.kletnieks@vt.edu
Subject: 4.14.(44->48) IPv6 RA issue?
Date: Mon, 18 Jun 2018 11:02:46 -0400
Message-ID: <35958.1529334166@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1529334166_20151P";
         micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org
To: netdev@vger.kernel.org
Return-path: <linux-kernel-owner@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

--==_Exmh_1529334166_20151P
Content-Type: text/plain; charset=us-ascii

So I'm trying to troubleshoot an issue on an OpenWRT/Lede based
router, where IPv6 connectivity totally fails. I've bisected it down to:

git log --oneline 187da94808a634477b5e5a69109ea0c566dfa64b..73d8a6ab7668173d70adbed45b61be5256c505e
73d8a6ab7668 (refs/bisect/bad) base-files: fix UCI config parsing and callback handling
e52f3e9b1376 kernel: bump 4.14 to 4.14.48
7590c3c58f5e (HEAD) scripts: Replace obsolete POSIX tmpnam in slugimage.pl with File::Temp function
987900f2de76 hostapd: properly build hostapd-only SSL variants

and am pretty sure that it's the kernel bump (works with a 4.14.44 kernel,
breaks with 4.14.48) as the other 3 commits don't go anywhere near IPv6 handling.

Symptoms:
With a good kernel, 'ip -6 neigh' reports:

ip -6 neigh
2601:5c0:c001:4341:2116:22ff:b17b:7cd6 dev wlan1 lladdr bc:85:56:1f:4f:6d REACHABLE
fe80::201:5cff:fe6f:1a46 dev eth1 lladdr 00:01:5c:6f:1a:46 router REACHABLE
fe80::9325:3b21:5021:fbd8 dev eth0 lladdr b8:27:eb:f7:0b:20 REACHABLE
fe80::2d9:d1ff:fed9:51a3 dev eth0 lladdr 00:d9:d1:d9:51:a3 REACHABLE

With a bad one, I get:

ip -6 neigh
fe80::be85:56ff:fe1f:4f6d dev wlan1 lladdr bc:85:56:1f:4f:6d STALE
fe80::2d9:d1ff:fed9:51a3 dev eth0 lladdr 00:d9:d1:d9:51:a3 STALE
fe80::9325:3b21:5021:fbd8 dev eth0 lladdr b8:27:eb:f7:0b:20 DELAY
2601:5c0:c001:4341:2116:22ff:b17b:7cd6 dev wlan1 lladdr bc:85:56:1f:4f:6d REACHABLE
fe80::201:5cff:fe6f:1a46 dev eth1  INCOMPLETE

Note that eth1 is the uplink towards my ISP.  I've pointed a 'tcpdump -n -i eth1 ip6'
at it, and see plenty of RA packets come in, but neighbor discovery never completes.
Looking at the Changelogs for .45->.50 don't show any smoking-gun patches.

This ring any bells, before I delve deeper into it?

--==_Exmh_1529334166_20151P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.8.0 04/21/2017

iQEVAwUBWyfJlo0DS38y7CIcAQJqRAf+Iy4OXUxuBVdMttqWqg8n4FMRa7fxLASq
LYTDD/3tgv8K25J5JquZxQxbAymUGaka1y2GAgLGKaujllOU/Hu4rVFJ+b0DW443
tYC4D56XR7kE45tGG1qnqg9GaTxie2XrXdi5rFGaGXgkoKHTzOUN7FC4aoki1TIa
1vbee9iCatuuQQe1mjwRaZIytptek7pXbj5cBhAgzGLLqDkBfrzJC0EBLtUs8l/k
zKslRjFhIG3wVpDvk8gYxE+jpNkUdoDijrnflkFkmc5cs8ol74aLaNvCZfIhcoUm
Ik/BU7rOdy04XaGaX7QAf/aUhS5hFWJYuHrDxAu2cq5Ap6kfw7Taiw==
=fa0F
-----END PGP SIGNATURE-----

--==_Exmh_1529334166_20151P--