Thanks for the contribution.

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

I think @Viacheslav is right here, I added the ethernet interfaces instead and now it works. I guess maybe add something that prevents adding bonds to flowtable, and instead directs the user to add the member interfaces?

@syncer I do not think this is worthwhile/advisable to backport changes for 1.3.x, given that there is an easy workaround.

Mechanism for adding kernel boot parameters in T5979/T5980

fixed in https://vyos.dev/T2180

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

This was supposed to be fixed in https://vyos.dev/T5794
We may need to double check once again

Looks like it is related to T5324

@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.

@Viacheslav, maybe we should just run the script on such platforms instead of doing CLI?

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