@scj643 If you want migration, there are some doubts about how it could be T6304 (old task with some proposes CLI)

PR https://github.com/vyos/vyos-vpp-patches/pull/25
PR https://github.com/vyos/vyos-1x/pull/4855
https://github.com/vyos/vyos-build/pull/1069

Ok so this can by worked around by running set terminal key query-help disable is operation mode.

@Viacheslav I will need some help with making configuration migrations. Since it seems for this we will need to make significant changes to the commit-archive options since right now it uses a leafNode. I do have a somewhat hacky option to allow &subdir=path/to/subdir inside the url.

@Viacheslav I need some guidance. I am trying to figure out what validator to use and it seems that the file-transport and url validators aren't in the vyos-1x repo and I can't seem to figure out what they are actually pointing to.

https://github.com/vyos/vyos-1x/pull/4856

Bug does not appear in VyOS 1.4.3

https://github.com/vyos/vyos-1x/pull/4854

With this option, set interface feature eth1 ip4-not-enabled arc ip4-unicast disable

Packet 22

Thanks Andrii, confirmed the issue.

Commit failed because you have to set local-zone and you don't have it
Behavior is correct.

Seems like the initial KeyError issue is resolved recently in https://vyos.dev/T7112

Re-tested in 2025.11.18-0020-rolling

One solution that I found, edit the template to allow dhcp_plugin

sudo nano -c +93  /usr/share/vyos/templates/vpp/startup.conf.j2

Add plugin:

plugin dhcp_plugin.so { enable }

Call this command:

sudo vppctl set dhcp client intfc eth1 hostname r14

eth1

vyos@r14# sudo vppctl show int addr
eth0 (up):
  L3 192.168.122.14/24
eth1 (up):
  L3 192.168.100.201/24
local0 (dn):
tap4096 (up):
tap4097 (up):
[edit]
vyos@r14#

@evgmol I have deleted the tag

@Viacheslav @badger42 hi Guys! Why is this in the Ansible FR section?

This could be done with systemd-cryptenroll and LUKS while bound to a TPM. Also you could bind it to a PKCS11 token (Yubikey) with a no touch and no pin policy to allow auto booting. (Not recommending FIDO2 because it always requires user presence)