MadaMada
@madamada@snac.void.my
[root@serv ~]# ndp -na | grep fe80::1Grr...
[root@serv ~]# netstat -rn6 | grep default
default fe80::1%eth0 UGS eth0
[root@serv ~]# ping -6 -c2 -t2 one.one.one.one
PING6(56=40+8+8 bytes) 2a02:c207:xx:xx::1 --> 2606:4700:4700::1001--- one.one.one.one ping6 statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss[root@serv ~]# curl -v6I https://one.one.one.one/
* Host one.one.one.one:443 was resolved.
* IPv6: 2606:4700:4700::1111, 2606:4700:4700::1001
* IPv4: (none)
* Trying [2606:4700:4700::1111]:443...
^C
Update: After trial and error, a static ndp entry is needed to recognize their shitty gateway..
ndp -s fe80::1%eth0 gw:mac:addr
ff02::2%eth0 doesn't return any neighbour routers, ndp -na doesn't show any neighbours .. simply adding fe80::1%eth0 won't work right away, so we have to resort to tricks like this to get IPv6 going.. grr
@madamada If only I would have known about static ndp entries 2 years earlier ... back then I lost IPv6 connectivity on my VPS regulary every 4 weeks or so because the gateway (fe80::1%vmx0) disappeared from the neighbor discovery table...