FRR changed this behavior several times https://github.com/FRRouting/frr/commit/322462920e2a2c8b73191c6eb5157d64cf4a593e
Sometimes it is disabled by default, sometimes enabled :)
So, depending on the FRR version, the behavior could be different.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 5 2025
Mar 4 2025
Should be fixed in https://vyos.dev/T7123
And/Or https://github.com/vyos/vyos-1x/commit/23477683cea2777f570ac0d98098aa2c6f041661
Can you try the latest rolling?
@treo Could you check the latest rolling to confirm if everything works as expected?
@daniel.arconada can you check this? The latest rolling has these modules.
vyos@vpp-left:~$ zcat /proc/config.gz | grep -i vdpa CONFIG_VIRTIO_VDPA=m CONFIG_VDPA=m # CONFIG_VDPA_USER is not set # CONFIG_MLX5_VDPA_NET is not set # CONFIG_MLX5_VDPA_STEERING_DEBUG is not set # CONFIG_VP_VDPA is not set # CONFIG_ALIBABA_ENI_VDPA is not set # CONFIG_SNET_VDPA is not set CONFIG_VHOST_VDPA=m vyos@vpp-left:~$ vyos@vpp-left:~$ show ver Version: VyOS 1.5-rolling-202503020018
Mar 3 2025
Not reproduced anymore
In T7213#217158, @freebsdjlu wrote:sorry , I thought the function should be "match mark 2 and use route table 200" , there is some misunderstanding , but if I only want route based on the mark ,not to change it , how to do it ?
vyos@r14# sudo nft list table ip vyos_mangle
table ip vyos_mangle {
chain VYOS_PBR_PREROUTING {
type filter hook prerouting priority mangle; policy accept;
iifname "eth1" counter packets 0 bytes 0 jump VYOS_PBR_UD_tproxy
}Add set of commands to reproduce.
Feb 28 2025
My proposed CLI was in https://github.com/vyos/vyos-vpp/pull/20
The question to @zsdc is why he doesn't like it...
I don't want to waste any more time on a feature that won't be accepted.
Was not accepted by maintainers
Close the task
Feb 27 2025
Reproduced again if start smoketests 17 times on VyOS 1.5-rolling-202502190007
Feb 27 16:50:13 r14 vyos-configd[794]: Received message: {"type": "node", "last": true, "data": "/usr/libexec/vyos/conf_mode/vpp.py"}
Feb 27 16:50:13 r14 vyos-configd[794]: "cpu main-core" is required but not set!
Feb 27 16:50:13 r14 vyos-configd[794]: Sending reply: ERROR_COMMIT with output
Feb 27 16:50:13 r14 vyos-configd[794]: scripts_called: ['vpp']
Feb 27 16:50:13 r14 systemd[1]: opt-vyatta-config-tmp-new_config_133953.mount: Deactivated successfully.
Feb 27 16:50:14 r14 vyos-configd[794]: Received message: {"type": "init"}
Feb 27 16:50:14 r14 vyos-configd[794]: config session pid is 133953
Feb 27 16:50:14 r14 vyos-configd[794]: config session sudo_user is vyos
Feb 27 16:50:14 r14 vyos-configd[794]: commit_scripts: ['vpp']
Feb 27 16:50:14 r14 vyos-configd[794]: Received message: {"type": "node", "last": true, "data": "/usr/libexec/vyos/conf_mode/vpp.py"}
Feb 27 16:50:14 r14 vyos-configd[794]: "cpu corelist-workers" and "cpu workers" cannot be used at the same
Feb 27 16:50:14 r14 vyos-configd[794]: time!
Feb 27 16:50:14 r14 vyos-configd[794]: Sending reply: ERROR_COMMIT with output
Feb 27 16:50:14 r14 vyos-configd[794]: scripts_called: ['vpp']
Feb 27 16:50:14 r14 systemd[1]: opt-vyatta-config-tmp-new_config_133953.mount: Deactivated successfully.
Feb 27 16:50:15 r14 vyos-configd[794]: Received message: {"type": "init"}
Feb 27 16:50:15 r14 vyos-configd[794]: config session pid is 133953
Feb 27 16:50:15 r14 vyos-configd[794]: config session sudo_user is vyos
Feb 27 16:50:15 r14 vyos-configd[794]: commit_scripts: ['vpp']
Feb 27 16:50:15 r14 vyos-configd[794]: Received message: {"type": "node", "last": true, "data": "/usr/libexec/vyos/conf_mode/vpp.py"}
Feb 27 16:50:15 r14 vyos-configd[794]: "cpu corelist-workers" is not correct
Feb 27 16:50:15 r14 vyos-configd[794]: Sending reply: ERROR_COMMIT with output
Feb 27 16:50:15 r14 vyos-configd[794]: scripts_called: ['vpp']
Feb 27 16:50:15 r14 systemd[1]: opt-vyatta-config-tmp-new_config_133953.mount: Deactivated successfully.
Feb 27 16:50:16 r14 vyos-configd[794]: Received message: {"type": "init"}
Feb 27 16:50:17 r14 vyos-configd[794]: config session pid is 133953
Feb 27 16:50:17 r14 vyos-configd[794]: config session sudo_user is vyos
Feb 27 16:50:17 r14 vyos-configd[794]: commit_scripts: ['vpp']
Feb 27 16:50:17 r14 vyos-configd[794]: Received message: {"type": "node", "last": true, "data": "/usr/libexec/vyos/conf_mode/vpp.py"}
Feb 27 16:50:17 r14 systemd[1]: Reloading.
Feb 27 16:50:17 r14 systemd[1]: Starting vpp.service - vector packet processing engine...
Feb 27 16:50:17 r14 systemd[1]: Started vpp.service - vector packet processing engine.
Feb 27 16:50:20 r14 vyos-configd[794]: ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 python3[794]: ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 python3[794]: CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 vyos-configd[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failed
Feb 27 16:50:20 r14 python3[794]: CRITICAL:VyOS StdErr:CRITICAL:VyOS StdErr:ERROR:root:select failedThe 1.3.x is mostly EOL.
We are not expecting any fixes here. Check config/firewall/so on
Consider updating to a more recent 1.4.x version.
Feb 26 2025
Feb 25 2025
At first glance, the problem could be with eth+ format
Feb 24 2025
Cannot reproduce it. It is necessary to get a configuration:
I tested this config and all works fine
VyOS 1.5-rolling-202502220006 + latest vyos-1x
set load-balancing haproxy backend bk01 server srv01 address '192.168.122.16' set load-balancing haproxy backend bk01 server srv01 check set load-balancing haproxy backend bk01 server srv01 port '8000' set load-balancing haproxy backend bk01 server srv02 address '192.168.122.16' set load-balancing haproxy backend bk01 server srv02 check set load-balancing haproxy backend bk01 server srv02 port '8888' set load-balancing haproxy service web backend 'bk01' set load-balancing haproxy service web port '80'
Feb 22 2025
PR https://github.com/vyos/vyos-1x/pull/4360
set load-balancing haproxy service web backend 'bk01' set load-balancing haproxy service web port '80' set load-balancing haproxy service web timeout client '600'
@treo Do you know is such timeout could be configurable for global-default/frontend/backend? I mean all the sections support them?
timeout client xx timeout connect xx timeout server xx timeout check xx
Mem_page_size test fails
vyos@r14:~$ /usr/libexec/vyos/tests/smoke/cli/test_vpp.py test_01_vpp_basic (__main__.TestVPP.test_01_vpp_basic) ... ok test_02_vpp_vxlan (__main__.TestVPP.test_02_vpp_vxlan) ... ok test_03_vpp_gre (__main__.TestVPP.test_03_vpp_gre) ... ok test_04_vpp_geneve (__main__.TestVPP.test_04_vpp_geneve) ... skipped 'Skipping this test geneve index always is 0' test_05_vpp_loopback (__main__.TestVPP.test_05_vpp_loopback) ... ok test_06_vpp_bonding (__main__.TestVPP.test_06_vpp_bonding) ... ok test_07_vpp_bridge (__main__.TestVPP.test_07_vpp_bridge) ... ok test_08_vpp_ipip (__main__.TestVPP.test_08_vpp_ipip) ... ok test_09_vpp_xconnect (__main__.TestVPP.test_09_vpp_xconnect) ... ok test_10_vpp_driver_options (__main__.TestVPP.test_10_vpp_driver_options) ... ok test_11_vpp_cpu_settings (__main__.TestVPP.test_11_vpp_cpu_settings) ... ok test_12_vpp_cpu_corelist_workers (__main__.TestVPP.test_12_vpp_cpu_corelist_workers) ... ok test_13_mem_page_size (__main__.TestVPP.test_13_mem_page_size) ... ERROR test_13_mem_page_size (__main__.TestVPP.test_13_mem_page_size) ... FAIL test_14_mem_default_hugepage (__main__.TestVPP.test_14_mem_default_hugepage) ... ok
One of the possible reasons is a lack of IP addresses (like source of the tunnels IP) on the VPP interface
Passed tests 5 times with IP address on eth1 successful
The latest test without an IP address on eth1 fails
Feb 20 2025
@daniel.arconada are you able to test it with the next rolling release? Those options will be included.
@daniel.arconada are you able to test it with the next rolling release? Those options will be included.
Feb 19 2025
Initial implementation PR https://github.com/vyos/vyos-vpp