I think this feature must then be modified with:

no it's the PPPOE server configuration

Actualy is just exports TMOUT option per login

In T5364#153398, @troggie wrote:

In T5364#153397, @Viacheslav wrote:

I'm wondering about the syntax
Will it be enough?

set service pppoe-server pado-delay 0

I think we should include the sessions incase there multiple PPPOE services and people want to spread the load across multiple devices?
Or maybe an option to allow without sessions as well as allow with sessions - make the system versatile ?

Tested in the latest rolling release with both ipsec configured as tunnel and transport mode . As suggested in the above comment, with the correct close-action setting configured in both the initiator and responder side, then no duplicate child_sa are noticed.

In T5364#153397, @Viacheslav wrote:

I'm wondering about the syntax
Will it be enough?

set service pppoe-server pado-delay 0

I'm wondering about the syntax
Will it be enough?

set service pppoe-server pado-delay 0

Will be fixed in the next rolling release.

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

Oh ok.

In T5363#153177, @Apachez wrote:

I think this should be configured through a config option if bash-history should be retained or not (by default it shouldnt for regular users and equal to root).

It can for security reasons be argued that history should only exist in current session but when user logs out it should be removed.

This way in a multiuser environment one user cannot steal potential sensitive data from another user.

If security logging (what a particular user have done to the system when logged in) is needed this should be done remotely through syslog or similar.

Dear Viacheslav
Can I get compiled binary suitable for dell VEP4600 wich will retain the bash history.

I can confirm by removing the incorrect update-check url like so:

Ooh, I thought update-check should point to the iso-file like so:

Something wrong with this template https://github.com/vyos/vyos-1x/blob/d2540ac4c6fc05991b18cf0e2434fbb6d5f3c2cf/data/templates/lldp/vyos.conf.j2#L7

It should be configurable as an option but not by default.

It is not fully implemented.
You have to set the URL to a JSON file with System versions, which not exists for now (there is no permanent URL for it), so it will be in the future developments.

FRR does not support it
Allows only full multicast table

r11# clear ip 
...
  mroute       IP multicast routing table

Just want to jump onto the train and say that I too like the proposal of having "lo" as the main linux kernel loopback and loN as the networking loopback who is VRF-aware aswell.

https://github.com/vyos/vyos-1x/blob/d2540ac4c6fc05991b18cf0e2434fbb6d5f3c2cf/src/init/vyos-router#L327
https://github.com/vyos/vyos-1x/blob/d2540ac4c6fc05991b18cf0e2434fbb6d5f3c2cf/src/conf_mode/system-login.py#L392-L393

I have experienced this myself several years ago where "Green Ethernet" aka "Energy-Efficient Ethernet mode" was the cause that HPE Comware switches/routers had issues with cable based Apple devices.

This could be considred as duplicate task for: https://vyos.dev/T5116

@c-po thanks for compiled the kernel module and @spion06 for your contribution script , now we've DCO rolling releases starting on 1.4-rolling-202307190317

Changes on documentation don't need a task here.

Already fixed:
https://vyos.dev/T5340

Adding system image using custom vrf it's supported:

I think this should be configured through a config option if bash-history should be retained or not (by default it shouldnt for regular users and equal to root).

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

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

The issue is actual.
I reproduced it. SSH was accessible at this moment. And sftp server was accessible too.

FRR upstream accepted this patch. https://github.com/FRRouting/frr/pull/13140

I confirm that the problem persist, as of testing the version was 1.4-rolling-202307060317 but are extremely hard to reproduce, since the steps I describe only work sometime.

@bbabich moved efforts to vpp with linux control plane plugin
but I have plans to come back to xdp later

@c-po
I'm a bit late to the party...
"VOO is the dataplane of choice?"

Dear Team
Earlier Bash history was retained after restart.It is useful feature as any changes done are lost after restart. Need
help on restoring this functionality.
Regards,
Vishvas

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

Final testing before PR:
https://github.com/vyos/vyos1x-config/compare/master...jestabro:immutable

The following will be in the PR for T5317:
https://github.com/vyos/vyos1x-config/compare/master...jestabro:single-pass

Fixed with enabling offloads https://vyos.dev/T3619

vyos@r14# set interfaces ethernet eth0 offload 
Possible completions:
   gro                  Enable Generic Receive Offload
   gso                  Enable Generic Segmentation Offload
   lro                  Enable Large Receive Offload
   rfs                  Enable Receive Flow Steering
   rps                  Enable Receive Packet Steering
   sg                   Enable Scatter-Gather
   tso                  Enable TCP Segmentation Offloading