Date: Wed, 09 Aug 2017 17:41:47 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: gcr+freebsd-stable@tharned.org Cc: freebsd-stable@freebsd.org Subject: Re: SLAAC not working Message-ID: <20170809.174147.590175436870311346.hrs@allbsd.org> In-Reply-To: <2045487.FzlpjXtTmv@flake.tharned.org> References: <1557648.beBEYmqKBO@flake.tharned.org> <20170809.162650.970303478864091097.hrs@allbsd.org> <2045487.FzlpjXtTmv@flake.tharned.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Wed_Aug__9_17_41_47_2017_273)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Greg Rivers <gcr+freebsd-stable@tharned.org> wrote in <2045487.FzlpjXtTmv@flake.tharned.org>: gc> > 2. What is shown by the command "ping6 ff02::1%lagg0" and "rtsol -dD lagg0"? gc> > gc> $ ping6 -c 2 ff02::1%lagg0 gc> PING6(56=40+8+8 bytes) fe80::ae16:2dff:fe1e:b880%lagg0 --> ff02::1%lagg0 gc> 16 bytes from fe80::ae16:2dff:fe1e:b880%lagg0, icmp_seq=0 hlim=64 time=0.181 ms gc> 16 bytes from fe80::f415:63ff:fe2b:ea06%lagg0, icmp_seq=0 hlim=64 time=0.263 ms(DUP!) gc> 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=0.318 ms(DUP!) gc> 16 bytes from fe80::8edc:d4ff:feaf:8938%lagg0, icmp_seq=0 hlim=64 time=0.369 ms(DUP!) gc> 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=0.803 ms(DUP!) gc> 16 bytes from fe80::ae16:2dff:fe1e:e998%lagg0, icmp_seq=0 hlim=64 time=0.868 ms(DUP!) gc> 16 bytes from fe80::ae16:2dff:fe1e:49f8%lagg0, icmp_seq=0 hlim=64 time=0.922 ms(DUP!) gc> 16 bytes from fe80::226:55ff:fe2f:40a4%lagg0, icmp_seq=0 hlim=64 time=0.971 ms(DUP!) gc> 16 bytes from fe80::f415:63ff:fe2b:ea06%lagg0, icmp_seq=0 hlim=64 time=2.144 ms(DUP!) gc> 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=4.154 ms(DUP!) gc> 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=4.220 ms(DUP!) gc> 16 bytes from fe80::ae16:2dff:fe1e:b880%lagg0, icmp_seq=1 hlim=64 time=0.222 ms You should have got responses from 64:a0:e7:45:63:43 (router), namely fe80::66a0:e7ff:fe45:6343%lagg0, but it seems it did not happen for some reason. Was the router receiving the ICMPv6 ECHOes which came from fe80::ae16:2dff:fe1e:b880? gc> > 2. What is shown by the command "ping6 ff02::1%lagg0" and "rtsol -dD lagg0"? (snip) gc> # rtsol -dD lagg0 gc> checking if lagg0 is ready... gc> lagg0 is ready gc> set timer for lagg0 to 1s gc> New timer is 1s gc> timer expiration on lagg0, state = 1 gc> send RS on lagg0, whose state is 2 gc> set timer for lagg0 to 4s gc> New timer is 4s gc> timer expiration on lagg0, state = 2 gc> send RS on lagg0, whose state is 2 gc> set timer for lagg0 to 4s gc> New timer is 4s gc> timer expiration on lagg0, state = 2 gc> send RS on lagg0, whose state is 2 gc> set timer for lagg0 to 1s gc> New timer is 1s gc> timer expiration on lagg0, state = 2 gc> No answer after sending 3 RSs gc> stop timer for lagg0 gc> there is no timer This indicates that there was no RA as an answer from the router after a RS message was sent. Probably there is a problem with the link between lagg0 and the router, not specific to IPv6. -- Hiroki ----Security_Multipart(Wed_Aug__9_17_41_47_2017_273)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlmKyssACgkQTyzT2CeTzy0V9wCgtO27iflAnvqJTHzpDnogMXpq gz0AoN6Zl0M0xwthBf9UXpvDpWUVLZwS =SZT/ -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Aug__9_17_41_47_2017_273)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170809.174147.590175436870311346.hrs>