I am currently attempting to configure an IPv6 BGP session on a Vultr VM. The issue is that Vultr does not offer a static IPv6 gateway; instead, they rely on Router Advertisement (RA). Consequently, I am unable to specify any static IPv6 routes.
Unfortunately, I am unable to initiate the IPv6 BGP session, as FRR refuses to establish an eBGP session through the system’s default route.
Is there a method to force FRR to establish an eBGP session using the kernel’s default route?
I had a VM setup with them a couple years or so ago, I did not except any RAs from them. I belive i used a static interface route for it. set protocols static route6 <peer>/128 interface <wan port>. They may require multihop aswell. Its been awhile so i dont remember all the details.
I’ve pocked around a bit more but unfortunately didn’t found a solution so far.
However, when I define a static route to the gateway I get via the RA, everything works fine and the bgp session comes up.
vyos@vyos# set protocols static route6 2001:19f0:ffff::1/128 next-hop fe80::fc00:4ff:febe:4db3 interface eth0
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# ping 2001:19f0:ffff::1
PING 2001:19f0:ffff::1(2001:19f0:ffff::1) 56 data bytes
64 bytes from 2001:19f0:ffff::1: icmp_seq=1 ttl=64 time=0.171 ms
64 bytes from 2001:19f0:ffff::1: icmp_seq=2 ttl=64 time=0.182 ms
But this isn’t a viable solution as the gateway can change at any time
There may be something that changed at some point, I recall being able to do the same as use a year or two ago, But with a fresh build im running into the same issue as OP. What version of VyOS are you using and what version of FRR does it have?.
It seems the solution is to enable “ipv6 nht resolve-via-default”, however it seems there is no option to do this via the VyOS cli currently. I created ⚓ T6001 Add option to enable resolve-via-default to get this feature added. Il try and see if i can get that done this week.
as I mentioned on task , that option was add as default behavior , although , it’s supported newest version (unfortunately, it’s an issues detected by our main developers) for that reason is not updated :