I’ve tried several times to get beta5 to load completely from beta4 on one of my routerboards (it loaded on another… but always just some of the packages would load initially, others had to be ftped up again, and again before being “taken”). The problem child is the wireless package (naturally, the one I need the most). It just refuses to load, for that matter, nothing beyond advanced-tools, dhcp, hotspot, ntp, and system will load. The files get deleted from the file area, but don’t get loaded. Also, every time (major, major problem IMO) is that the routerboards need to be manually (power cycled) everytime they are rebooted from Winbox. I’m going to try the reboot from the CLI this next time (faint hope, very faint) and see what happens.
Was able to downgrade back to beta4 OK. Still a mystery why 1) Beta5 won’t load completely, and 2) why a power cycle is required after a reboot (routerboards just freeze on reboot).
I managed to put Beta5 on two Soekris 4526 boards, upgrading from 2.8.13 (I think) not from a previous Beta.
Went on without a hitch, and showing about 5Mbps throughput LAN-wireless-LAN again using 5211 or 5212 cards (can’t remember which are on right now). Not enough time spent to find bugs, I will do more testing starting Monday.
Regards
Stephen
Good to hear that the Soekris is working well. I too, haven’t had any problems with MT on third party hardware.
Ironically, the problems are manifested on Routerboard alone, in my experience (and I have two of them to play with), and are quite frusterating with 2.9.
Again, hanging on reboot (every time, both boards), not taking an upgrade package completely, (again, every time, the system gets loaded, but nothing else, and it takes repeated ftp uploads and reboots–and the consequent power cycles, to get a load completely setup) Not very encouraging.
Keep in mind that these Routerboards, although identical in their hardware configuration (a/b 100mW cards), their power sources are different. One is powered from the supplied PoE injector/AC PS, and another is running off a 24vdc solar/battery setup. But both maifest the same problems.
I just want to remind you that “Routerboard” is a trademark of MikroTik and should only be used for products of http://www.routerboard.com
If you see any companies promoting products as routerboards that do not come from us, please inform us.
John
Routerboard 230’s, to be exact. And they don’t reboot when issued the command from 2.9beta2-5…they hang. Both of 'em. Most disturbing when hardware from other manufacturer’s works without a glitch w/MT, and the Routerboards don’t.
The other big problem IMHO is the fact that you cannot get a complete software load on them all at once. I’m not sure what’s causing it, but try uploading say, system, wireless, ppp, dns, advanced tools, routerboard, etc, as an upgrade. What I found is that system will load, but not the rest. To get the rest on the Routerboard, it took multiple FTP uploads of the packages in question, and multiple power cycles (because of the hang problem). And in one case, I was never able to get beta5 on one of the boards…it just wouldn’t take wireless, no matter how many times I tried, and I had to back down to beta4.
Perhaps it’s the software, but then again, perhaps I’ve got two identically bad boards…but it does seem a bit unlikely. Or maybe I’m doing something identically wrong…if so, I’d like to know what.
That is a good report. As many things are changed in v2.9, I am sure we will find such issues and more for a while. We will start putting this on all main routers soon to check the stability – of course we have redundency also.
John
What size and brand of Compact Flash you are using?
Martins
64MB, and it’s whatever ships with the Routerboards from routerboard.com. The licence is level 5. The amout of RAM is 64MB also.
please send a supout.rif file to support. make this file right after your system comes up after reboot.
I have been seeing the same “hang” problem on a RB230 I am using as CPE at my house. 128mb RAM and no additional interfaces…just using the two onboard LAN ports.
The system.npk has to be uploaded first and without other packages in order to “take”. I’m guessing due to it’s size. After system.npk has been uploaded and the sys reboot command is given the unit has to be power cycled before it comes back online. Uploading the rest of the packages can only be done a couple at a time for them to “take”.
Also, I just noticed the UPS module is not listed or configurable anywhere in Winbox even though it shows installed under packages.
Brad