@jknott said in IPv6 routing over VPN:
Can you spare another? Also, you can always use Unique Local Addresses for the tunnel.
No. But the tunnel is not the problem. Here I already use Unique Local Adresses.
Here is my IPv6 configuration, maybe it helps to solve my problem:
Wireguard Server:
[Interface]
Address = 10.56.0.1/24, fe00::1/64
PrivateKey = ********************
ListenPort = 51820
[Peer]
PublicKey = ********************
AllowedIPs = 10.56.0.5/32, fe00::2/128, 2001:********************::/64
At the wireguard client side (the pfSense) I use the fe00::2. This works.
But the routing/NAT between my DMZ server and the pfSense is not working:
On the pfSense DMZ interface (which I gave no IPv6 ip) I have the following static route:
2001:******************** 3c:ec:ef:70:6d:ba UHS igb2
On the DMZ server (with the ip 2001:********************:21/128) I configured the route back as the host route:
[::]/0 fe80::3eec:efff:fe70:6dba UGH 1024 3 0 ens18
And here comes my problem:
Direct ping to fe80::3eec:efff:fe70:6dba (the pfSense's link local address) works. But no NAT or routing to other targets.