From owner-freebsd-stable@freebsd.org Tue Sep 5 17:13:05 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D39E4E13510 for ; Tue, 5 Sep 2017 17:13:05 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76AD375131 for ; Tue, 5 Sep 2017 17:13:05 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback8o.mail.yandex.net (mxback8o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::22]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 565395D8157E; Tue, 5 Sep 2017 20:12:51 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback8o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 8JW3msPGXq-CoPKO4md; Tue, 05 Sep 2017 20:12:51 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504631571; bh=Y4npVe08gyJa28qIfceDCBkrTI5xjJV++a/DAC+acDA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Noo9G7V2dh457UROW7k4iBr7cl9hmqM6+YAIy71+q4OamdcR/ZIof/1VRBioGefTf BJKJNJZk+ZnWrdFBtM3mPqorkY4RHf4c+mLvno499sfw3y7adfafofmnjaQ5iTarlm DWun+JdPyA/4z/eL3BfqL1Umc4KhNH+e9gZSBHhQ= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id xgb3kuiElG-CnEKDL0Z; Tue, 05 Sep 2017 20:12:49 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504631570; bh=Y4npVe08gyJa28qIfceDCBkrTI5xjJV++a/DAC+acDA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=hP0HIVnnpO45Gyd5xQHw+ZpEnWRysXJNCi6/wLrnt6deT3+E1ki62MPO1wNVkyEg1 0OxCmppJZS1+HlCjwPTWUM/+nf8Z/u+n0xBt7u7+Sggqh4Sv5lHhxPwAoF1EQkpdYM n2kb6F1jTM3abkgPMNNBy9LSUFvXDMez4XTV6D7I= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: SLAAC not working To: Greg Rivers , freebsd-stable@freebsd.org References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Date: Tue, 5 Sep 2017 20:09:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1762879.zBQMMkUt4K@flake.tharned.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 17:13:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx Content-Type: multipart/mixed; boundary="Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI"; protected-headers="v1" From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org Message-ID: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Subject: Re: SLAAC not working References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> In-Reply-To: <1762879.zBQMMkUt4K@flake.tharned.org> --Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.09.2017 18:25, Greg Rivers wrote: > dtrace saw nothing, yet tcpdump recorded what one would expect. Apparen= tly the inbound RAs and NSs are not making it through to the IPv6 stack. = At this point I suspect a bug in the Emulex oce(4) driver, or a bad inter= action between oce(4) and lagg(4). I have not seen this issue on hosts wi= th lagg and other NICs. As soon as I can, I'm going to eliminate lagg and= repeat the experiment while running on just one oce interface. I'll repo= rt back with results. >=20 >>> $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 >>> ping6: UDP connect: Network is unreachable >> >> Hmm. Can you show the second word of address in this example? >> Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? >> > Correct, neither of the XXXX parts are zero; the :: part is at the end = of the address: ...::2%lagg0. Sorry for the obfuscation, but policy at $W= ORK about company information on public lists is very strict. I think the problem is not with oce(4) driver. Unfortunately, your router uses IPv6 LLA that is not compatible with KAME based IPv6 stack that is used by all BSDs. The FreeBSD kernel internally uses special form of IPv6 addresses, that have IPv6 scope zone id embedded into second word of address. This problem was recently discussed here: https://mailarchive.ietf.org/arch/msg/ipv6/fuzpfBXJHeBfsEddMBtgIpGjKvk Some time ago I have patched the kernel to avoid use of this hack, but this was done for 9.3 kernel and currently I have no time to port patches to recent CURRENT. --=20 WBR, Andrey V. Elsukov --Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI-- --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmu2j8ACgkQAcXqBBDI oXqVxgf8CCzVpEVFMOQ4zpMh7sCP2AUc70ojW884+/Oq2tbB5NTOMtY19QtUc28K TX3spruzZKWa31xERAx0t2ZbTEfR3uNyCtH7uDqim8fPMV2rzcuhlQ9YdpyWFIWB 6+vnHwlQMoYv5wBK/lmlEfhb9RNxoEhO+YO9pfE8RDQR2sMH4mFYDYU/oveNdX04 UD55AQx9W/CS6Fn3b8AnoO2egr6KcubKd87yUaYvbI4EEuImBkTpRGLLHFLHfiCe 022UPoHoJVVhhuc1WyNjDUPd64Y4XqDynkbdgxur7Yf0pe6KJXox7f4Xw9bgXKYZ VGjF695hp0+QIMMGBBwhDYIdwNPrJQ== =xqv2 -----END PGP SIGNATURE----- --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx--