Guys,
It’s a normal behavior, or a winbox bug?
In Advertisement tab of BGP menu, i got a warning about too many advertisemement to show, but i know i have just 2, it’s the first bug.
The second one: If i click “ok, click here to see them all” i can see my 2 advertisement, but for just 2 second and the warning show up again.
Thanks for your answer.
Anyone?
Have you tried showing the same information from the command line interface?
If it shows only two and doesn’t give the warning, then I would think it’s a winbox bug.
Mikrotik support will probably need to answer this question better than I just did, though.
Yes, probably a winbox bug, as i said on first post, mikrotik guys confirm?
just an idea: is it possible that you have multiple bgp connection and reflect provider1 (+your prefixes) to provider2?
Thanks for your answer, no, just one BGP peer.
I get this problem too, on routers with thousands of routes or routers with ~20 routes, just never shows all the routes and is annoying.
Even when it does work (i.e. CLI) its slow as anything, this is the biggest performance boost required, searching through the route table and the advertisements table, taking 30s + is annoying as hell.
Maybe they should add a new action in the /ip route “folder” - something like:
/ip route lookup 12.34.56.192{/mask}
If no mask or /32 mask is specified, it should return the exact route that would be used to reach 12.34.56.192.
(or multiples if ECM routes)
If a valid mask is specified, then only routes of that exact prefix should be returned (if any exist in the routing table)
If mask is /0 is specified, a list of all matching prefixes in the routing table which include the target should be returned.
Routes returned by ‘lookup’ should have all of the usual attributes that routes returned by ‘find’ have - protocol, distance, next hop, etc - so you could still use get/set/where, etc.
Of course Winbox would need a nice query window for this functionality, with checkboxes for OSPF, BGP, etc…
Already possible
/ip route print where dst-address=12.34.56.0/24
/ip route print where 12.34.56.192 in dst-address
/ip route print where dst-address in 12.0.0.0/8
and so on.
I never thought about flipping those around like that.
Works for me - curious how fast it is on a full bgp table. (don’t have one to play with though)
Depends on CPU speed. On Routerboards its quite slow.
4 min on CCR 1036
with 3 bgp peer
536000 routes active
It seems like you could hook the RIP lookup so that it’s packet-fast even on a huge routing table.
(which is why I was thinking to make a “lookup” action in stead of filtering the output from a dump of the routing config + dynamic config)
EDIT- I mean RIB table lookup - what a funny typo it was to see RIP lookup. 
mrz, and what about the Advertisement table described on this thread?
bug confirmed?
Yes, its an old problem wait for v7.