Hi,
I’m trying my first bgp connection with ROS. This is a real
hard learning curve. (I’ve done this with Cisco and Quagga already).
My newest problem is winbox handling of routes.
Enabling a full feed makes winbox unusable. It seems that
exchanging the routing table makes winbox hanging around.
CPU of the PC running winbox is 100%. If I kill winbox I can
relogin with winbox.
Shutting the feed down gives the same problem.
2.9.42 routing-test
Stefan
Problems seems to be known:
http://forum.mikrotik.com/t/mt-bgp-border-router/1159/1
So this makes winbox unusable with a bgp router if there is not a
real fast connection between winbox PC and bgp router. I see this
loading of routes at connection time and when I open IP-Routes-Window
this loading is done again.
I’ve some hints for people trying to setup bgp:
beware of the prepend parameter. I know it from cisco/quagga where
it is the path you prepend to the AS path. In ROS it is the count how
often you prepend your AS to the path. So if you use it ciscoish
you shoot with a real big path at your bgp-peer (depends on your AS 
).
Prepend 1 is default. If you want your peer to see your AS twice
you have to write 2.
Using multihop I needed an incoming filter to set my nexthop.
It’s not enough to have a static route to the peer.
Stefan
Hi,
If I set an incoming filter to prepend incoming routes I have only the
possibility to prepend my own AS.
Seems this is ok for Cisco, but quagga/zebra does not install
routes with its own AS prepended. (I tried to enforce this with
a higher localpref). I think incoming prepend should
prepend the AS of the peer the announcement comes from.
Stefan