In T6258#184876, @canoziia wrote:

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

This sysctl option is deprecated

DEPRECATED PARAMETERS         top

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.

Meanwhile, trying to build 1.4 fails for a different reason - Debian 12 (bookworm) is still where it was, but sagitta-packages.vyos.net gives a 403 error:

So most likely we will have to find another implementation.

I sent a question to ISC regarding https://www.isc.org/blogs/dhcp-client-relay-eom/ and:

Reopen to investigate.

I tested in the latest rolling version and the traceback error is not received anymore and the tunnel ip column shows n/a but with multiple entries.
It still shows the disconnected client and I assume it should not show disconnected clients

Close it as wontfix due to legacy backend.

In some cases, we can't predict the interface name (if the interface name is over 15 characters) https://vyos.dev/T6222

@sempervictus Any updates or additional context?

Fixed, VyOS 1.5-rolling-202404240023

vyos@r4# run show conf com | match "bri|tun0"
set interfaces bridge br0 member interface tun0
set interfaces tunnel tun0 encapsulation 'gretap'
set interfaces tunnel tun0 remote '192.168.122.111'
set interfaces tunnel tun0 source-address '192.168.122.14'
[edit]
vyos@r4# delete interfaces tunnel 
[edit]
vyos@r4# commit
[ interfaces tunnel tun0 ]
Interface "tun0" cannot be deleted as it is a member of bridge "br0"!

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

Not actual for 1.5/1.4
@mrlocke Can you re-check the 1.3?

@doctorpangloss Any updates?

@modzilla99 Could you provide an example of set commands to reproduce?

Tested as working in: VyOS 1.5-rolling-202404230019

In T6258#184716, @Viacheslav wrote:

Most likely needs to change priority to 319 for the sysctl

vyos@r4:~$ /usr/libexec/vyos/priority.py | match "ethernet|sysctl"
       300  interfaces_virtual-ethernet.py      ['interfaces', 'virtual-ethernet']
       318  interfaces_ethernet.py              ['interfaces', 'ethernet']
       318  system_sysctl.py                    ['system', 'sysctl']
       321  interfaces_pseudo-ethernet.py       ['interfaces', 'pseudo-ethernet']
vyos@r4:~$

What happens if another value occupies the index?
For example, PPPoE-server and PPP interface can generate thousands of interfaces

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

It was filtered in https://vyos.dev/T2086 to avoid pam_unix mess

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

Can't reproduce it, close the task

Most likely needs to change priority to 319 for the sysctl

vyos@r4:~$ /usr/libexec/vyos/priority.py | match "ethernet|sysctl"
       300  interfaces_virtual-ethernet.py      ['interfaces', 'virtual-ethernet']
       318  interfaces_ethernet.py              ['interfaces', 'ethernet']
       318  system_sysctl.py                    ['system', 'sysctl']
       321  interfaces_pseudo-ethernet.py       ['interfaces', 'pseudo-ethernet']
vyos@r4:~$

I have asked the OP @canoziia to provide such in the forum.

Extend to <1-65535>
PR https://github.com/vyos/vyos-1x/pull/3353

What do I need to do to get these values?

root@r1-right:/home/vyos# sysctl net.ipv6.neigh.eth3/2.base_reachable_time_ms
sysctl: cannot stat /proc/sys/net/ipv6/neigh/eth3.2/base_reachable_time_ms: No such file or directory

I can only refer to whats unfolded on the forum at https://forum.vyos.io/t/how-to-set-net-ipv6-neigh-etha-b-base-reachable-time-in-vyos/14304

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

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

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

@Viacheslav or another of the Maintainers:

Could you provide the full set of commands to reproduce?

So the root cause here is that vrf.py runs prior to vrf_vni.py where the first one eliminates all vni configuration within FRR.
The main reason for this weird logic is T5492.