@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

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

I can verify @samip537's comments -- the X553 interface won't establish link state using the default ixgbe driver included in Linux kernel 6.1 or 6.6. In my case, I'm testing hardware with X553 interfaces against a Dell PowerConnect 8132F. Qualified/Non-Qualified modules or DAC-cables make no difference. Using the OOT Intel driver, however, does work as one would expect.

recently mentioned on netdev (upstream bugs and other threads linked as well):

The issue is raised in this forum query: https://forum.vyos.io/t/commit-archive-doesnt-accept-symbols-in-password/13817
Remote host having password with special character is not accepted using with scp command

@ErnyTech This has been discussed at the forums in length what the problems are, but most of them seem to come from an link-related commit in the in-tree driver: https://marc.info/?l=linux-netdev&m=170113799914642. Meaning that no matter what one does, with the built-in driver, one cannot establish a link between X533 and eg. Juniper switch but they do see each other according to transceiver information but just no link.

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

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