On Wednesday, August 09, 2017 16:26:50 Hiroki Sato wrote:> The configuration looks correct to me, but two questions: > > 1. Does "sysctl net.inet6.ip6.forwarding" command show "0"? >$ sysctl net.inet6.ip6.forwarding net.inet6.ip6.forwarding: 0> 2. What is shown by the command "ping6 ff02::1%lagg0" and "rtsol -dD lagg0"? >$ ping6 -c 2 ff02::1%lagg0 PING6(56=40+8+8 bytes) fe80::ae16:2dff:fe1e:b880%lagg0 --> ff02::1%lagg0 16 bytes from fe80::ae16:2dff:fe1e:b880%lagg0, icmp_seq=0 hlim=64 time=0.181 ms 16 bytes from fe80::f415:63ff:fe2b:ea06%lagg0, icmp_seq=0 hlim=64 time=0.263 ms(DUP!) 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=0.318 ms(DUP!) 16 bytes from fe80::8edc:d4ff:feaf:8938%lagg0, icmp_seq=0 hlim=64 time=0.369 ms(DUP!) 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=0.803 ms(DUP!) 16 bytes from fe80::ae16:2dff:fe1e:e998%lagg0, icmp_seq=0 hlim=64 time=0.868 ms(DUP!) 16 bytes from fe80::ae16:2dff:fe1e:49f8%lagg0, icmp_seq=0 hlim=64 time=0.922 ms(DUP!) 16 bytes from fe80::226:55ff:fe2f:40a4%lagg0, icmp_seq=0 hlim=64 time=0.971 ms(DUP!) 16 bytes from fe80::f415:63ff:fe2b:ea06%lagg0, icmp_seq=0 hlim=64 time=2.144 ms(DUP!) 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=4.154 ms(DUP!) 16 bytes from fe80::f415:63ff:fe2b:e806%lagg0, icmp_seq=0 hlim=64 time=4.220 ms(DUP!) 16 bytes from fe80::ae16:2dff:fe1e:b880%lagg0, icmp_seq=1 hlim=64 time=0.222 ms --- ff02::1%lagg0 ping6 statistics --- 2 packets transmitted, 2 packets received, +10 duplicates, 0.0% packet loss round-trip min/avg/max/std-dev = 0.181/1.286/4.220/1.396 ms $ fg su - # rtsol -dD lagg0 checking if lagg0 is ready... lagg0 is ready set timer for lagg0 to 1s New timer is 1s timer expiration on lagg0, state = 1 send RS on lagg0, whose state is 2 set timer for lagg0 to 4s New timer is 4s timer expiration on lagg0, state = 2 send RS on lagg0, whose state is 2 set timer for lagg0 to 4s New timer is 4s timer expiration on lagg0, state = 2 send RS on lagg0, whose state is 2 set timer for lagg0 to 1s New timer is 1s timer expiration on lagg0, state = 2 No answer after sending 3 RSs stop timer for lagg0 there is no timer -- Greg Rivers
Greg Rivers <gcr+freebsd-stable at tharned.org> wrote in <2045487.FzlpjXtTmv at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170809/a15ad956/attachment.sig>