Trying to find more information with debugging settings of zebra process.
Apr 12 23:52:18 router zebra[1472]: 0:2404:5780:3::/48: Route install failed
Apr 12 23:52:18 router zebra[1472]: 0:2404:5780:3::/48 Stale dplane result for old_re 0x555f6166b300
Apr 12 23:52:18 router zebra[1472]: 0:2404:5780:3::/48 Processing dplane ctx 0x555f765ff7a0, op ROUTE_UPDATE result FAILURE

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

Thanks very much, @jestabro !

@chrismarget I'll commit the changes shortly, and close the task; thanks!

c-po closed PR#100 based on intent to restore (I didn't realize they'd been removed) those packages via the dockerfile.

Tested on 1.2.5

There are no other reports about such issues
we need valid reproduction procedure for this, otherwise, not much that we can do

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

could you please try this patch. if it still fails, can you remove the 'mtu' from the 'options' line and try again ?

diff --git a/python/vyos/ifconfig/tunnel.py b/python/vyos/ifconfig/tunnel.py
index 0506066..46900ce 100644
--- a/python/vyos/ifconfig/tunnel.py
+++ b/python/vyos/ifconfig/tunnel.py
@@ -141,8 +141,8 @@ class GREIf(_Tunnel):
     default = {'type': 'gre'}
     required = ['local', ]  # mGRE is a GRE without remote endpoint

Retested today using VyOS 1.3-rolling-202004120117

Also fixed in 1.3 https://github.com/vyos/vyos-build-kernel/commit/006550a30afa3c595a07782ec3ce239dc6f65443

Any comments @dmbaturin ?

with T2238 interface can be listed using their feature definition (broadcast, bonding, bridge ...).

@zsdc asked if we could find out a better API for the command and there is an issue where it seems that the environment dict passed to Popen() is not working as expected.

on any equipment with many interfaces, you would expect "port 0" to be "eth0", etc. As vendors are likely to give incremental mac addresses to their interfaces, could the hardware mac address be used at boot to order the interfaces? adding new interfaces may cause a re-numbering but it would give stability on if the hardware does not change.

Naming convention seems fine.

Uh, that's nice easter eggs folks :-) Thank you both for your valuable hints! They'll be very handy!

It is a useful feature .. please do not kill, This patch will fix things until it can be looked into 🤕

+1 on that, already migrated l2tp and sstp VPN to systemd today

I use http://jinja.quantprogramming.com/ to test templates. With it you
can test all possible combinations of input variables. (You need to test
all combinations if you're stripping whitespace, as some combination can
have a good format, another can have too much whitespace stripped)

Looks good, you can actually emulate a wifi card: modprobe mac80211_hwsim

PR https://github.com/vyos/vyatta-netflow/pull/5

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

@Dmitry
set system flow-accounting interface 'eth4.XX'
set system flow-accounting interface 'eth4.XX'
set system flow-accounting sflow agent-address 'xxx.xxx.169.246'
set system flow-accounting sflow sampling-rate '2048'
set system flow-accounting sflow server xxxxx.tld port '6343'

@blackmetal provide, please flow accounting configuration show configuration commands | strip-private | match flow for reproducing