PR for 1.3.x https://github.com/vyos/vyos-1x/pull/2225

For the tests above, which configs are actually being used?

Some observations:

Cherry-pick to 1.4 https://github.com/vyos/vyos-1x/pull/2226

PR for 1.4 https://github.com/vyos/vyos-1x/pull/2224

The PR is merged

PR is created https://github.com/vyos/vyos-build/pull/394

Sagitta PR updated with fix for regression in T5556.

The logic error is fixed in commit above: updates work as expected, and all smoketests (but for unrelated test) pass.

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

Not as such: this is a logic error in T5353, which will be fixed momentarily. Nonetheless, T5514 is worthwhile to consider.

Related to https://vyos.dev/T5514 ?

For 1.4 add session [default=ignore success=2] pam_succeed_if.so service = sudo to /etc/pam.d/common-session-noninteractive fixes the issue

# here are the per-package modules (the "Primary" block)
session [default=1]                     pam_permit.so
# here's the fallback if no module succeeds
session requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
session required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
session required        pam_mkhomedir.so umask=0022 skel=/etc/skel
session [default=ignore success=2] pam_succeed_if.so service = sudo
session [default=ignore success=ignore] pam_succeed_if.so user ingroup aaa quiet
session [authinfo_unavail=ignore success=ok default=ignore] pam_radius_auth.so
session required        pam_unix.so
# end of pam-auth-update config

Logic error in recent bug fix; correction is being checked ...

current PR: https://github.com/vyos/vyos-1x/pull/2217
1.4 PR: https://github.com/vyos/vyos-1x/pull/2218
1.3 PR: https://github.com/vyos/vyos-1x/pull/2219

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

PR for Sagitta (draft until dependency PR 2207 is merged to Sagitta):
https://github.com/vyos/vyos-1x/pull/2215

@sdev take a look over these repository :

PR for current:
https://github.com/vyos/vyos-1x/pull/2211

PR for Sagitta:
https://github.com/vyos/vyos-1x/pull/2207

Well in that case it boils down to if the FRR/vrrpd supports namespaces, various tracking (interface etc) aswell as multicast vs unicast which keepalived seems to support them all.

In T2444#158779, @Apachez wrote:

If the FRR/vrrpd is good enough then the main benefit is that the FRR/vrrpd is already included so no need to also include and use keepalived (unnecessary files and binaries and dependencies).

Things to verify however before a switch is performed (and keepalived is thrown out) is support for vrf/namespaces, various interface and other tracking and multicast vs unicast (it seems that keepalived supports them all - dunno about FRR/vrrpd).

https://docs.frrouting.org/en/latest/vrrp.html

If the FRR/vrrpd is good enough then the main benefit is that the FRR/vrrpd is already included so no need to also include and use keepalived (unnecessary files and binaries and dependencies).

Might be related: