I think I'm hitting the same issue in 2.6.0-RELEASE
I have a working VTI IPv4 routing scenario linking two LANs and wanted to add ipv6
I added a second P2 on both pfsenses nodes configured as follow :
The ipv6 tunnel come up successfully, however gateways are not defined correctly :
In dashboard/gateway widget for OPT1_VTIV6 : ipv6 is displayed as ~, RTT pending, status Unknown In system_gateways.php, a gateway named OPT1_VTIV6 appears but stays empty with no ipv6 nor monitor ip.Interfaces are configured correctly :
Node A : inet6 fd87:dcb9:c321:6610::1 prefixlen 126
Node B : inet6 fd87:dcb9:c321:6610::2 prefixlen 126
I'm however able to ping both sides of the vti tunnel
If I add a static route from my lans to OPT1_VTIV6, boths lans can ping themself
However, netstat -rn for the static route shows :
2001:41c9:1111:d2d::/64 ipsec1 US ipsec1
Which confirms the lan is routed directly to the interface and not to the ipv6 vti tunnel like it is done for ipv4
If I add a manual gateway 'test' (on node B for example) on interface OPT1 with ip fd87:dcb9:c321:6610::01 -> the dashboard displays this gateway correctly
I can then define my static route on this 'test' gateway
Now netstat -rn shows this for the static route :
2001:41c9:1111:d2d::/64 fd87:dcb9:c321:6610::1 UGS ipsec1
(same behaviour as with ipv4 vti)
Traffic is passing correctly in both scenarios, however it does not feel normal to have a route directly to the interface in this case.
I tried to set P2 local ip to single address (fd87:dcb9:c321:6610::01) or wider range fd87:dcb9:c321:6610::01/64) with no more success
If I disable gateway monitoring : no changes
If I force a monitoring IP, the gateway is shown as 'Online' but still with empty ipv6
Any clue on fixing this ? Or to disable automatic gateway creation ?