So I guess this is very low priority for you guys, but it is very critical for me, so quick question, do you accept PR from general public? If yes, I might go ahead and take a look in how to get this done :)
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 7 2025
Mar 6 2025
It appears this is by design, FRR creates kernel routes with metric 20
vtysh show ip route, shows correct route
Is there anyone else we should tag on this ticket?
Mar 5 2025
Is resolved in VyOS 2025.03.05-0017-rolling.
I am running on VyOS 1.5-rolling-202503030030 , and this error has fixed
Mar 4 2025
In T7215#217255, @c-po wrote:Hi @MPStudyly,
can it be the case that your system you're running the test son already has a VRF named red?
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.
Should be fixed in https://vyos.dev/T7123
And/Or https://github.com/vyos/vyos-1x/commit/23477683cea2777f570ac0d98098aa2c6f041661
Can you try the latest rolling?
can it be the case that your system you're running the test son already has a VRF named red?
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.
@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