Could we get some information about new implementation of BGP in 2.9? It’s quite a long time since John Tully wrote some progress http://forum.mikrotik.com//viewtopic.php?t=1059&highlight=bgp. Any news? Large BGP support is very invited. 
It’s working. You are welcome to try.
And documentation?
In the works 
Helo, I would like to test some features of new BGP but I have fundamental problems to configure basic things like how to announce a network when there is no “/routing bgp network” command.
Please answer this quiestion, If my necessary features will not work fine, I have to change to Zebra e.g.
Router announces only routes found in it’s own RIB.
To install the route-test package you have to remove route package first, reboot and then add the package? Any chances to lose connectivity by removing the package?
Upload routing-test package, then mark routing package for uninstall (/system packages set routing uninstall=yes) and reboot. You can lose connectivity in case you are connecting through a route learned by one of dynamic routing protocols.
Thank you, I tried route-test. I can’t see any settings via winbox
Terminal console is the way to go 
Anyone know how to setup the bgp to change the next-hop address?
/ routing bgp instance
set default as=64991 router-id=68.15.19.xx redistribute-static=no redistribute-connected=no redistribute-rip=no redistribute-ospf=no redistribute-other-bgp=no
name=“default” out-filter=“” disabled=no
/ routing bgp peer
add remote-address=216.165.129.xxx remote-as=65333 multihop=yes in-filter=all out-filter=none keepalive-time=0s hold-time=0s ttl=1 disabled=no
/ routing filter
add chain=bgpchain type=bgp action=accept set-nexthop=10.0.0.1 comment=“” disabled=no
The bgp routes are being established, but the ‘routing filter’ doesn’t seem to be doing anything. I assume its similiar to the filters within IP firewall, how do I match the incoming routes so that I can change the nexthop? Wondering if there is any initial docs anywhere on the /routing filter setup…
Sam
I have the same problem,
in your example I think you have problem, you have to redistribute something, e.g. redistribute-connect=yes.
As for the filter, it seems good but it should be assigned to the peer, so I suppose it should be:
/ routing bgp peer … in-filter=bgpchain
such a configuration modified gw of imported routed from peer, but the gw was “crazy”, it was “0.0.0.1”
If you find a solution, please let me know.
I am not redistributing any routes, therefore I have not checked any of those options. I am simply pulling routes from another location but not distributing any. This is actually for the bgp-bogon stuff that Cymru has done - I want to gather bogon routes from them and null-route them automatically.
Yes, I am getting the same results:
DST-ADDRESS PREFSRC G GATEWAY DIS INTERFACE
0 Db 1.0.0.0/8 u 0.0.0.1
1 Db 2.0.0.0/8 u 0.0.0.1
2 Db 5.0.0.0/8 u 0.0.0.1
3 Db 7.0.0.0/8 u 0.0.0.1
0.0.0.1 is unknown to me - maybe just a small bug in bgp-routing test package?
Sam
I just submitted a support ticket on this one. I believe it is a bug. Also, I can setup a 0.0.0.1 ip on an empty bridge and then it starts recognizing the interface, etc … so I’m almost there : )
Sam
I found that my problem is questioned here. Well, I’m interested how to specify which networks to announs when routeing-test is installed. Said in other words - what is the equivalent of “/routing bgp network” when routeing-test is installed.
I’m still learning this as well… I think /routing filter is what you want to look into.
Sam
Yes, I loked into /routing filter, howver couldn’t find a solution. Moreover there’s almost no documentation about it. If somebody knows s.th. relating this problem, please post some comments here.
10x
Hi Eugene,
I tried to configure routing-test as our border router, but stucked on the same thing as previous users.
There’s no option like /routing bgp networks.
I need to propagate whole subnet assigned from RIPE, in our case it is 80.78.144.0/20, if I will let propagate for example connected routes, so there will be propagating 10 subnets, each /24 size.
In the enterprise networking it is fairness and sometimes need to propagate as large as possible subnets. Some telco operators don’t accept prefixes smaller then /24, and if I use /30 point-to-point subnets for customers, they will not be propagated to the world.
I don’t know, how it is solved in cisco, for example, but I suppose that this feature will be necessary for regular using of new bgp implementation.
Now I’m still running old BGP (on 2.8.26), with satisfaction. I only miss more information in log about peers, if any error occur, I don’t have any possibility how to find problem.
Hope the new routing will be more communicative in this way…
Add /20 network to an empty bridge interface, set redistribute-connected to ‘yes’ and filter out prefixes smaller then /20.
I would be very glad in case that someone can explain why “/routing bgp network” has to be removed and no similar functionality added. Why people have to use hacks like “add an empty bridge interface, filter … and so on”?