Hi! I think I am hitting a similar/the same bug with a very minimal configuration.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 26 2025
Jul 25 2025
Jul 24 2025
Jul 23 2025
Jul 22 2025
Tried to fix here: https://github.com/vyos/vyos-1x/pull/4616
Jul 21 2025
Fixed in FRR master: https://github.com/FRRouting/frr/pull/17544
Jul 20 2025
this is already supported by FRR and already used by VyOS, but not in this behavior. If you create an 2nd VRF and use dynamic routing protocols, you create in frr multiple processes of that routing protocol you use. OSPF and BGP in frr support multiple processes out of the box.
Jul 19 2025
Does it supported by FRR?
Jul 17 2025
Jul 16 2025
Jul 15 2025
Sorry, wasn't on regular computer when I filed. Just wanted to get it put in.
@giga1699, Can you add steps or a set/seq of commands to reproduce?
Jul 14 2025
@SrividyaA 1.5 and 1.4 use completely different DHCP server implementations so this task cannot possibly be relevant for both (even if they have a similar-looking issue, it will need completely different fixes).
We need a precise spec for it, what's required to support it. We also need a testing environment. I do think it would be nice to support it, but I wonder if it would bring many new customers.
Jul 9 2025
In T6909#228780, @Viacheslav wrote:@natali-rs1985 Can you create a backport to circinus?
@natali-rs1985 Can you create a backport to circinus?
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.