Hi Guys.
We’re using only BGP on a number of networks (both eBGP and iBGP). One of the recurrent issues we have is that default route cannot be propagated - are we seriously the only people that miss this feature?
I’m really not in the mood for deploying more Cisco’s at the edge 
Thoughts anyone?
R
Default route is propagated if default-originate parameter is set. The same behavior as cisco.
Hi mrz,
Actually, that’s not correct - in the Mikrotik case you ‘originate’ - you do NOT propagate the existing default route. As such the ASPATH and community information does not propagate. In addition, if I have a primary default via BGP and a secondary default as a static (with greater distance) the Mikrotik will continue to originate a default route even if there is no default in table.
If one looks at http://wiki.nil.com/BGP_default_route as an example. I don’t disagree that you originate a default on a session - just like a Cisco does. A cisco however allows me to propagate an existing default that is not neccesarily originated by that router.
Between own own network and networks we manage for customers I’d estimate around 150 Mikrotik’s running BGP. For me the default propagate and some BGP instabilities (where old routes remain in table indefinitely) are the only reasons we are forced to use Cisco routers in border router environments.
Don’t get me wrong - I love your product - I’m just trying to make it more useful to me in an ISP environment.
Any ETA on the new routing package that’s been mentioned in the forums?
R
Thank you for clarification. We will improve default route propagation.
Unfortunately I cannot give you any ETA on new routing package.