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

vyos@r14:~$ show ntp
.- Number of sample points in measurement set.
                            /    .- Number of residual runs with same sign.
                           |    /    .- Length of measurement set (time).
                           |   |    /      .- Est. clock freq error (ppm).
                           |   |   |      /           .- Est. error in freq.
                           |   |   |     |           /         .- Est. offset.
                           |   |   |     |          |          |   On the -.
                           |   |   |     |          |          |   samples. \
                           |   |   |     |          |          |             |
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
ec2-34-206-168-146.compu>  31  15   70m     +0.225      0.056  +1295us   112us
ec2-18-193-41-138.eu-cen>  31  13   70m     -0.305      0.070   -968us   119us
ec2-122-248-201-177.ap-s>   6   3   52m     -2.587      0.901   +109us   252us
vyos@r14:~$

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

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

@Arc771 thanks for mentioning this, i now will close it

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

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

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

pre-auth stage of the negotiation does not populate the Device, IPv4, _TX, and _RX values yet, that's why the command fails: the raw array doesn't contain these variables yet.

@Viacheslav, Thank you for the hint. After further analysis, these are the findings from the tests done in the lab running 1.4.0 version on both sides with server/client setup.

In T6545#194997, @SrividyaA wrote:

@Viacheslav, For site-to-site or server/client mode, when used cipher option as none then also issue is noticed. When you commit, it gives this warning:

vyos@vyos# set int openvpn vtun1 encryption cipher none
[edit]
vyos@vyos# commit
Warning: "encryption none" was specified!
No encryption will be performed and data is transmitted in plain text over the network!

Logs:

Jul 10 14:51:39 openvpn-vtun1[12357]: Cipher NONE not supported

@Viacheslav, For site-to-site or server/client mode, when used cipher option as none then also issue is noticed. When you commit, it gives this warning:

@SrividyaA what cipher should be selected instead if none is removed and migrated away?

@SrividyaA Does it work for site-to-site ciphers option?

The critical issue was addressed in T5520, and the matter avoided with the move to revised image tools. No more to do on this at this point, and will close.

The correct pass options without "

set interfaces openvpn vtun20 encryption ncp-ciphers 'aes256'
set interfaces openvpn vtun20 hash 'sha512'
set interfaces openvpn vtun20 mode 'server'
set interfaces openvpn vtun20 openvpn-option 'push keepalive 1 10'
set interfaces openvpn vtun20 server subnet '10.10.2.0/24'
set interfaces openvpn vtun20 server topology 'subnet'
set interfaces openvpn vtun20 tls ca-certificate 'ca'
set interfaces openvpn vtun20 tls certificate 'cert'
set interfaces openvpn vtun20 tls dh-params 'dh'

Which exectly config it generates?
Based on this code should work https://github.com/vyos/vyos-1x/blob/b3b1d59d86af510c454da446f013b514389f5c7f/src/conf_mode/interfaces_openvpn.py#L683

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

set service monitoring telegraf loki url 'http://localhost'
set service monitoring telegraf loki metric-name-label 'r123'

@Viacheslav Fabse started working on it and I did have a look at the changes last week.

@Fabse @nvollmar Are any of you working on this task?

I tend to say that this is not necessary and very dangerous. These modules can easily destroy the VyOS filesystem when used improperly.

I would have put it on my list. @Fabse if you get stuck or need some support just slack me.

Sure @Viacheslav! I'll try to add the PR. Also thanks for the documentation @nvollmar :)

@nvollmar Do you want to claim the task?

Relevant telegraf documentation: https://github.com/influxdata/telegraf/blob/release-1.31/plugins/outputs/loki/README.md

It will be easy to add; you need to generate a new CLI like with "prometheus-client" for example https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/interface-definitions/service_monitoring_telegraf.xml.in#L188-L250
And add template changes https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/data/templates/telegraf/telegraf.j2#L45-L58

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

The suggested change as in matching number of "x" with number of characters in each octet/hextet in the IPv4/IPv6 address will be less anonymizing than todays method.

Draft PR Added: https://github.com/vyos/vyos-1x/pull/3599

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

In T6439#190868, @Viacheslav wrote:

Should be fixed in T6373

Should be fixed in T6373