Routing-test BGP
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.ph ... hlight=bgp. Any news? Large BGP support is very invited.
test of BGP
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.
Please answer this quiestion, If my necessary features will not work fine, I have to change to Zebra e.g.
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
/ 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
change bgp route
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.
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
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
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...
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...
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"?
Last edited by gottin on Fri Oct 14, 2005 11:46 am, edited 1 time in total.
The issue is open for the vendors to decide.
Cisco although has "network x.y.z.v/n" command in bgp, the network is not propagated until it exists in the routing table. The solution is actually the same.. You just have to add a null route (ip route 10.0.0.0 255.255.255.0 null0 for instance if you want to propagate the 10/24 to bgp)
My question is ...
Is there some roadmap on the routing-test package that we can see what's coming?
Will there be bgp dampening? (provided that we have the memory to do such things)
Also can there be a change on the default bgp timers not to be 0 (timeout etc)?
Since there IS bgp I hope it will be a complete package.
Keep up the good work guys..
EDIT
A null interface would be a good idea don't you think?
Cisco although has "network x.y.z.v/n" command in bgp, the network is not propagated until it exists in the routing table. The solution is actually the same.. You just have to add a null route (ip route 10.0.0.0 255.255.255.0 null0 for instance if you want to propagate the 10/24 to bgp)
My question is ...
Is there some roadmap on the routing-test package that we can see what's coming?
Will there be bgp dampening? (provided that we have the memory to do such things)
Also can there be a change on the default bgp timers not to be 0 (timeout etc)?
Since there IS bgp I hope it will be a complete package.
Keep up the good work guys..
EDIT
A null interface would be a good idea don't you think?