If you need to temporarily resolve this issue, you can try increasing the number of all ethX (for example, starting the interface naming from eth100). I have a server with 8x E823-L ports and named them from eth101-eth108.

https://github.com/vyos/vyos-vpp-patches/pull/55

If you don't mind I can post a report from LLM. Although it's long, I think it did find the problem.

Hello, I finally use 2 patches to solve this:

diff --git a/src/plugins/linux-cp/lcp_interface_sync.c b/src/plugins/linux-cp/lcp_interface_sync.c
index ca7638e..61db256 100644
--- a/src/plugins/linux-cp/lcp_interface_sync.c
+++ b/src/plugins/linux-cp/lcp_interface_sync.c
@@ -363,7 +363,7 @@ lcp_itf_interface_add_del (vnet_main_t *vnm, u32 sw_if_index, u32 is_create)
   const vnet_sw_interface_t *sw;
   uword is_sub;

Hello, I found this is because the lcp_nl_resync operation is a potentially long-running full netlink synchronization, but the VyOS wrapper invokes it with the generic VPP PAPI response timeout of 5 seconds.

sorry, With VPP sFlow enabled but without set system sflow enable-egress, the generated hsflowd config will not contain psample { group=1 }. I cannot edit this task. I think I choose the wrong form type (I should create bug report, not task)

I just built a new image with the driver enabled, and it no longer causes kernel panic on my setup.

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

The problem is caused by inconsistent parameter ordering: in def kea_delete_lease(inet, ip_address, vrf_name=''): permalink the vrf_name is placed after ip_address, while in if not kea_delete_lease(inet, vrf, address): permalink the vrf appears before the address.

If one chooses not to copy config to new image, according to https://github.com/vyos/vyos-1x/blob/f46bd3ae7d225d67968397cf85887ae64160592a/src/op_mode/image_installer.py#L1105-L1108 , it won't copy default config to f'{target_config_dir}/config.boot' (This behavior is different from install_image, in which it copied the default config to f'{target_config_dir}/config.boot'). So get_cli_kernel_options cannot find the file and raise an error.

We can close it because it's similar to https://vyos.dev/T7708 and has now been fixed.

This appears to be a logical bug. I have opened a Pull Request to fix it.
https://github.com/vyos/vyos-1x/pull/4663

Should I close this task?

In T7394#222617, @curtdept wrote:

Still happening somewhere

{F14387702}

In T6258#184875, @Viacheslav wrote:

This sysctl option is deprecated

DEPRECATED PARAMETERS         top

       The base_reachable_time and retrans_time are deprecated.  The
       sysctl command does not allow changing values of these
       parameters.  Users who insist to use deprecated kernel interfaces
       should push values to /proc file system by other means.  For
       example:

       echo 256 > /proc/sys/net/ipv6/neigh/eth0/base_reachable_time

I propose to add new option under interface

set interfaces ethernet eth1 ip[v6] base-reachable-time xxx

Hi everyone, I think I found the simplest configuration that can reproduce this problem. If we set up firewall and use this command(set system sysctl parameter net.ipv6.neigh.eth3/2) in configuration at the same time, an error message will show when startup.
This is an example

set firewall
set interfaces ethernet eth0 address 'xxx.xxx.184.32/24'
set interfaces ethernet eth0 hw-id 'xx:xx:xx:xx:xx:50'
set interfaces ethernet eth1 hw-id 'xx:xx:xx:xx:xx:ba'
set interfaces ethernet eth1 vif 2
set interfaces loopback lo
set protocols static route xxx.xxx.0.0/0 next-hop xxx.xxx.184.1
set service ntp allow-client xxxxxx 'xxx.xxx.0.0/0'
set service ntp allow-client xxxxxx '::/0'
set service ntp server xxxxx.tld
set service ntp server xxxxx.tld
set service ntp server xxxxx.tld
set service ssh
set system config-management commit-revisions '100'
set system conntrack modules ftp
set system conntrack modules h323
set system conntrack modules nfs
set system conntrack modules pptp
set system conntrack modules sip
set system conntrack modules sqlnet
set system conntrack modules tftp
set system console device ttyS0 speed '115200'
set system host-name xxxxxx
set system login user xxxxxx authentication encrypted-password xxxxxx
set system sysctl parameter net.ipv6.neigh.eth1/2.base_reachable_time_ms value '14400000'
set system syslog global facility all level 'info'
set system syslog global facility local7 level 'debug'

If delete the first line (set firewall), system will start normally without error message.