Will be fixed in rolling releases starting 20210112. Thanks for reporting.

Hello.
Do you need something else?

systemd-container - easiest way to get containers rapidly into VyOS because all of the infrastructure (systemd) is already there.
We build our images with it, works fine.

You might want to take a look at the patches in T228 - its a 5.4 build with a bunch of C fixup, but using the Intel proprietary drivers for an in-tree build (permits signing of all modules at kernel build time).
We have this running on a host with a dual-port 740 (not doing all that much, some routing, NAT, ACL, and a couple of OpenVPN and IPSEC tunnels), and it seems to be fairly happy in that low intensity environment.
I can try to beat up on it and see how it fares, but probably worth a try.

Needs to add that expression with the right logic.

$VAR(../../../../@) != $VAR(../../../interface/remote-as/@)

1.2 crux the same behavior

I have just re-checked. It works fine for everyone LSAs type.
summary and asbr-summary also works fine

@runar @c-po A new PR has been created and can be reviewed

PR:
https://github.com/vyos/vyos-1x/pull/677
https://github.com/vyos/vyatta-cfg-system/pull/134
https://github.com/vyos/vyos-documentation/pull/424

external works for me, can you re-check?

vyos@r5-roll:~$ show ip ospf database external 10.20.40.0

It works fine for show ip ospf database router x.x.x.x and show ip ospf database network x.x.x.x
It does not work for show ip ospf database <summary|asbr-summary|external> x.x.x.x
The output of these commands is empty.

Can be cherry-picked for equuleus and crux

PR https://github.com/vyos/vyatta-cfg-quagga/pull/62

I'm on 1.4-rolling-202101100217 and it looks like the DUID command is gone at the interface level or system level. Besides overwriting the DUID file (which seems to not persist between upgrades), is there a good strategy here if the use-case doesn't require a custom DUID per interface?

tuned is known for altering values inside sysctl, its written on the projects web page - I simply did not thought about that issue when installing tuned.

Sounds good, syslog needs to be set to level debug for kernel facility, so it's per default only visible in the journal logs. Tested with a few tunnels, it's not very noisy, even with 20 tunnels.

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

Ok. I'll do it

@craterman Will be fixed in the next rolling release, can you check it tomorrow?

FRR value for the same command

Thank you for the response. There is also a smoketest wmbedded which runs during ISO ge erstion ensuring this always works:

+1 for default, IPsec is also very chatty

Why not add this by default?

just confirming 1.4-rolling-202101100217 works as well

This is fixed:

trae@cr01b-vyos:~$ restart flow-accounting
trae@cr01b-vyos:~$ show ver

output looks then like below and is being logged to ringbuffer as well as systemd-journald:

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

When the vyos kernel is higher than 5.8+, you can start the formal test before merging nat66

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

In T915#81521, @Cheeze_It wrote:

@c-po @runar If there are no other problems, I will change the VLAN aware bridge code and update the description of T3137 in the near future

@c-po

There is no need to use set interfaces bridge br1 vlan-aware, as soon as the vif node is present, it will be vlan aware. We should not randomly add all kinds of new CLI nodes.

I pushed it already. If you wish to re-merge, it's there.