Looks working

Already implemented

vyos@r4# set interfaces macsec macsec0 security static 
Possible completions:
   key                  MACsec static key
+> peer                 MACsec peer name

@cuongdt1994 could you add an example of integration and configuration?

@Giggum yes you can choose which image will be booted

vyos@r4:~$ set system image default-boot 
The following images are available:
	1: 1.5-rolling-202404120636 (running) (default boot)
	2: 1.5-rolling-202404090019
Select an image to set as default:

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

The kernel still does not support it without patches

root@r4:/home/vyos# echo "65535" | tee /sys/class/net/br2/bridge/group_fwd_mask 
65535
tee: /sys/class/net/br2/bridge/group_fwd_mask: Invalid argument
root@r4:/home/vyos#

@tjh Do you still need this package? As it was relevant for ipset/iptables

@m.korobeinikov It could be a part of the existing op-mode generate interfaces debug-archive
Can you extend this script to include the required options and create a PR?

Closes it as wontfix

Note "Note that RFC 1701 is mentioned in MikroTik's docs but there is nothing in common between the standard and the actual protocol used."

You can create /use your own images

vyos@r4:~$ generate container image foo path 
Possible completions:
  <filename>            Path to Dockerfile

It looks fixed by the upstream

64 bytes from 8.8.8.8: icmp_seq=18 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=116 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=116 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=116 time=20.1 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=116 time=20.1 ms

It is not backported to 1.4
So for 1.3, it won't be backported

It was implemented around a year ago https://github.com/vyos/vyos-1x/commit/e201454f073c9a92fb56b65f497eae55fc634521
Just need to check if it works as expected.

In T6222#183247, @Chrisc-c-c wrote:

Wouldn’t your suggested fix to https://vyos.dev/T6223 also apply here? If the plan is to validate interface name lengths and allow custom names this would be a non-issue.

CPU Quota and ipt_netflow are different tasks.
CPU limits could be part of this task https://vyos.dev/T3706

Propose to add names for the interfaces:

set interfaces ethernet eth2 vif-s 100 vif-c 300 name if9999

An additional found old dhcp-client issue, does not properly support interface names with length > 13
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858580

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

@dex can you re-check?
It should execute the stop script if disabled in config https://github.com/vyos/vyos-1x/blob/5d890037b177ce6971ac00f52e4cce2cac898f46/src/conf_mode/high-availability.py#L204-L206

Can someone re-check it in 1.5/1.3.6?

It can be working with set service dhcp-relay disable

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

Recheck and close it iff it was solved

The minimal configuration to reproduce:

set interfaces ethernet eth0 address '192.168.122.14/24'

The same behavior with VyOS 1.3-stable-202404080454
Work in VyOS 1.4-stable-202404080309

@greywolfe, let us know if you have tested it.

Reopen if you still have the issue.
Close the task as there is no response from the author. And we don't have reports like this.

@vfreex Can you re-check to see if everything works as you expected?

It is another bug, should be a separate bug report

I don't have any issues with your config, but my addresses (of course, I don't have all BGP VPN connections, etc.)

vyos@r4# set vrf name foo table 10101
[edit]
vyos@r4# commit
[edit]
vyos@r4# 
[edit]
vyos@r4# run show ver
Version:          VyOS 1.5-rolling-202404090019
Release train:    current

@d.shleg As I mentioned the config is not applied by FRR

r4# show run bgpd
Building configuration...

Could you try the latest rolling?

Your initial configuration and adding a new peer is not acceptable by FRR

vyos@r4# run show ver
Version:          VyOS 1.5-rolling-202404090019
Release train:    current

vyos@r4# compare 
[protocols bgp neighbor]
+ 10.177.75.2 {
+     peer-group "OVERLAY"
+     remote-as "64542"
+ }

Probably the same task https://vyos.dev/T6097

Mark it as resolved, reopen the task if required.