Cannot ping fe80::1 / discover a gateway in some KVM environments

mfld

Some VPS hosts will give me DHCP6. Some will tell me to use a gateway that is from a different prefix.

I usually make it work easily by adapting the way it works in Linux to pfSense.
Hetzner for example:

IPV6_DEFAULTGW=fe80::1
IPV6_DEFAULTDEV=eth0

It's just a matter of creating the gateway in pfSense.

For others that provide a gateway that is on a different prefix I do a GW on fe80::1 and then one static route that says to reach that prefix via the fe80::1 GW.

Example:

VPS has 2001:db8:0:20::/64
Gateway I am given is 2001:db8::1

I can usually

ping6 -I vtnet0 fe80::1

I can make a static route to 2001:db8::1 via fe80:: and all is well.

But I have now come across two VPS providers where their KVM VPS will not work with pfSense. I can spin up any flavor of Linux and it's all good but with pfSense I cannot even do

ping6 -I vtnet0 fe80::1

--- fe80::1 ping6 statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss

For testing I did all kinds of stuff. Allow APIPA, disable filtering etc. A full

pfctl -d

Brings some interesting result:
PING6(56=40+8+8 bytes) 2001:db8:0:20::99 --> 2620:fe::fe
ping6: sendmsg: No buffer space available
ping6: wrote 2620:fe::fe 16 chars, ret=-1
ping6: sendmsg: No buffer space available
ping6: wrote 2620:fe::fe 16 chars, ret=-1

Other than what I described above, is there another pfSense equivalent of what would in CentOS be achieved by:

ip addr add 2001:db8:0:20::99/64 dev eth0
ip -6 route add 2001:db8::1 dev eth0
ip -6 route add default via 2001:db8::1 dev eth0

FWIW VPS hosts where I have encountered this so far are Trabia and AlphaVPS.

DaddyGo

This post is deleted!