can it be the case that your system you're running the test son already has a VRF named red?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 4 2025
Hello! Any news regarding this issue?
Just to add to the argument: Using the build_type to determine if the banner gets shown or not would allow individual/custom builds to have it disabled as well (we know what we are doing). Obviously I can just speak for my use case, where we roll our own builds to get back qemu-guest-agent. I can't tell if this would go against the intention of introducing this banner in the first place.
In T7206#216891, @danielr1996 wrote:I tried adding
[[includes_chroot]] path = "opt/vyatta/etc/config/config.boot" data = ""to the build flavor, and now it seems to work.
I still get warning in the cloud init log, but so far I haven't noticed anything not working. This works as a workaround for me, but I still think that this is a bug.
@treo Could you check the latest rolling to confirm if everything works as expected?
With T6641 implemented and a discussion with @jestabro and @dmbaturin this would be a perfect addition.
Mar 3 2025
I don't think the original work around would work with Kea becuase how the Jinja is formatted, but expanding on this for Kea specifically, a couple of things that would need to be implemented would be client classes that match have some type of match
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 ?
btw , could we add a feature to support tproxy when do pbr ?
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
}set policy route tproxy rule 100 mark '2'
set policy route tproxy rule 100 set table '200'
Add set of commands to reproduce.
Mar 2 2025
Ran across this when trying to get a DHCP relay when doing EVPN, also on an Arista platform
Can confim the configuration carried over with vyos-1.5-rolling-202503020018. I need to test things further but at first glance things look good.
@Apachez could you please assign this task to me?
Tested as working in: VyOS 1.5-rolling-202503020031
Mar 1 2025
This has been implemented in VyOS rolling already as part of T6989.
It will be backported to VyOS 1.5
Feb 28 2025
@sarthurdev I think, conntract should be transferred from input or forward to the global section or used in prerouting. Because now it looks like conntrack is used only in these rules, not for all traffic.
I think this should be considered expected behaviour, during the several iterations of the firewall (including Vyatta era - without explicit tables and chains) we've not changed the logic of enabling conntrack.
I did more tests. If I create any rule called conntrack (in input, forward, with different conditions), Conntrack affects all traffic that passes through or to the router.
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.
Care to elaborate on why this was denied?
Was not accepted by maintainers
Close the task
I tried adding
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 failedNothing to thank me for @HollyGurza, you're the one who fixed it! :) After all, it seems I got the issue wrong anyway. ^^"
Thank you @MPStudyly
Feb 26 2025
I did not have a deeper look yet, but as some tests related to hugepages are failing, I assume they'd need to be enabled on the host running the tests and Docker should be allowed to make use of them as well? About the latter I'm unsure as a VM is spun up to perform the tests, so Docker might be irrelevant to this.