This is a bug which is introduced by the rewrite of policy from old node.def files to XML and Python.

That was generated by running make defconfig, enabling numa, and saving it back. BUILD_BIN2C is related to kexec.

It seems to show the output correctly when single tunnel is present not with multiple tunnels.
Ref Task: https://phabricator.vyos.net/T3473

Latest rolling runs 5.10.30 - patch is in there, please verify

That should be rewritten in the same style as the interface stuff rendering the appropriate commands (https://github.com/vyos/vyos-documentation/blob/master/docs/_include/interface-disable.txt)

Can someone modify this sentence and add an output statement before it to see what caused the error?

Version: VyOS 1.4-rolling-202104151445

That's a good point. I just might do that.

@jestabro Cool!!!

Is there a specific reason not to put it in vyos-1x instead?

Thank you. If you have any questions, please keep in touch.

@jack9603301 Unfortunately the only environment I have to test in is home, and my wife would probably kill me. ;) I also don't have a second "router PC" available right now which I would need before I can spin up VyOS and give it a try. I need to keep the other system untouched so I have something I can fall back on if I can't make VyOS work the way I want, and the hardware is old enough that if I virtualize my router OS, network performance suffers. I tried using ESXi with OPNsense and WAN throughput was down 200-300Mbps vs. what I can do on the bare metal.

@ZPrime Although UPNP is not merged, you are welcome to test it if you wish, and if you have any questions, please let me know (you can also get in touch with me on Stack) so I can fix it before merging

ipv6 address autoconf works here. It does pick up a v6 address from the RA - I had an error in the config on the router issuing the RA announcements, and thought that autoconf was not working, but it does. Perhaps this issue should be closed?

The suggested resolution is to define an include file with the syntaxVersion element. The syntaxVersion element contains the component name and version number; the including interface definition file corresponds to the conf_mode script. Hence, this defines a mapping

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

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 %}

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.

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: