- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 23 2025
Looks good to me. I've added it to the documentation in https://github.com/vyos/vyos-documentation/pull/1599
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'
According to the documentation the timeouts are supported like that:
timeout client: defaults, frontend, listen
timeout connect: defaults, listen, backend
timeout server: defaults, listen, backend
timeout check: defaults, listen, backend
@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 21 2025
@talmakion I think it good idea is removed , this attribute was added by cisco in the early day of internet, as you mentioned , it can be solved using 0:0 in a RM.
Can't reproduce the issue
Looks like this was deprecated in FRR a while ago: https://github.com/FRRouting/frr/commit/81a57d81812115bdbab25168e86e509e2db607a1
Has this one been resolved by adding named VRF targeting?
Feb 20 2025
I will look into after https://github.com/vyos/vyos.vyos/pull/387
I can look into this after https://github.com/vyos/vyos.vyos/pull/387 is actioned
It looks like the problem is in this `key_mangling', it's probably that function where these kind of errors are given:
I've extend the test in the enviorment , it looks like there is a problem with names in our policies : eg , where it brokes the configuration :
@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
Tested as working in: VyOS 1.5-rolling-202502190007
Closing this, new tasks can be opened for any issues found in new WLB.