Actually even when setting the public key manually, FRR won't show it on a subsequent run:

@matzus give us more information

Hey @Viacheslav any chance of getting this merged into crux in addition to current?

I think we have a workable solution to this.

Looks good on 1.4-rolling-202101280218:

vyos@vyos:~$ configure
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# exit
Warning: configuration changes have not been saved.
exit
vyos@vyos:~$ ps ax | grep dhcp6c
 1860 ttyS0    R+     0:00 grep dhcp6c
vyos@vyos:~$ show version

Looks good on 1.4-rolling-202101280218:

vyos@vyos:~$ configure
[edit]
vyos@vyos# set interfaces dummy dum0
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface dum0
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options duid 00:02:00:00:0d:e9:30:30:31:45:34:36:2d:58:58:58:58:58:58:58:58:58:58:58:58:58:58
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# exit
Warning: configuration changes have not been saved.
exit
vyos@vyos:~$ show version

Development is continuing, so this PR is a draft

PR with smoketest check https://github.com/vyos/vyos-1x/pull/706

Would it be too hard to hack the legacy config management script into using systemd for scheduling reboots instead of atd?

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

I can confirm that the issue of accepting configurations that yield errors is present in the latest LTS (1.2.6) and latest rolling release (1.4-202101240218). However, I couldn't replicate the issue of the configuration parser breaking at startup. Do we want to prevent the user from committing erroneous input at the risk of annoying false positives?

Found a minor bug: if DHCPv6 PD is configured without requesting an IPv6 address, the configured DUID is not sent.

I think we can make it a systemd service that is started on commit-confirm and stopped on confirm.

The following options are deprecated (as of VyOS 1.2), and will be removed:

• protocols rpki timeout
• protocols rpki initial-synchronization-timeout

No one complained in a long time. ;)
If it re-appears, feel free to reopen. We also need to find a platform that knowingly does IKEv1 lifetime negotiation for testing this.

Last I checked it was able to log in the post-rewrite code. If the problem re-appears, feel free to reopen of course.

Backported to equuleus https://github.com/vyos/vyos-1x/commit/fb5a64a0a517291efe62185d053b437b62ef2921

THis issue also exists in the WWAN interface, can you please also provide a fix here and a SMoketest checkick this exact situation, that when switching from online -> disabled the interface is gone and no ppp peer configs exist?