Also both to IPv4 and IPv6 per applicable vyos adjust-mss options.

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

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

In T7857#247986, @Viacheslav wrote:

@patient0 could you confirm it works as expected?

Still under review in FRR, but merged as FRR patch in VyOS.

Done.

It was decided to roll back SNMP update, so fix is not needed.

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

Resolved with https://github.com/vyos/vyos-build/pull/1098

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

@dsg, could you re-check the latest rolling?

@patient0 could you confirm it works as expected?

@peterablehmann It is not clear what you want in this task. Could you clarify?
Under local-role peer, the strict option is available.

vyos@r16# set vrf name net protocols bgp neighbor 11::5 local-role peer 
Possible completions:
   strict               Neighbor must send this exact capability, otherwise a role
                        missmatch notification will be sent

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

PR https://github.com/vyos/libnss-tacplus/pull/4

Updated PR https://github.com/vyos/vyos-build/pull/1092

Should be fixed after merging https://github.com/vyos/vyos-1x/pull/4942

New Playbook

Thank you. I see my mistake now. When I read under step 3, "Optionally, the user can attach a CDROM with an ISO as a cloud-init data source", it left me with the impression this was *optional*—that skipping this would not cause problems. I didn't realize that it would mean no default username/password would be set.

If you use the official proxmox image, you have to use cloud-init to set login/pass for the proxmox flavors.
Feel free to improve the documentation.
Thanks.

What is the intended way to apply configuration to a newly created proxmox flavor instance? At the page I referenced, it doesn't give any indication how to login or add a configuration under the "deploy from qcow2" section. Under the deploy from rolling release, it does mention the normal default vyos/vyos credentials.

We will get rid of this in the near future if we implement it now.
If we are focusing on the Common Criteria Profile for Network Devices, it is not accepted.
Needs to figure out in which form we can/should implement it if we want.

Proxmox images don't use any default passwords.
You use this flavour incorrectly.

We should dissalow to configure PPPoE if we use XDP, XDP wasn't implemented for VPP/PPPoE

In my opinion the headers are correct.
It could be described in the documentation.

I can confirm it is now working on my system since https://github.com/vyos/vyos-1x/pull/4946

@nicolas Fort @Srividya Anantapatnaikuni here is the solution

As an update, I didn't realize originally but it seems I need to both the new VM once before the password reset option will work. If I go directly to it on first boot I get a message about no config.boot file and this not being a restore tool. Booting normally once seems to create the default config, then the password recovery option works from the serial interface.

PR:
https://github.com/vyos/vyos-build/pull/1103

There is a straightforward solution here, which requires adjusting the image flavor build tools to respect the changes of https://vyos.dev/T6006, which resolved long-standing issues of migration and config initialization.
In short, after T6006:

• the file /usr/share/vyos/config.boot.defult is the build-time source of truth --- the flavor build system should install any flavor-defined config.boot.default at that location
• both /opt/vyatta/etc/config.boot.default and /opt/vyatta/etc/config/config.boot are installed on first boot, at different stages of gathering system-specific information in vyos-router (component version information, respectively, migration and activation updates)

A workaround could be the following:
Old:

vyos_config:
  src: "templates/template.j2"

New:

vyos_config:
    lines: "{{ lookup('template', 'templates/template.j2').splitlines() }}"

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