Page MenuHomeVyOS Platform

VPP: DHCP client on an interface breaks its configuration
Closed, ResolvedPublicBUG

Description

Note

This seems to be unique to Mellanox interfaces only, or a combo with Mellanox + VF. Host where it is reproducible has: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function [15b3:101e].
The issue cannot be reproduced on the same VM type deployed with VirtIO NIC.

Summary

When a DHCP client is configured on an interface, the settings for this interface are not applied at all.

How to reproduce

The configuration is:

set interfaces ethernet eth0 address 'dhcp'
set interfaces ethernet eth0 address '172.20.17.91/25'
set interfaces ethernet eth0 mtu '1500'
set protocols static route 0.0.0.0/0 next-hop 172.20.17.1
set service ssh client-keepalive-interval '180'
set service ssh port '22'
set system console device ttyAMA0
set system name-server '1.1.1.1'
set system option kernel cpu disable-nmi-watchdog
set system option kernel cpu isolate-cpus '2-3'
set system option kernel cpu nohz-full '2-3'
set system option kernel cpu rcu-no-cbs '2-3'
set system option kernel disable-hpet
set system option kernel disable-mce
set system option kernel disable-mitigations
set system option kernel disable-softlockup
set system option kernel memory hugepage-size 2M hugepage-count '1024'
set system option reboot-on-upgrade-failure '5'
set system syslog local facility all level 'info'
set system syslog local facility local7 level 'debug'
set vpp settings cpu corelist-workers '3'
set vpp settings cpu main-core '2'
set vpp settings interface eth0 driver 'dpdk'
set vpp settings memory main-heap-size '1G'
set vpp settings unix poll-sleep-usec '1000'

If a system is booted with this config, the whole process seems to look fine (no errors, warnings, etc.), and the interface itself is fully operable. But the actual config is not applied:

vyos@instance-20260116-1337:~$ show configuration commands | grep eth0
set interfaces ethernet eth0 address 'dhcp'
set interfaces ethernet eth0 address '172.20.17.91/25'
set interfaces ethernet eth0 hw-id '02:00:17:23:64:17'
set interfaces ethernet eth0 mtu '1500'
set vpp settings interface eth0 driver 'dpdk'
vyos@instance-20260116-1337:~$ show interfaces 
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address    MAC                VRF        MTU  S/L    Description
-----------  ------------  -----------------  -------  -----  -----  -------------
eth0         -             02:00:17:23:64:17  default   9000  u/u
lo           127.0.0.1/8   00:00:00:00:00:00  default  65536  u/u
             ::1/128
vyos@instance-20260116-1337:~$ show vpp interfaces 
Kernel    Dataplane    Type    IP Address    MAC                  MTU  State
--------  -----------  ------  ------------  -----------------  -----  -------
          eth0         dpdk                  02:00:17:23:64:17   9000  up
          local0       local                 00:00:00:00:00:00      0  down
eth0      tap4096      virtio                02:fe:03:30:c3:ab   1500  up

Details

Version
20260116102901-rolling (arm64 build)
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

natali-rs1985 changed the task status from Open to In progress.Jan 19 2026, 10:16 AM
natali-rs1985 claimed this task.
natali-rs1985 triaged this task as Normal priority.
natali-rs1985 changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.

@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


set interfaces ethernet eth3 address 'dhcp'
set interfaces ethernet eth3 address '172.20.17.91/25'
set interfaces ethernet eth3 hw-id '10:70:fd:56:22:1d'
set interfaces ethernet eth3 mtu '1500'
set vpp settings interface eth3 driver 'dpdk'
commit

vyos@he-r650-01# run show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address       MAC                VRF        MTU  S/L    Description
-----------  ---------------  -----------------  -------  -----  -----  -------------
eth0         10.217.32.76/24  b0:7b:25:f8:44:2a  default   1500  u/u
eth1         -                b0:7b:25:f8:44:2b  default   1500  u/D
eth2         -                10:70:fd:56:22:1c  default   1500  u/u
eth3         172.20.17.91/25  10:70:fd:56:22:1d  default   1500  u/u
eth4         -                6c:fe:54:6b:4b:d8  default   1500  u/u
eth5         -                6c:fe:54:6b:4b:d9  default   1500  u/u
lo           127.0.0.1/8      00:00:00:00:00:00  default  65536  u/u
             ::1/128
[edit]
vyos@he-r650-01# run show vpp interfaces
Kernel    Dataplane    Type    IP Address       MAC                  MTU  State
--------  -----------  ------  ---------------  -----------------  -----  -------
          eth3         dpdk    172.20.17.91/25  10:70:fd:56:22:1d   1500  up
          local0       local                    00:00:00:00:00:00      0  down
eth3      tap4096      virtio                   02:fe:4c:b3:b1:63   1500  up
[edit]

vyos@he-r650-01:~$ uname -m
x86_64

This also is not reproduced after reboot.

vyos@he-r650-01:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address       MAC                VRF        MTU  S/L    Description
-----------  ---------------  -----------------  -------  -----  -----  -------------
eth0         10.217.32.76/24  b0:7b:25:f8:44:2a  default   1500  u/u
eth1         -                b0:7b:25:f8:44:2b  default   1500  u/D
eth2         -                10:70:fd:56:22:1c  default   1500  u/u
eth3         172.20.17.91/25  10:70:fd:56:22:1d  default   1500  u/u
eth4         -                6c:fe:54:6b:4b:d8  default   1500  u/u
eth5         -                6c:fe:54:6b:4b:d9  default   1500  u/u
lo           127.0.0.1/8      00:00:00:00:00:00  default  65536  u/u
             ::1/128
vyos@he-r650-01:~$ show vpp interfaces
Kernel    Dataplane    Type    IP Address       MAC                  MTU  State
--------  -----------  ------  ---------------  -----------------  -----  -------
          eth3         dpdk    172.20.17.91/25  10:70:fd:56:22:1d   1500  up
          local0       local                    00:00:00:00:00:00      0  down
eth3      tap4096      virtio                   02:fe:4e:dd:93:b8   1500  up
vyos@he-r650-01:~$ ethtool -i defunct_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

This issue could be specific only to ARM architecture.

This is good - the problem seems more isolated now.

There are still two major differences between the test scenarios:

  • Physical NIC vs. VF
  • x86_64 vs. aarch64

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.

However, statically configured IP addresses are not applied, regardless of the VPP configuration.
When dhclient restarts, it flushes all IPv4 addresses on the interface, but the static addresses are not re-added.

Welcome to VyOS!
   ┌── ┐
   . VyOS rolling-20260203103401
   └ ──┘  current
 * Documentation:  https://docs.vyos.io/en/latest
 * Project news:   https://blog.vyos.io
 * Bug reports:    https://vyos.dev
You can change this banner using "set system login banner post-login" command.
VyOS is a free software distribution that includes multiple components,
you can check individual component licenses under /usr/share/doc/*/copyright
Last login: Thu Jun 26 15:00:26 2025 from 85.114.199.30
vyos@instance-20260203-1330:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address      MAC                VRF        MTU  S/L    Description
-----------  --------------  -----------------  -------  -----  -----  -------------
eth0         172.18.1.95/24  02:00:17:0f:0b:56  default   1500  u/u
lo           127.0.0.1/8     00:00:00:00:00:00  default  65536  u/u
             ::1/128
vyos@instance-20260203-1330:~$ show vpp interfaces
Kernel    Dataplane    Type    IP Address      MAC                  MTU  State
--------  -----------  ------  --------------  -----------------  -----  -------
          eth0         dpdk    172.18.1.95/24  02:00:17:0f:0b:56   1500  up
          local0       local                   00:00:00:00:00:00      0  down
eth0      tap4096      virtio                  02:fe:a7:97:8d:bc   1500  up
vyos@instance-20260203-1330:~$ show conf comm | grep eth0
set interfaces ethernet eth0 address 'dhcp'
set interfaces ethernet eth0 address '172.18.0.223/24'
set interfaces ethernet eth0 hw-id '02:00:17:0f:0b:56'
set interfaces ethernet eth0 mtu '1500'
set vpp settings interface eth0

logs

Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Passing command to /usr/sbin/ip: "-4 addr flush dev eth0 label eth0"
Jun 26 14:59:10 instance-20260203-1330 vpp[1930]: linux-cp/router: Failed to delete neighbor: 172.18.1.1 eth0
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Deleting search domains with tag "dhcp-eth0" via vyos-hostsd-client
Jun 26 14:59:10 instance-20260203-1330 staticd[1675]: route_notify_owner: Route 0.0.0.0/0 failed to install for table: 254
Jun 26 14:59:10 instance-20260203-1330 staticd[1675]: route_notify_owner: Route 0.0.0.0/0 failed to install for table: 254
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"type": "search_domains", "op": "delete", "data": ["dhcp-eth0"]}
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': None}
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Deleting nameservers with tag "dhcp-eth0" via vyos-hostsd-client
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"type": "name_servers", "op": "delete", "data": ["dhcp-eth0"]}
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': None}
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Deleting default route: via 172.18.1.1 dev eth0 metric 210
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: FRR status: running
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Checking if the route presented in kernel: default via 172.18.1.1 dev eth0 metric 210
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Converted vtysh command: "no ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Sending command to vtysh
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Command was executed successfully via vtysh: "no ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: FRR status: running
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Checking if the route presented in kernel: 0.0.0.0/0 via 172.18.1.1 dev eth0
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Converted vtysh command: "no ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Sending command to vtysh
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Command was executed successfully via vtysh: "no ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: FRR status: running
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Checking if the route presented in kernel: 169.254.0.0/16 dev eth0
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Converted vtysh command: "no ip route 169.254.0.0/16  eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Sending command to vtysh
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Command was executed successfully via vtysh: "no ip route 169.254.0.0/16  eth0 tag 210 210 "
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2723]: Applying changes via vyos-hostsd-client
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"op": "apply"}
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Applying 2 changes
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Writing /etc/resolv.conf
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Writing /etc/hosts
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Writing /run/pdns-recursor/recursor.vyos-hostsd.conf.lua
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Writing /run/pdns-recursor/recursor.forward-zones.conf
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: pdns_recursor not running, not sending "reload-lua-config"
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: pdns_recursor not running, not sending "reload-zones"
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Success
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:10 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': {'message': 'Applied 2 changes'}}
Jun 26 14:59:10 instance-20260203-1330 systemd[1]: dhclient@eth0.service: Deactivated successfully.
Jun 26 14:59:10 instance-20260203-1330 systemd[1]: Stopped DHCP client on eth0.
Jun 26 14:59:10 instance-20260203-1330 systemd[1]: dhclient@eth0.service: Consumed 2.903s CPU time.
Jun 26 14:59:10 instance-20260203-1330 systemd[1]: Starting DHCP client on eth0...
Jun 26 14:59:10 instance-20260203-1330 systemd[1]: Started DHCP client on eth0.
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: Internet Systems Consortium DHCP Client 4.4.3-P1
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: Copyright 2004-2022 Internet Systems Consortium.
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: All rights reserved.
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: Copyright 2004-2022 Internet Systems Consortium.
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: All rights reserved.
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:59:10 instance-20260203-1330 dhclient[2851]:
Jun 26 14:59:10 instance-20260203-1330 dhclient-script-vyos[2853]: Current dhclient PID: 2851, Parent PID: 1, IP version: 4, All dhclients for interface eth0: 2851
Jun 26 14:59:10 instance-20260203-1330 netplugd[2713]: eth0: state INNING pid 2714 exited status 0
Jun 26 14:59:11 instance-20260203-1330 dhclient-script-vyos[2853]: Passing command to /usr/sbin/ip: "link set dev eth0 up"
Jun 26 14:59:11 instance-20260203-1330 dhclient-script-vyos[2853]: No changes to apply via vyos-hostsd-client
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Listening on LPF/eth0/02:00:17:0f:0b:56
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Listening on LPF/eth0/02:00:17:0f:0b:56
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Sending on   LPF/eth0/02:00:17:0f:0b:56
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Sending on   Socket/fallback
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Sending on   LPF/eth0/02:00:17:0f:0b:56
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: Sending on   Socket/fallback
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPOFFER of 172.18.1.95 from 169.254.169.254
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPOFFER of 172.18.1.95 from 169.254.169.254
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPREQUEST for 172.18.1.95 on eth0 to 255.255.255.255 port 67
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPREQUEST for 172.18.1.95 on eth0 to 255.255.255.255 port 67
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPACK of 172.18.1.95 from 169.254.169.254
Jun 26 14:59:11 instance-20260203-1330 dhclient[2851]: DHCPACK of 172.18.1.95 from 169.254.169.254
Jun 26 14:59:11 instance-20260203-1330 dhclient-script-vyos[2885]: Current dhclient PID: 2851, Parent PID: 1, IP version: 4, All dhclients for interface eth0: 2851
Jun 26 14:59:11 instance-20260203-1330 dhclient-script-vyos[2885]: Replacing MTU value for eth0 with preconfigured one: 1500
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Passing command to /usr/sbin/ip: "-4 addr add 172.18.1.95/255.255.255.0 broadcast 172.18.1.255 valid_lft 86400 preferred_lft 86400 dev eth0 label eth0"
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Passing command to /usr/sbin/ip: "link set dev eth0 mtu 1500"
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Deleting nameservers with tag "dhcp-eth0" via vyos-hostsd-client
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"type": "name_servers", "op": "delete", "data": ["dhcp-eth0"]}
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': None}
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Adding nameservers "169.254.169.254" with tag "dhcp-eth0" via vyos-hostsd-client
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"type": "name_servers", "op": "add", "data": {"dhcp-eth0": ["169.254.169.254"]}}
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': None}
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Applying changes via vyos-hostsd-client
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Request data: {"op": "apply"}
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Applying 2 changes
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Writing /etc/resolv.conf
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Writing /etc/hosts
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Writing /run/pdns-recursor/recursor.vyos-hostsd.conf.lua
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Writing /run/pdns-recursor/recursor.forward-zones.conf
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: pdns_recursor not running, not sending "reload-lua-config"
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: pdns_recursor not running, not sending "reload-zones"
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Success
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Jun 26 14:59:12 instance-20260203-1330 vyos-hostsd[1144]: Sent response: {'data': {'message': 'Applied 2 changes'}}
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: No changes to apply via vyos-hostsd-client
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: FRR status: running
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Checking if the route presented in kernel: 0.0.0.0/0 via 172.18.1.1 dev eth0
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Converted vtysh command: "ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Sending command to vtysh
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Command was executed successfully via vtysh: "ip route 0.0.0.0/0 172.18.1.1 eth0 tag 210 210 "
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: FRR status: running
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Checking if the route presented in kernel: 169.254.0.0/16 dev eth0
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Converted vtysh command: "ip route 169.254.0.0/16  eth0 tag 210 210 "
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Sending command to vtysh
Jun 26 14:59:12 instance-20260203-1330 dhclient-script-vyos[2885]: Command was executed successfully via vtysh: "ip route 169.254.0.0/16  eth0 tag 210 210 "
Jun 26 14:59:12 instance-20260203-1330 dhclient[2851]: bound to 172.18.1.95 -- renewal in 41834 seconds.
Jun 26 14:59:12 instance-20260203-1330 dhclient[2851]: bound to 172.18.1.95 -- renewal in 41834 seconds.
Jun 26 14:59:14 instance-20260203-1330 kernel: perf: interrupt took too long (8817 > 8796), lowering kernel.perf_event_max_sample_rate to 22000
Jun 26 14:59:25 instance-20260203-1330 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jun 26 14:59:25 instance-20260203-1330 kernel: perf: interrupt took too long (11045 > 11021), lowering kernel.perf_event_max_sample_rate to 18000
Jun 26 14:59:36 instance-20260203-1330 systemd[1]: systemd-localed.service: Deactivated successfully.
Jun 26 14:59:39 instance-20260203-1330 sshd[3000]: Accepted publickey for vyos from 85.114.199.30 port 46022 ssh2: RSA SHA256:rN+9JaI8jbA1/v6yWKFxbVvkftnjHmIu8Ni+b1C/zHU
Jun 26 14:59:39 instance-20260203-1330 sshd[3000]: pam_unix(sshd:session): session opened for user vyos(uid=1002) by (uid=0)
Jun 26 14:59:39 instance-20260203-1330 systemd-logind[1142]: New session 1 of user vyos.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Created slice User Slice of UID 1002.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Starting User Runtime Directory /run/user/1002...
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Finished User Runtime Directory /run/user/1002.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Starting User Manager for UID 1002...
Jun 26 14:59:39 instance-20260203-1330 (systemd)[3003]: pam_unix(systemd-user:session): session opened for user vyos(uid=1002) by (uid=0)
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Queued start job for default target default.target.
Jun 26 14:59:39 instance-20260203-1330 systemd-journald[850]: File /var/log/journal/5a72a0622d9a4762a633a77f511b1477/user-1002.journal corrupted or uncleanly shut down, renaming and replacing.
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Reached target paths.target - Paths.
Jun 26 14:59:39 instance-20260203-1330 rsyslogd[2146]: imjournal: journal files changed, reloading...  [v8.2302.0 try https://www.rsyslog.com/e/0 ]
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Reached target sockets.target - Sockets.
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Reached target timers.target - Timers.
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Reached target basic.target - Basic System.
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Reached target default.target - Main User Target.
Jun 26 14:59:39 instance-20260203-1330 systemd[3003]: Startup finished in 142ms.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Started User Manager for UID 1002.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: Started Session 1 of User vyos.
Jun 26 14:59:39 instance-20260203-1330 systemd[1]: opt-vyatta-config-tmp-new_config_3026.mount: Deactivated successfully.
Jun 26 14:59:39 instance-20260203-1330 sshd[3000]: pam_env(sshd:session): deprecated reading of user environment enabled
Jun 26 15:00:13 instance-20260203-1330 systemd[1]: Starting Rotate log files...
Jun 26 15:00:13 instance-20260203-1330 systemd[1]: logrotate.service: Deactivated successfully.
Jun 26 15:00:13 instance-20260203-1330 systemd[1]: Finished Rotate log files.
Jun 26 15:00:23 instance-20260203-1330 kernel: perf: interrupt took too long (13808 > 13806), lowering kernel.perf_event_max_sample_rate to 14000

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

For my tests this does not look like to be VPP related.

set interfaces ethernet eth0 vif 10 address 172.16.33.201/24
commit

vyos@vyos# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address         MAC                VRF        MTU  S/L    Description 
-----------  -----------------  -----------------  -------  -----  -----  -------------
eth0         -                  00:50:56:bf:c5:6d  default   1500  u/u 
eth0.10      172.16.33.201/24   00:50:56:bf:c5:6d  default   1500  u/u

Now also add DHCP to eth0.10

set interfaces ethernet eth0 vif 10 address dhcp
commit

vyos@vyos# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address         MAC                VRF        MTU  S/L    Description
-----------  -----------------  -----------------  -------  -----  -----  -------------
eth0         -                  00:50:56:bf:c5:6d  default   1500  u/u
eth0.10      172.16.33.201/24   00:50:56:bf:c5:6d  default   1500  u/u
             172.16.33.130/24

Now renew the DHCP lease on the interface - the static IP address will get lost

vyos@vyos# run renew dhcp interface eth0.10
Restarting DHCP client on interface eth0.10...

vyos@vyos# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address         MAC                VRF        MTU  S/L    Description
-----------  -----------------  -----------------  -------  -----  -----  -------------
eth0         -                  00:50:56:bf:c5:6d  default   1500  u/u
eth0.10      172.16.33.130/24   00:50:56:bf:c5:6d  default   1500  u/u
natali-rs1985 moved this task from Need Triage to Completed on the VyOS Rolling board.