$ sudo nft add element inet vrf_zones ct_somethingelse_map { "vni" : 100 } Error: syntax error, unexpected vni add element inet vrf_zones ct_somethingelse1_map { vni : 100 } ^^^
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 26 2025
Jun 25 2025
In T7432#227763, @yzguy wrote:@aalmenar I believe you would need to configure RPKI in the default VRF + your management VRF. They validate prefixes for their respective VRFs
I believe this is a limitation/intention of FRRouting not VyOS itselfhttps://docs.frrouting.org/en/latest/bgp.html#configuring-rpki-rtr-cache-servers
RPKI/RTR can be configured independently, either in configure node, or in vrf sub context. If configured in configure node, the core bgp instance of default vrf is impacted by the configuration. Each RPKI/RTR context is mapped to a vrf and can be made up of a specific list of cache-servers, and specific settings.
@aalmenar I believe you would need to configure RPKI in the default VRF + your management VRF. They validate prefixes for their respective VRFs
I believe this is a limitation/intention of FRRouting not VyOS itself
I have installed version:
In T7527#227294, @namtech wrote:As this is unfixed in VyOS 2025.06.17-0020-rolling. Is there a workaround that allows i.e to update container images without removing/adding the complete image/config?
Sorry to necro this thread, but wanted to chime in with a real world use-case.
Jun 24 2025
Confirmed fixed on 2025.06.24-0020-rolling
There is no reason to fix it in 1.4.4 because FRR10.2 will be implemented soon.
I can confirm the issue exists in what will become VyOS 1.4.3 as this is a bug in the FRR codebase itself and not the VyOS CLI configuration.
NAT44:
Adding exclude rule can fix the problem
CGNAT testing:
This is also available in FRR 9.1 used by VyOS 1.4 sagitta. We should add it there, too