Unable to get dpinger to work on WAN ipv6 link local address

Started by IsaacFL, May 26, 2020, 06:10:55 AM

Previous topic - Next topic
New user to opnsense.

My WAN ipv6 gateway is a link local address and dpinger shows the gateway down.

In the Gateway Logs I see:
2020-05-25T20:46:37 dpinger: WAN_DHCP6 fe80::201:5cff:fe76:b846%hn0: sendto error: 65

If I try to ping I get:
# /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%hn0
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: 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 loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host


It seems to me that something is wrong with the route for link local on the WAN interface?

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.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Also, can you post the output of netstat -6rW. Obfuscate any gua addresses, just interested in the default route.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

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.

Quote from: marjohn56 on May 26, 2020, 08:18:01 AM
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.
ISP is Time Warner/Spectrum in Southern California.

The file hn0_routerv6 does exist, its contents are:
fe80::201:5cff:fe76:b846

which is the gateway of the ISP

Quote from: marjohn56 on May 26, 2020, 08:24:47 AM
Also, can you post the output of netstat -6rW. Obfuscate any gua addresses, just interested in the default route.

root@OPNsense:~ # netstat -6rW
Routing tables

Internet6:
Destination        Gateway            Flags       Use    Mtu    Netif Expire
default            fe80::201:5cff:fe76:b846%hn0 UG   111414   1500      hn0
localhost          link#1             UH            0  16384      lo0
64:ff9b::/96       fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGS       35   1500      hn4
64:ff9b::424a:d401 fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGHS    42464   1500      hn4
dns.google         fe80::201:5cff:fe76:b846%hn0 UGHS    42480   1500      hn0
2605:e000:abcd:ef10::/64 link#6       U         27147   1500      hn1
2605:e000:abcd:ef10:15:5dff:feff:2b00 link#6 UHS           0  16384      lo0
2605:e000:abcd:ef20::/64 link#7       U             0   1500      hn2
OPNsense           link#7             UHS           0  16384      lo0
2605:e000:abcd:ef30::/64 link#8       U          6858   1500      hn3
2605:e000:abcd:ef30:15:5dff:feff:2b02 link#8 UHS           0  16384      lo0
2605:e000:abcd:ef64::/64 link#9       U             0   1500      hn4
2605:e000:abcd:ef64:15:5dff:feff:2b03 link#9 UHS           0  16384      lo0
OPNsense           link#5             UHS           0  16384      lo0
fd04:6ddc:fe8e:2310::/64 link#6       U             0   1500      hn1
OPNsense           link#6             UHS           0  16384      lo0
fd04:6ddc:fe8e:2330::/64 link#8       U          2851   1500      hn3
OPNsense           link#8             UHS           0  16384      lo0
fd04:6ddc:fe8e:2364::/64 link#9       U         44377   1500      hn4
OPNsense           link#9             UHS           0  16384      lo0
fe80::%lo0/64      link#1             U             0  16384      lo0
fe80::1%lo0        link#1             UHS           0  16384      lo0
fe80::%hn0/64      link#5             U            25   1500      hn0
fe80::21f:e1ff:fe10:e676%hn0 link#5   UHS           0  16384      lo0
fe80::%hn1/64      link#6             U          1614   1500      hn1
fe80::15:5dff:feff:2b00%hn1 link#6    UHS           0  16384      lo0
fe80::%hn2/64      link#7             U             0   1500      hn2
fe80::15:5dff:feff:2b01%hn2 link#7    UHS           0  16384      lo0
fe80::%hn3/64      link#8             U          4126   1500      hn3
fe80::15:5dff:feff:2b02%hn3 link#8    UHS           0  16384      lo0
fe80::%hn4/64      link#9             U          3482   1500      hn4
fe80::15:5dff:feff:2b03%hn4 link#9    UHS           0  16384      lo0
root@OPNsense:~ #

Quote from: cpw on May 26, 2020, 04:23:15 PM
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.

That is what I have done temporarily, but it should work. 

Link Local Addresses are the most common gateways that I have seen.

It worked with pfsense, so something different here.

Can you do:


# ps auxw | grep dpinger


post the v6 entry... ta..
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Sorry.. read the last message from you just after I posted. Can you post the none working and the working ps -auxw ....
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: marjohn56 on May 26, 2020, 07:32:10 PM
Can you do:


# ps auxw | grep dpinger


post 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

Just to eliminate the firewall, I added a rule to WAN passing LLA to LLA out,

Then tried pinging using WAN interface, I can see in the firewall log, it passing out, but no response.


Quote from: marjohn56 on May 26, 2020, 07:36:25 PM
Sorry.. read the last message from you just after I posted. Can you post the none working and the working ps -auxw ....

Working using Google DNS as the monitor:
root@OPNsense:~ # ps auxw | grep dpinger
root      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


Non-Working using default gateway:
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


Even more bizarre is this > My primary router works to my ISP using the link local address - ping or dpinger. My secondary test router to the primary router using link-local address does not ??? .
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

I am not sure if this is a valid test or not, but I opened 2 windows of opensense.  One is doing packet capture my link local ip (fe80::21f:e1ff:fe10:e676) as host to capture.

the other window tried to ping. This is result:
# /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%hn0
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: 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 loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host


The capture was empty.


Well a lightbulb came on... VLANs... my primary LANs are all VLANs. So I was then able to ping out from the primary to the  test router OK, but of course, not the other way.


Anyway.. I'll play with this tomorrow...


OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member