hmmmm ok. right now use netinstall with the key supplied in it
FYI, I have installed 2.9.23 and it’s install ok, so it might be something wrong with 2.9.24
btw, why upgrade if everything that is needed is working? 
no, janisk, the problem was not with upgrade, but with clean install. please re-download the CD installation ISO, we have fixed the issue. the new ISO will be online in 3 minutes.
bgp setup w/ routing-test won’t work without redistribute connected, in version 2.8.28 w/ regular routing, filtering won’t work correctly
redistribute inject into bgp cause bgp origin=incomplete
and sometimes routing table screwed!
bgp can’t see if peers refreshed…
another problem :
state=established, prefix=180000+, but no routes in routing table???
even there is routes in routing table, ping timeout, reboot router fix this problem
supout.rif already sent!
Where the BEEEEEEEPPPPP… is RSTP?
I am trying to set up a WDS mesh system !!!
Craig
I may try to upgrade some of our routers that are using VRRP this weekend and we’ll see how it goes.
Any advice for upgrading VRRP enabled routers from version 2.9.7?
We use RSTP too. Did someone find out if that is enabled in this release or schedule for a future release?
Hello
well, the missing bgp network command can be replaced -in a way- by enabling the “redistribute static” in the bgp instance settings
and by installing a static route manually that should point in a local interface.
By making this we should filter properly our routes.
It’s a fact that the routing-test from 2.9.20 and up has been greatly improved.
In fact it outperfrom the stable routing package.
However there is a major problem in the bgp update process.
In some circumstances bgp removes succesfully a route as is suposed to do, but it does not inform correctly other bgp neighbors.
The only way to uninstall the invalid routes from the other neighbors is by disabling/enabling the bgp instance in them.
In any case the bgp timers was set in a value bigger then zero because in the past we were having problems when they left in 0.
This situation was tested and replicated succesfully in our wireless network in several routers in Athens (http://www.awmn.net).
Thanks in advance
Here is an example of a stucked AS path (2.9.24 routing-test).
routing bgp instance> print
Flags: X - disabled
0 name="default" as=1286 router-id=10.17.119.1 redistribute-static=yes
redistribute-connected=no redistribute-rip=no redistribute-ospf=no
redistribute-other-bgp=no out-filter="" client-to-client-reflection=no
Destination: 10.94.141.0/24
BGP AS Path: 3757,4790,2379,913,410,3180,3170,2801,2804,38,941,199,3329,2315,1,2615,5023,45,8580,65141
The bgp router from which this info has extracted, is having link with bgp routers 45 and 3757.
The bgp router 45 does not have this route in his routing table.
The network 10.94.141.0/24 actually is down but its stuck on some routers bgp table
and comming in to my router from the bgp neighbor 3757.
This produces invalid path information in the routing table and its just a small example of the problem.
There is also a supout availlable.
where?
If you mean the supout, i just send it to the support mail.
Thanks
Just to let you know that this issue still seems to be there in the CF image. Copied the image to CF then installed on a WRAP and got the license expired message. Install 2.9.23 then upgrade to 2.9.24 works fine.
I also have the same problem on my router running 2.9.24 + routing test
I have sent the supout.rif to mikrotik let’s hope that they will find out what’s wrong.
Yeah, you are not the only one who have problem with crashing winbox efter upgrading to 2.9.24.
Yes I´m using winbox the latest 2.2.10 version… 
but it still doesn´t work 