Since the original vyos-vm-images is deprecated, I suppose we should close this for now.

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

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

Well-known behavior when you use VTI interfaces you have to use set vpn ipsec options disable-route-autoinstall otherwise you can get any unexpected things.

Kea doesn't have that issue, and in 1.5 rolling release builds, static leases are already displayed in show dhcp server leases. But in ISC DHCPd, which is unmaintained, I'm not sure if we should switch from the tried and proved static leases to anything else.

@jack9603301 Feel free to create a PR as do usually do for documentation, the Task is not required.
For example https://github.com/vyos/vyos-documentation/pull/1229

Are we going to just let EVPN be the L2VPN technology of choice and not go down the VPWS/VPLS route for L2VPN? EVPN is the future anyway, so going and adding VPWS/VPLS is kind of doing legacy work.

No longer applicable now that XDP is phased out.

We use the netavark plugin for the containers, which fixes this.

set container name alp01 image 'alpine'
set container name alp01 network NET01
set container network NET01 prefix '100.64.0.0/24'

Fixed in https://github.com/vyos/vyos-vm-images/commit/090e5367dc6df9b49c037e0b60f7adfafdf54a53

@fernando Thanks!

i've re-checked with the new image from GCP and new cloud-init version , it seems to be working as expexted :

The kernel is not supporting pseudowire/VPLS now
this patch was never merged into the kernel

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

No, installing the miniupnpd_functions.sh file does not correct the problem.

Another bug it that /config/upnp.leases is hardcoded, but there is no script who creates it https://github.com/vyos/vyos-1x/blob/aebb458262072457c6a3840d1b17031fbd780eca/data/templates/firewall/upnpd.conf.j2#L128

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

Will it work if you manually download the functions? https://github.com/miniupnp/miniupnp/blob/miniupnpd_2_3_1/miniupnpd/netfilter_nft/scripts/miniupnpd_functions.sh

OK, a little digging around in the grub configs led me to a "workaround" solution for the serial console problem after the machine is booted.

Can confirm this is exactly the same in 1.4 rolling (as of Jan 09). Same errors. The miniupnpd daemon receives the request (for either a UPnP, NAT-PMP, or PCP port mapping) and then reports the errors @simplysoft reports in the description.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2787 which will be backported to 1.4

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

Lowering priority to normal to proceed with adding the interface-monitor daemon development, mentioned above, for 1.5.

Quick test done on a VM with 1 CPU and 1G RAM:

vyos@1.4.0-rc1# for I in  {1..2542}; do set firewall ipv6 name Test rule $I action accept ; set firewall ipv6 name Test rule $I destination port $I; set firewall ipv6 name Test rule $I protocol tcp ; done
vyos@1.4.0-rc1# time commit

@sempervictus Thanks for the update!

OK, the grub serial config described here got me as far as seeing the Grub selection screen at boot time.

Oh wow, this is ancient. Can definitely close this out - @zsdc and i figured out a bunch of the insanity around cloud-init since then and i've got it working in our openstacks as well as public clouds on a single config.

What to do with atop and logrorate?