For eapol specifically, if your use case involves only a single chain (1 root CA + 1 or more intermediate CAs), then my fix from T4245 should do the trick. You can add each root/intermediate CA to the PKI and then set eapol to the leaf intermediate CA. When the wpa_supplicant configuration is generated, vyos will add the intermediate CA and all of its parents to the .crt file.

Submitted PRs:

Otp not configured

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

We have targets-checks 203.0.113.1, 192.0.2.1, and if any of these targets are unreachable, we delete this route.
Is it correct?

@c-po How is the review and discussion on this feature going?

A similar output exists

 show system login users 
Possible completions:
  <Enter>               Execute the current command
  all                   Show information about all accounts
  locked                Show information about locked accounts
  other                 Show information about non VyOS user accounts
  vyos                  Show information about VyOS user accounts`

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

In T4362#146398, @Viacheslav wrote:

@marc_s Will be fixed in the next rolling release, could you check?

Thanks @Viacheslav will test ASAP, next week I have a maintenance window, will let you know.

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

set system login max-login-session '1'
set system login timeout '600'

Is it possible to implement multiple test targets instead of just one?

Bug: unable to rename a failover route:

@Viacheslav Ok!

@Harliff It is better to write to this task if you find bugs or propose new features.
So anyone could claim/fix it.
Thanks.

@Viacheslav, where is best place to discuss the feature (ask a question or report a bug)?

PR https://github.com/vyos/vyos-build/pull/333
PR https://github.com/vyos/vyos-1x/pull/1938

Nice feature. I'm testing it now.

@neilmckee Thanks.
If output looks good we can close the task

Fixed in https://github.com/vyos/vyos-1x/commit/bcc9e2092b07954c72a90f3f9916c9e041308b5b

I think one of the problems is that all tables are generated even if there are no rules in it.

Yes. Packet drops are classed as "event_samples" internally. Definitions for telemetry counters are here:
https://github.com/sflow/host-sflow/blob/v2.0.50-4/src/Linux/hsflowd.h#L460-L486

@marc_s Will be fixed in the next rolling release, could you check?

Will be available in the next rolling release.