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

1. A̶d̶d̶ ̶c̶h̶e̶c̶k̶s̶ ̶t̶o̶ ̶p̶r̶e̶v̶e̶n̶t̶ ̶s̶e̶t̶ ̶i̶p̶ ̶a̶d̶d̶r̶e̶s̶s̶ ̶f̶o̶r̶ ̶c̶o̶n̶t̶a̶i̶n̶e̶r̶ ̶o̶u̶t̶ ̶o̶f̶ ̶r̶a̶n̶g̶e̶ ̶"̶p̶r̶e̶f̶i̶x̶" done

set container name alp02 image 'alpine'
set container name alp02 network NET01 address '192.0.2.1'
set container network NET01 ipv4-prefix '10.0.0.0/24

error

time="2021-04-14T00:52:03+03:00" level=error msg="Error adding network: failed to allocate all requested IPs: 192.0.2.1"
time="2021-04-14T00:52:03+03:00" level=error msg="Error while adding pod to CNI network \"NET01\": failed to allocate all requested IPs: 192.0.2.1"
Error: unable to start container "60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625": error configuring network namespace for container 60f20a2b517b4f828bef5683cd8a20504aa984648a0911f7f8df5c1a064d2625: failed to allocate all requested IPs: 192.0.2.1

The issue exists because the ifupdown package that is required for the eni renderer was removed by the https://github.com/vyos/vyatta-cfg-system/commit/3dd837f2d3518b7ddcf8e1ab68d8ab9f3eff0968
To not take back it again for all the platforms, the problem was resolved by the https://github.com/vyos/vyos-vm-images/commit/090e5367dc6df9b49c037e0b60f7adfafdf54a53 , so all the images created with the vyos-vm-images should not contain the problem with the renderer.

This task must be obsoleted by the https://phabricator.vyos.net/T2116

Just a small update on this.
PXE boot service for all 1.2 / 1.3 / 1.4 versions is up and running in private testing.

PR# 803

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

looks like this was missing in the bgp template
manually adding to /usr/share/vyos/templates/frr/bgp.frr.tmpl:

{%       if afi_config.as_override is defined %}
  neighbor {{ neighbor }} as-override
{%       endif %}

PR for crux https://github.com/vyos/vyatta-cfg-quagga/pull/73

UPnP is something I require (as a home user with multiple gaming systems), so I'm very happy to see this making progress in VyOS. I've been getting tired of the mess over in pfSense/OPNsense-land, wanting to try a Linux-based router, and I'm familiar with VyOS from past experience with "EdgeOS" on Ubiquiti hardware so it was on the top of my list, but held back by lack of UPnP in the past.

Thanks!

@danhusan that PR was only done to current and not backported. I just packported it to the crux branch.

Sorry for the late reply, I've dismantled the setup as I needed to put the PPP link back in use, I will look into it again tonight. In essence, it would be good to see something like this on terse view:

sudo journalctl -b

lspci -knn

The reason these validations https://github.com/vyos/vyos-1x/blob/aca3254d96d01cc37c9e15e02e500a36f3708959/interface-definitions/vrrp.xml#L220-L224
There is no such problem in version 1.4.

@Viacheslav 1.2.7.

@c-po I expected this to go into 1.2.7 but it did not. How would I tag this properly so it hopefully makes it into 1.2.8?

This can be close. The commit is working again after upgrading to the latest rolling

Submitted following PR:

@dtoux could you provide us with a mocked up output what you would like to see?

frr-reload output: 184 % Cannot have local-as same as BGP AS number