Needs the original file with OpenVPN addresses/statistics which are parsed /run/openvpn/{interface}.status
Without it, it will be difficult to do something.

Updates have been applied on 1.4 and 1.5.

I decided to dig into this a little more and try to trace this out:

sudo nft add chain inet vrf_zones trace_chain { type filter hook prerouting priority -301\; }
sudo nft add rule inet vrf_zones trace_chain meta nftrace set 1

@dmbaturin, @sever
Would love your input regarding the lack of headers when using the -c option. I've created a PoC around "chronyc -c activity" as it was the most straight forward command to start with.

@dmbaturin , @Viacheslav - I use debian snapshot repository when building VyOS LTS on my own.

side note, if you flush ruleset, and only add:

Something I just figured out is that the minute I do:

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

The regression causing 'image cannot be found" was fixed in https://vyos.dev/T6186.

PR:
https://github.com/vyos/vyos-http-api-tools/pull/11

Status update:

• "Like for like" functionality between .sh script and .py script is complete and working (can be viewed in PR)
• Raw output capability -> in progress

@Viacheslav concur that it looks to be resolved. The last log entry was at 9:10 and nothing telegraph-related has been logged in almost 30 minutes since. I will close ticket. Thank your help and insight.

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

PR https://github.com/vyos/vyos-1x/pull/3313
Add onlink option

set interfaces ethernet eth0 vif 10 address '10.20.30.1/32'
set protocols static route 10.20.30.0/32 interface eth0.10

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

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

It is more of a feature request than a bug due to specific kernel routes.
Feature to add onlink option

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

Read the documentation for the 1.5

I probably can continue here in summer at first.

My system finally crashed again today. I found a workload that generates enough traffic over the VPN to reliably re-produce.

I don't see those logs:

set service monitoring telegraf influxdb authentication organization 'vyos'
set service monitoring telegraf influxdb authentication token 'lxxx='
set service monitoring telegraf influxdb bucket 'vyos'
set service monitoring telegraf influxdb url 'http://192.168.122.14'

Did you try another image (not hello-world)?
Tested on VyOS 1.5-rolling-202404140022

Apachez, the QOS-MAPPING is FROM:TO, which means egress-priority 0 will be mapped to 2, egress-priority 2 will be mapped to 3. In my case i need only 0:3 or 0:5 on vif-s or vif-c because priority 0 is used by default for iperf application. Hope this helps for your understanding...

How is this supposed to work?

Viacheslav, YES it works, THANK YOU so much, now it's possible to set the priority on vif-c and vif-s. This is a great step forward to have this opportunity in my lab.
Now i have two questions:
-Is there a possibility to make the setting permanent ?
-And do you think, someone in the community is willing to implement a command/parameter to configure the priority on vif-c and vif-s also CLI ?. As i wrote I would pay for this implementation so everyone in the community can use this feature in VyOS.

Does it work?

vyos@r4:~$ sudo cat /proc/net/vlan/eth2.100.200 
eth2.100.200  VID: 200	 REORDER_HDR: 1  dev->priv_flags: 81121
         total frames received            0
          total bytes received            0
      Broadcast/Multicast Rcvd            0

@dmbaturin PR is here https://github.com/vyos/vyos-1x/pull/3307

@dmbaturin hope you don't mind but this looked like a good task for a beginner and with it being low priority thought I'd give it a go.

can we also include this change into sagitta epa3?

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

Will a migrationsscript be included so that users who used the default of:

Will a migrationsscript be included so that users who used the default of:

The priorisation for data traffic on our DSLAM access network is based on 802.1q because this are mainly Layer2 devices. The network between the DSLAMs prioritize also the data traffic based on 802.1q header. At the moment we need Layer2 ethernet tester which allow us to set the COS bit (0-7) on vif and vif-c+vif-s to measure the QoS through the network. The reason for my request was, to ask some VyOS community member, if this would be possible with VyOS + iperf like we do it today with the Layer2 ethernet tester.

Thanks for the quick fix! I intentionally messed with the file ownership and can confirm that VyOS 1.5-rolling-202404130016 will correct them to the proper values.

You can do the QoS priority on the VyOS by matching the traffic based on VLAN ID and then set the DSCP (TOS) using "set-dscp" according to the manuals below:

Yes, we want to configure the QoS priority "three bits" of the 802.1p field. In our lab the packet forwarding is based on 802.1q priority.
https://en.wikipedia.org/wiki/IEEE_802.1Q

You mean you want QoS based on VLAN which is named 802.1p ?

Link to forum thread: https://forum.vyos.io/t/output-similar-to-packet-tracer/