I have done some testing with bgp in 2.9.10 and ran into a problem. I don’t know if its a configuration problem but I dont think so.
I’ve ran a script to generate 65000 routes on one router.
# Removing old route table.
/ip route remove [/ip route find routing-mark=bgptest]
# Start new routing entries.
:local startip 10.100.1.0
:for i from=1 to=65535 do={
:log info ("adding route " . ($startip + $i))
/ip route add dst-address=(($startip + $i) . "/32") gateway=10.20.0.1 routing-mark=bgptest
}
The /routing filter that is used is here:
3 chain=test-out routing-mark=bgptest action=accept
This should mean everything within the routing table ‘bgptest’ publish right? Here is the routing bgp instance:
1 as=64991 router-id=10.20.1.1 redistribute-static=yes
redistribute-connected=no redistribute-rip=no
redistribute-ospf=no redistribute-other-bgp=no name="testing"
out-filter=""
and then the peer setup (another 2.9.10 router with routing-test)
1 remote-address=10.20.1.254 remote-as=65530 multihop=no
in-filter=test-in out-filter=test-out route-reflect=no
hold-time=3m instance=testing ttl=60 tcp-md5-key=""
The only routes I get on the far end are the default gateway and the one single static route in the main table I’ve entered … it’s ignoring the routing-mark on the filter for test-out.
Progress is good on BGP - so far it seems to be more stable, faster, and has md5 passwords now! Thank you thank you thank you.
Sam