Donatas Abraitis

I tested with your given config, I can't replicate this. Can you enable `debug bgp updates` and see why 0.0.0.0/1 is denied in the logs?

If you could enable logs, it would be much easier to spot why it's not added to BGP.

Also, keep logging enabled and remove 0.0.0.0/1 then recreate it. Then show the logs here. From this output, https://github.com/FRRouting/frr/issues/11935#issuecomment-1250638560 seems that the route-map kinda works _OK_, but the route is...

> You mean remove the route for 0.0.0.0/1 temporarily, or remove the prefix from the prefix-list? I think I also disabled rm-optimization, which unfortunately did not help. You can try...

Are you able to replicate easily the same behavior? Logs still would be useful.

Let's wait until October 4, when the freeze ends.

@maduri111 could you rebase?

Is this related to specifically 8.2.2 or even 8.0, because you said 7.5.1 - OK, 8.x - NOT OK.

I'm unable to replicate your case: ``` pe2# sh ip bgp vrf RED 172.16.255.1/32 BGP routing table entry for 172.16.255.1/32, version 2 Paths: (1 available, best #1, vrf RED) Advertised...

Can you show `show ip bgp vrf red 1.1.1.1/32`? And again, enable `debug bgp nht`, `debug bgp updates` and show the logs. >Any difference in configuration between what we both...