[BUG]IPV6 Link monitor can't ping

Started by norgan, March 24, 2021, 03:27:10 AM

Previous topic - Next topic
March 24, 2021, 03:27:10 AM Last Edit: March 25, 2021, 06:09:37 AM by norgan
I have a dual stack link and today I had no internet because the ipv6 wan interface had no IP address. I'm not able to properly evaluate it's state so the gateway group doesn't work.
Id like to have a ping working so i can monitor the link and flick back to ipv4 if ipv6 isn't working.


root@router:~ # ping 2401:d002:2302:b00:9ae7:f4ff:fe67:e871
ping: cannot resolve 2401:d002:2302:b00:9ae7:f4ff:fe67:e871: Host name lookup failure
root@router:~ # ping 2620:fe::fe
ping: cannot resolve 2620:fe::fe: Host name lookup failure
root@router:~ # ping6 2620:fe::fe
ping6: UDP connect: No route to host
root@router:~ #


Update: As I have come to understand, it seems the addition of an ipv6 gateway into a gateway group causes some ipv6 strangeness. I have taken the ipv6 gateway out of the group and things have settled.

Now that is strange, I can ping google and my next hop on the router.
2401:d002:2302:b00:9ae7:f4ff:fe67:e871

But can't ping the quad9 ipv6 dns servers.
2620:fe::fe
2620:fe::9

Perhaps they are filtering ICMP. Could someone with working ipv6 please ping one of the above and let me know if you get a response.

And now i can't even ping that lol I think my provider is having ipv6 issues as well but those quad9 servers don't seem to ping. I like using quad9 as a link monitor because that's my DNS forwarder target.