PRs:

• https://github.com/vyos/vyos-1x/pull/4923
• https://github.com/vyos/vyos-documentation/pull/1731

Proposed config options:

It has been fixed and should work now.
I'm waiting for comments from the forum: https://forum.vyos.io/t/i-cant-complete-my-registration-for-vyos-dev/17173/8?u=o.kuchmystyi

Looks like it's already been implemented here:

I have tested the latest internal build of sagitta and the next version 1.4.4 will contain this fix.

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

In T4001#173519, @Viacheslav wrote:

Needs to re-check for 1.4/1.5

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

PR: https://github.com/vyos/vyos-1x/pull/4881
Documentation PR: https://github.com/vyos/vyos-documentation/pull/1719

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

I tried to reproduce these errors for VyOS 2025.11.25-rolling but everything works fine. @a.kudientsov could you re-check it again?

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

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

PR: https://github.com/vyos/vyos-1x/pull/4806
Documentation PR: https://github.com/vyos/vyos-documentation/pull/1697

@rherold I tried to reproduce this behavior using your configuration for VyOS 1.4.2, 1.4.3 and 1.5, but everything works fine in my lab.

PR: https://github.com/vyos/vyos-1x/pull/4734
PR for documentation: https://github.com/vyos/vyos-documentation/pull/1686

@dmbaturin, @c-po, @jestabro and @n.fort

In VyOS 1.3, this command was used to integrate with StrongSwan's uniqueids=no setting in ipsec.conf, facilitating environments requiring non-unique IKE_SAs. However, with StrongSwan's transition to swanctl.conf, such unique ID management should ideally be performed via the connections.<conn>.unique parameter. More details about the migration you can find here.