Matching routes for originating-AS is VERY slow

RouterOS Forwarding Protocols
1

Hi,

we have a CCR1009 with a BGP full feed (~702.000 IPv4 and ~55.000 IPv6). Matching routes for a specific originating-AS eg. via ip route print detail where bgp-as-path~“15169$” sometimes takes up to 5 minutes. The router is running on latest ROS 6.42.5 and CPU usage is at around 10% in idle and while running the ip route print command.

On other platforms such as Cisco, Juniper, etc. matching routes works within SECONDS. Even performing a grep on a file with 1.000.000 lines on a recent ARM/RPi is much faster…

Is this normal behaviour?

Thanks

2

Welcome to RouterOS

3

Our “solution” was to take a BGP feed into a routeserver on Bird, and point https://github.com/sileht/bird-lg at it.

4

Will we ever see some improvement here?

5

MikroTik teased a new BGP implementation some years ago, part of the mythological “RouterOS v7”. More recently we’ve been hearing, “almost everything we were going to put in v7 is now in v6”… except things like not crashing when pushing lots of IPv6 packets, or BGP not constantly scanning the tables rather than doing actual updates, or… there’s a long list, we don’t know how long we’re going to be waiting.