Simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu.
What’s new in 6.10 (2014-Feb-12 13:46):
KNOWN ISSUE: IPsec AES-CBC 256 Bit encryption algorithm doesn’t work in some cases. Use 128 bit AES, or hold on for v6.11
*) fix autosupout.rif generation after kernel panic;
*) ovpn - make it work again;
*) ovpn client - remove cipher=any & auth=any options,
protocol does not support them;
*) pptp - fixed where Windows & MacOS clients were disconnecting all the time;
*) sstp - make it work with Windows client with AES encryption;
*) ipv6 pool - fix dynamic prefix disappearing which may influence large
VPNs with IPv6;
*) ssh client - fix key agreement when sometimes wrong DH algorithm was selected;
*) bgp - multipath eBGP now does not propagate BGP nexthop unless
forced in configuration;
*) removed 10/100 half duplex from autonegotiation advertisement on CCR;
Check your BIOS settings for HDD, try to change the SATA settings to compatibility mode or legacy mode.
What kind of motherboard and chipset are you using?
RB2011UAS-RM. (with LCD)
I updated last firmware in 6.9 - 3.10
Normal full starting (seen on LCD) working about 5-10 sec - reboot… again start … reboot … loop
I don’t have converter micro-USB now and connect to console…
ahum, version 6.10 now already… they must be speeding up their new release in front of a new season of mum’s…
I actually noticed a small, only irritation causing, error in the latest 6.xx versions… I was hoping it would go away itself in newer releases but no… (well, I didn’t test 6.10 yet)
Anyway; when you open a telnet session and you type the login the first time but you make a typo, in the old days a backspace and re-type was enough to correct the typo. But since some versions the moment you try to use backspace button, it just creates extra symbols and you basically have to close the telnet window to open it again new…
So if MT guys are reading this, please correct this irritating behaviour in the next version. I think I skip 6.10 now (just rolling out 6.9) and wait to see this correction in 6.11 or .12 made…
Ok.
But intresting moment: today I installed last DUDE version (beta) to this RB2011 and not rebooted it yet.
Only add 2 devices with ping.
First reboot with DUDE was upgrade to 6.10.
Found here intresting info - http://forum.mikrotik.com/t/dude-crashes-rb2011-uas-rm/72782/1
I have the same problem.
Noticed on v6.9 and this is still present is v6.10 as well - Times in log are always in +0 gmt offset even though I have set up another time zone. When going in system->clock it shows correct time, in my case 19:57 at the moment (gmt offset +02:00), but in log it shows 17:57
Well, not true imho. It started about half a year ago. Don’t know what version I actually was using then, probalby 6.3 or 6.4 (that was a disaster version anyway). Never had that before, I am sure. I use quit a long admin login with 12 caracter passw. So typo’s are relatively easy made, special when your under stress and things go wrong… So it hits me again and again, something I am sure not was happening earlier versions…
Anyway, the cntrl+backspace option was not know by me, so thanks…
Now my sstp connections with 6.7 clients don’t work, Nice.
Reverted to 6.7…
Mikrotik, you should really hire some test engineers. Maybe start reading about Lint, QAC, Rational Test Realtime, automated functional regression testing…