We use common-generic password which uses limits
We should change it here.
What number of symbols is better to make?

Needs testing, will be fixed in the next rolling release

@syncer not it doesn’t
JSON parser wasn’t back ported so other branches are not affected

I created a separated bug report https://vyos.dev/T6856

I'm going to close PR, https://github.com/vyos/vyos-build/pull/832#pullrequestreview-2420618828

@paulywog Can you check the latest rolling?

@SteveP Thanks!
I created a PR to exclude these rules https://github.com/vyos/vyos-build/pull/832

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

We use suricata only for the rolling
backport not required

@marekm, stop spamming in every message about LTS.
You know all the ways to get LTS images, including entirely free ones.
Thanks!

The vyos-vm-image is deprecated

@natali-rs1985, can we close this task if it is fixed?

@marekm It has to be solved in the upstrem, https://github.com/accel-ppp/accel-ppp
It cannot be fixed otherwise.

Just do not use bond in the flow
Use native ethernet interfaces

@syncer In my opinion, it is better to have a CLI that can process network interrupts only by the local NUMA node.
As I remember, the set system option performance xxx option overrides some sysctl options if it is not fixed.
Otherwise, we have to use customer scripts to balance interrupts on the required cores.

@syncer What I know only from XEN or XCP-NG was reported
Do no have reports from other platforms

It is not implemented
But it probably will not be implemented
The only affected service was SNMP

In T6545#204568, @ordex wrote:

Thanks for the pointer. I am even surprised that this worked with --cipher. In any case, I presume that template needs an exception.

The problem is that the template returns the none values in uppercase https://github.com/vyos/vyos-1x/blob/ba18d12f6863505133cde688d5e8188689af63bb/python/vyos/template.py#L567

In T2584#204474, @syncer wrote:

@Viacheslav do we want to do this?

PR https://github.com/vyos/vyos-build/pull/825

@SteveP could you attach those files for debugging where the issue exists?

/config/config.boot
/run/udev/log/vyos-net-name 
sudo journalctl -b | tee /tmp/journalct.log
sudo journalctl -k | tee /tmp/journalct-k.log

I’d prefer to drop it at all for now.
Until someone can investigate it more deeply.
I don’t have any idea what is wrong.
Thanks

@SteveP Can you try the latest rolling?

PR https://github.com/vyos/vyos-build/pull/823

related https://bugzilla.redhat.com/show_bug.cgi?id=2321325
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20241020124951.180350-1-pablo@netfilter.org/

The issue of breaking smoketest is not with iproute2

• Team upload
  • Revert "Drop legacy /usr/sbin/ip symlink", as many packages still depend on /sbin/ip or /usr/sbin/ip

The original driver will be included in the next rolling release

You can add PR for the documentation without a task

Probably related driver T6713

Should be fixed in the next rolling release

PR https://github.com/vyos/vyos-build/pull/816

@SteveP could you provide the link to the source code (git) for the official drivers?
Where we can clone the code and build correct package for Debian?

Bump Realtek driver version
PR https://github.com/vyos/vyos-build/pull/814

We use this https://github.com/vyos/vyos-build/blob/2359180068a653e39724a33b91bfa1ed395c1993/scripts/package-build/linux-kernel/build-realtek-r8152.py#L38

You can add PR a delete here https://github.com/vyos/vyos-build/blob/2359180068a653e39724a33b91bfa1ed395c1993/data/architectures/amd64.toml#L9
I think it is better to figure out what could be wrong

@jvandenbroek fell free to cereate a PR for fix.