https://github.com/vyos/vyos-build/pull/490

https://github.com/vyos/vyos-build/pull/490

The working implementation is linked below; performance is not yet comparable to the legacy loadFile, though there are obvious points of optimization to be made. The general framework will be submitted for PR to support other development, with load_config as an illustrative example, but not yet a replacement for loadFile.

New data point. I installed vanilla Debian 12, connected modem via

it think that we can use also something similar to what we use ocserv to generate ssl certificates:

I put together a PR for this https://github.com/vyos/vyos-1x/pull/2908. I just edited this in github, I was kind of hoping that a workflow would run the smoketests, but I'm not sure that is the case. Either way I'll try pulling the code local and see what I can figure out.

Maybe something like

Seemingly long term solution is to migrate to a DHCP/DHCPv6 server that supports it. I've been going back and forth with the systemd folks -- https://github.com/systemd/systemd/issues/27219
One of them seems to show it works fine, but I can't replicate it. I am going to try and do it under just normal Debian 12 bookwork and not VyOS so as not to introduce anything strange

Some update in the time i posted it on the forum and posted it here,
today i added an additional IPSec-VTI VPN with OSPF (IPv4),
all working as expected.

it makes seens , agree with add a Config Error to do not allow both options simultaneously ,.

In this case, 'both'' is preferred now.
If you use in frr

Can this be backported to 1.3 cause I run into the problem today on 1.3.5

Firstly, note that this is a failure in boot configuration, and is not related to migration: the log output of vyos-router is misleading, reporting the steps following initialization. On success:
Starting VyOS router: migrate configure
on failure:
Starting VyOS router: migrate configure failed !

Adding vyos-config-debug to the boot options on first boot after installation will provide more information on the config error, if it is possible to try that; cf.:
https://docs.vyos.io/en/sagitta/contributing/debugging.html#kernel

Duplicate of https://vyos.dev/T3500

In T6001#174979, @fernando wrote:

this command was added by default in FRR , but it's supported on lasted version (9.1):

https://docs.frrouting.org/en/latest/zebra.html#clicmd-ip-nht-resolve-via-default

https://docs.frrouting.org/en/latest/zebra.html#clicmd-ipv6-nht-resolve-via-default

as I mentioned , it was added in 9.1 as default behavior :

PR:
https://github.com/vyos/vyos-1x/pull/2902

I was looking into the issue here on the forums for the user, i see the documentation says it should be enabled by default for the traditional profile which it appears to be set to use, but it does not work until i manually set that option through vtysh.

this command was added by default in FRR , but it's supported on lasted version (9.1):

Firstly, note that this is a failure in boot configuration, and is not related to migration: the log output of vyos-router is misleading, reporting the steps following initialization. On success:
Starting VyOS router: migrate configure
on failure:
Starting VyOS router: migrate configure failed !