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

@tjjh89017 Have a look at https://vyos.dev/T5965

In T5619#177706, @ErnyTech wrote:

Unfortunately I haven't seen this before, for me this choice of using the out-of-tree driver is extremely wrong!

Most of the community's development is done on the mainline kernel driver (where among other things I'm working on sending patches to improve the ixgbe driver), if there are issues in the mainline driver they should be reported or resolved with a patch to be applied in vyos downstream and then send it to the Intel-wired-lan mailing list.

Please @samip537 can you tell me in a short list what exactly problems you encounter with the mainline Linux driver?

I hope a proper solution can be found as the current behavior of segfaulting the api server is a very unpleasant place to be while working on tooling for vyos.

Cf. the details leading to having changed this for config_op:
https://vyos.dev/T5305

I have create a pr with the required change to fix this issue if the problem described in T5305 is no longer a blocker.

@Viacheslav the problem was still solved in 1.4. (I don't know, when I will have the chance to test with 1.5.) The reason this issue exists is, that 1.4. was not declared to be stable back then. Now since 1.4 is official released as stable we can use 1.4 instead of 1.3. So I think we can close the issue.

I even have a router with it working:

On 1.4.0-epa1, there is no longer an indication that configuration file actually has been saved.

This is not a feature request, this has been working until made the detail available only when the lldpd service was running or not. It was even documented:

It is not the bug.
There is the feature request T6045

1.4 and 1.5 run on strongswan 5.9.11

@c-po I suggest that we should reopen this issue. And I have a question is why DHCP server with VRF support works correctly in v1.4 but not in v1.5？

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

I would say this would still be useful for c-states, and also for other things, for example setting hugepages, and If I remember right, the VPP addon also requires boot arguments be added.

Knob is now available starting 1.4.0-rc3 to disable spectre. Is this sufficient or you still have a usecase for cstates?

I'm using a workaround. I'm running a process in a script /config/scripts/vyos-postconfig-bootup.script:

In T4733#148990, @c-po wrote:

Hi @daniil and @NikolayP,

this is already implemented and working. You need to specify: set vrf bind-to-all and it will work out of the box with your configuration stated above

I have created a PR to resolve this issue: https://github.com/vyos/vyos-build/pull/511

In T4733#148990, @c-po wrote:

Hi @daniil and @NikolayP,

this is already implemented and working. You need to specify: set vrf bind-to-all and it will work out of the box with your configuration stated above

https://github.com/vyos/vyos-build/pull/509

This issue seem to be wider than just 1 occurance as I just stumbled into it again on the latest version (1.5-rolling-202402240021)

This example only contains the commands related to the bug, not for general setup.

@cnrd Provide please the "set" of the commands to reproduce.
This will make life much easier for developers.

Adding https://forum.vyos.io/t/quick-and-dirty-benchmark-of-cores-vs-mhz/13831/ for reference which also concludes that something is off with the commit and boot times of VyOS.

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

PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/3045