At least 2 CPUs should be for the system processes (Not VPP)
So the error looks handled correctly if you have 8 cores and are trying to use 7 cores.
So, max-number-cores - 2, you can use for VPP even if you isolate 7.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 6 2025
Sep 5 2025
Sep 4 2025
Needs the correction of the error message to be clearer.
It's already disallowed. Vpp is not started with proper error message
Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1
The calculation is okay for me: 1 socket, 2 cores. Threads or virtual cores will do more harm than good to performance. Should we disallow starting VPP on such instances?
Sep 3 2025
Sep 1 2025
Looks like a feature
What about option priority?
set container name c1 priority 1 set container name c2 priority 2
Aug 30 2025
@marvin, I think you can claim it
Aug 29 2025
Aug 28 2025
Aug 27 2025
The VyOS 1.3.x is EOL
for the newest versions fix here https://github.com/vyos/vyos-1x/pull/4663
Aug 26 2025
The similar task T6223
Aug 25 2025
interface {
inside vpptun10.144
outside vpptun10.145
}I have found an interesting project with EINat/fullcone NAT implementation https://github.com/EHfive/einat-ebpf
Use cases https://github.com/EHfive/einat-ebpf/blob/main/docs/guide/use-case.md
https://github.com/EHfive/einat-ebpf/blob/main/docs/reference/rfc-compliance.md
You can download a static binary to play with it.
Aug 23 2025
Aug 22 2025
Will be fixed after migration to the accel-ppp-ng T7744
Aug 21 2025
Will be fixed in the next rolling release.
Nice to re-check after 21 August