PR https://github.com/vyos/vyos-vpp-patches/pull/31

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

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

PR to re-add all static IPv4 addresses configured on interface.
https://github.com/vyos/vyos-1x/pull/4968

The issue with MTU and is specific to ARM systems. It was reproduced on Oracle Cloud using the vyos-20260116102901-rolling-oracle-cloud-arm64 image.
After upgrading to the latest rolling ARM image, the MTU is configured correctly and DHCP works as expected.

PR is ready for review: https://github.com/vyos/vyos-documentation/pull/1756

PR for vyos1x-config:
https://github.com/vyos/vyos1x-config/pull/65

Advice for people wanting to use this is to run it inside a container.

I don't see any compelling reason to replace it.

Update February 3rd, 2026
I noticed that this config path DOES exist, but is also not documented in VyOS!

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

@Viacheslav any preference on which syntax?

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

ARM supported
Feel free to add new tasks if necessary.

I'm always interested in new software suggestions — I didn't know about this project!

@a.pidnebesny thanks for testing

Tested on VyOS 1.4.4, 1.5 and Latest Rolling release.

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

Tested on VyOS 2026.01.28-0022-rolling.

I think it should be:

It seems to be possible to configure the required MACVLAN / pseudo-ethernet interface on the bridge (despite not offered by the autocompletion):

pseudo-ethernet peth1 {
    address 10.255.11.1/24
    description "Anycast Gateway for VNI 1001"
    mac f6:54:73:26:5e:1f
    source-interface br1.1001
}

@cellulosa, any idea for CLI?

aws instance with vpp enabled successfully receives ipv6 address from aws dhcpv6

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

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

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

*Edited to remove an "option" I don't have a way to code.

I need to double check, but could this part:

Ideally some example of config that could be reproduced by developers
It is unknown bug and I do not see someone else affected it.
As I see at least policy

In T6740#248635, @Viacheslav wrote:

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

Any specific part?
I want to avoid to share full config.

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

This way, it is simple to handle native nft commands with custom tables, then use them in the VyOS CLI.
I'm not expecting this feature to be implemented in the suggested format.