Router Reflector Scenario

Hello, I’m setting up a reflector router with FRR in the lab.
I have a Mikrotik ROS 7.6rc2 peering eBGP with a provider, the provider sends me about 145,000 routes. On the Mikrotik I have configured an iBGP peer towards the Route Reflector, the routes are then correctly propagated to the router reflector. The problem is that the router reflector sends the routes back to the mikrotik and I find myself on the routing table of the double routes, the routes received by the reflector are obviously disabled because they have a weight of 200 while the eBGP route is the active one. I remember that with ROS6 iBGP routes that were double or in any case non-preferential compared to an eBGP route were automatically withdrawn.

What am I forgetting?

Theoretically RouterOS should discard the paths received from the Reflector which have as Originator ID itself or am I wrong?

from MT wiki:
Also note that next-hop is not changed on route reflection, except when it’s set in the filter.

so u need routing/filter/ rules

Hi Nicky, it’s not about the next hop .. here’s what the support replied:

Thank you for the report, It is a known problem and will be fixed in the future.

Unfortunately there is no filter capable of discarding a route via Originator ID, see: https://help.mikrotik.com/docs/display/ROS/Route+Selection+and+Filters

Maybe construct a deny filter for the corresponding iBGP connection so that it won’t advertise the routes back to the originator. For the time being this seems to me the only solution.

do you mean some filters on the reflector router side?

because I thought of creating a filter on the mikrotik rr to discard all the prefixes that have as originator ID itself .. unfortunately there is no expression to detect the originator ID from the RouterOS filters ..

maybe i should look if i can do something about FRR ..

On the RR itself since the last filter rule is a deny all. In that way it won’t be re-advertised to the originator.