This bug should be closed since vyos has moved to use Kea and no longer uses wide-dhcpv6

@Viacheslav AFAIK this request has nothing to do with https://vyos.dev/T3771

Since it has been implemented, can also global options be implemented?

I even have a router with it working:

This is not a feature request, this has been working until made the detail available only when the lldpd service was running or not. It was even documented:

In my case the upgrade from 1.4-rolling-202308060317 to vyos-1.4-rolling-202308060317 made the vrf unavailable so no access to management. Booting back to old version became working again.

This also affects latest rolling release as of 1.4-rolling-202308240020 which is available @vyos.io

Nope, now i had to do

@c-po Tried with latest rolling 1.4-rolling-202308060317, rpki doesn't start automatically, one must do:

I believe this change had an unintended side effect:

This is a nice addition but it requires also implementation of RFC 8781 for it to work. It has been merged in latest radvd https://github.com/radvd-project/radvd/commit/a6460662c6ac2b13307a8977ef068825b66fbce0 but it still hasnt been released

There's something weird happening with this. If you change simply persistent-keepalive from 25 to 30 or 30 to 25 will reactivate the peer. At least thats my experience. Doing anything else didnt work for me including:

i dont know if this is good or not, next version of radvd will include options la RFC8781 which are not even though for frrouting, even im opening them a request for such feature but i dont expect it to be available anytime soon.

Mark as resolved as a i have tested it on 1.4-rolling-202207260217 and has been merged

@c-po which one is the new syntax?

@Viacheslav i believe this one can be closed ge and le where inverted order until i found out the error.

I have added a pull request for this:

@Viacheslav yep that one works...

While i like the inclusion of NAT64 inside vyos (And the effort vfreex has made), i believe that tayga is not the way to go, it was last updated on 2010-12-12 according to the readme in it. Jool on the other hand has a bigger throughput being kernel module. The only issue i believe is the module compilation cause configuration is quite easy.