- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 8 2025
Jul 7 2025
Jul 6 2025
It’s completely doesn’t work even with PBRD https://github.com/FRRouting/frr/issues/3160 (I didn’t check)
Jul 4 2025
Jul 2 2025
Confirmed working on 2025.07.01-0813-rolling, interfaces no longer appears in ra-interfaces after setting and resetting BGP
Jul 1 2025
it has been fixed about month or two ago, but still there is a problem with updated links and/or certificates.
This is still a problem. Is anyone looking into this?
Forgot to circle back on this. But it does work.
Jun 30 2025
Jun 28 2025
Jun 27 2025
The case is very rare
Jun 26 2025
@991jo As far as I can tell, the documentation for both VyOS and FRR are simply correct - both bgp as-path access-list and show bgp ipvX regex render AS paths as text and run a POSIX regular expression against them. There's no range expansion or other fanciness beyond special handling of the '_' match - just a space-separated text string of ASNs vs a regexec()'d pattern.
$ 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 } ^^^
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:
Jun 24 2025
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.
This is also available in FRR 9.1 used by VyOS 1.4 sagitta. We should add it there, too
Jun 23 2025
Jun 22 2025
We need to revisit this, ixgbe, i40e is updated in 6.15
Jun 19 2025
Jun 18 2025
As 1.3.x allowed for an ip address as value of
Jun 17 2025
Jun 16 2025
Jun 13 2025
Jun 12 2025
Jun 11 2025
Jun 10 2025
Jun 8 2025
Jun 7 2025
HI ,
I tested it . it works well. Could you please merge it into stable version vyos 1.4 ? Many thanks!