2020-05-25T20:46:37 dpinger: WAN_DHCP6 fe80::201:5cff:fe76:b846%hn0: sendto error: 65
# /sbin/ping6 -S 'fe80::21f:e1ff:fe10:e676%hn0' -c '3' 'fe80::201:5cff:fe76:b846'PING6(56=40+8+8 bytes) fe80::21f:e1ff:fe10:e676%hn0 --> fe80::201:5cff:fe76:b846%hn0ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1--- fe80::201:5cff:fe76:b846 ping6 statistics ---3 packets transmitted, 0 packets received, 100.0% packet lossping6: sendmsg: No route to hostping6: sendmsg: No route to hostping6: sendmsg: No route to host
What's your ISP?Can you check in your /tmp/ folder. and look for a *_routerv6 file, does it exist?p.s following your thread on the pfSense forum - multiple-ipv6-capable-connections, interesting.
Also, can you post the output of netstat -6rW. Obfuscate any gua addresses, just interested in the default route.
root@OPNsense:~ # netstat -6rWRouting tablesInternet6:Destination Gateway Flags Use Mtu Netif Expiredefault fe80::201:5cff:fe76:b846%hn0 UG 111414 1500 hn0localhost link#1 UH 0 16384 lo064:ff9b::/96 fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGS 35 1500 hn464:ff9b::424a:d401 fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGHS 42464 1500 hn4dns.google fe80::201:5cff:fe76:b846%hn0 UGHS 42480 1500 hn02605:e000:abcd:ef10::/64 link#6 U 27147 1500 hn12605:e000:abcd:ef10:15:5dff:feff:2b00 link#6 UHS 0 16384 lo02605:e000:abcd:ef20::/64 link#7 U 0 1500 hn2OPNsense link#7 UHS 0 16384 lo02605:e000:abcd:ef30::/64 link#8 U 6858 1500 hn32605:e000:abcd:ef30:15:5dff:feff:2b02 link#8 UHS 0 16384 lo02605:e000:abcd:ef64::/64 link#9 U 0 1500 hn42605:e000:abcd:ef64:15:5dff:feff:2b03 link#9 UHS 0 16384 lo0OPNsense link#5 UHS 0 16384 lo0fd04:6ddc:fe8e:2310::/64 link#6 U 0 1500 hn1OPNsense link#6 UHS 0 16384 lo0fd04:6ddc:fe8e:2330::/64 link#8 U 2851 1500 hn3OPNsense link#8 UHS 0 16384 lo0fd04:6ddc:fe8e:2364::/64 link#9 U 44377 1500 hn4OPNsense link#9 UHS 0 16384 lo0fe80::%lo0/64 link#1 U 0 16384 lo0fe80::1%lo0 link#1 UHS 0 16384 lo0fe80::%hn0/64 link#5 U 25 1500 hn0fe80::21f:e1ff:fe10:e676%hn0 link#5 UHS 0 16384 lo0fe80::%hn1/64 link#6 U 1614 1500 hn1fe80::15:5dff:feff:2b00%hn1 link#6 UHS 0 16384 lo0fe80::%hn2/64 link#7 U 0 1500 hn2fe80::15:5dff:feff:2b01%hn2 link#7 UHS 0 16384 lo0fe80::%hn3/64 link#8 U 4126 1500 hn3fe80::15:5dff:feff:2b02%hn3 link#8 UHS 0 16384 lo0fe80::%hn4/64 link#9 U 3482 1500 hn4fe80::15:5dff:feff:2b03%hn4 link#9 UHS 0 16384 lo0root@OPNsense:~ #
I have the same problem with the ipv6 link-local address. I changed it to one of the google dns ipv6 addresses and it has worked since, modulo other problems with dpinger.
Can you do:# ps auxw | grep dpingerpost the v6 entry... ta..
root 50166 0.0 0.1 11008 2468 - Is 10:40 0:00.01 /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP6 -B fe80::21f:e1ff:fe10:e676%hn0 -p /var/run/dpinger_WAN_DHCP6.pid -u /var/run/dpinger_WAN_DHCP6.sock -C /usr/local/etc/rc.syshook monitor -s 1s -l 2s -t 60s -A 1s -D 500 -L 20 -d 0 fe80::201:5cff:fe76:b846%hn0
Sorry.. read the last message from you just after I posted. Can you post the none working and the working ps -auxw ....
root@OPNsense:~ # ps auxw | grep dpingerroot 369 0.0 0.1 6912 2356 - Is 10:37 0:00.02 /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP6 -B 2605:e000:ffc0:3a:3583:9dcc:d43b:b16e -p /var/run/dpinger_WAN_DHCP6.pid -u /var/run/dpinger_WAN_DHCP6.sock -C /usr/local/etc/rc.syshook monitor -s 1s -l 2s -t 60s -A 1s -D 500 -L 20 -d 0 2001:4860:4860::8844