Based on feedback from the PR, I will do further investigation, come up with a proper test case and comparison with how others (eg: OpenWRT) implement MSS adjustment.

RP: https://github.com/vyos/vyos-build/pull/1108

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

FRR 10.5 removed support for applying route-maps to connected and kernel routes upon import from zebra. This is a breaking change, even though configs that used that feature are very unlikely to exist in the wild.

@Viacheslav, the thread is closed and I can't find a way to message @hyyram on the forum. Can you or someone with enough rights on the forum, message him/her?

PR: https://github.com/vyos/vyos-1x/pull/4950 , although to be honest I am not perfectly happy with the implementation, there is likely a better way to implement it.

@zsdc After testing on our server this configuration works correctly (no dhcp address but still... no issues with MTU and static address):

yos@he-r650-01# ethtool -i eth3
driver: mlx5_core
version: 6.6.117-vyos
firmware-version: 16.35.4030 (DEL0000000016)
expansion-rom-version:
bus-info: 0000:31:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

I am happy to produce a pull request which adds the missing forward chain.

Applies both to IPv4 and IPv6 per applicable vyos adjust-mss options.

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

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

In T7857#247986, @Viacheslav wrote:

@patient0 could you confirm it works as expected?

Done.

It was decided to roll back SNMP update, so fix is not needed.

Resolved with https://github.com/vyos/vyos-build/pull/1098

https://github.com/vyos/vyos-build/pull/1105

@dsg, could you re-check the latest rolling?

@patient0 could you confirm it works as expected?

@peterablehmann It is not clear what you want in this task. Could you clarify?
Under local-role peer, the strict option is available.

vyos@r16# set vrf name net protocols bgp neighbor 11::5 local-role peer 
Possible completions:
   strict               Neighbor must send this exact capability, otherwise a role
                        missmatch notification will be sent

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

PR https://github.com/vyos/libnss-tacplus/pull/4

Updated PR https://github.com/vyos/vyos-build/pull/1092

Should be fixed after merging https://github.com/vyos/vyos-1x/pull/4942
Related task T8125

We will get rid of this in the near future if we implement it now.
If we are focusing on the Common Criteria Profile for Network Devices, it is not accepted.
Needs to figure out in which form we can/should implement it if we want.

We should dissalow to configure PPPoE if we use XDP, XDP wasn't implemented for VPP/PPPoE

I can confirm it is now working on my system since https://github.com/vyos/vyos-1x/pull/4946

PR:
https://github.com/vyos/vyos-build/pull/1103

There is a straightforward solution here, which requires adjusting the image flavor build tools to respect the changes of https://vyos.dev/T6006, which resolved long-standing issues of migration and config initialization.
In short, after T6006:

• the file /usr/share/vyos/config.boot.defult is the build-time source of truth --- the flavor build system should install any flavor-defined config.boot.default at that location
• both /opt/vyatta/etc/config.boot.default and /opt/vyatta/etc/config/config.boot are installed on first boot, at different stages of gathering system-specific information in vyos-router (component version information, respectively, migration and activation updates)

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

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