This blog has now been updated to 3.5.
So I finally decided to upgrade my home router to ROS 6.0. With RC5 just coming out I figured it was a good time to do so. Some notes
I upgraded a RB450G. Board firmware went from 2.41 to 3.02. Dear mikrotik a changelog on this would be nice.
The terminal screen has some basic commands to help you get starte if you are new to command line.
The Plus is now blue. Much more soothing.
I have had several people inquiring about what the Ubiquiti ToughSwitch interface is like. The following are some screenshots for you.
What’s new in 5.22 (2012-Nov-23 09:28):
*) userman – fix PayPal “bad HTTP response”;
*) kvm – fixed possible ROS guest incomplete package installation;
*) l2tp server – added keepalive-timeout setting;
*) wireless – fixed RADIUS mac-caching;
*) wireless – fixed rare nv2 link stall;
*) metarouter – fixed system occasional lockup for 12s on RB4xx and RB7xx;
*) metarouter – fixed crash when FPU exception was raised in one of powerpc metarouters;
*) quickset – added HomeAP mode;
*) fixed “export compact” in “ip proxy”;
A few people have written in within the past 18 hours about their NTP server/clients getting set to the year 2000. The cause of this behavior is that an NTP server at the US Naval Observatory (pretty much the authoritative time source in the US) was rebooted and somehow reverted to the year 2000. This, then, propogated out for a limited time and downstream time sources also got this value. It’s a transient problem and should already be rectified. Not much really to report except an error at the top of the food chain causing problems to the layers below. If you have a problem, just fix the year or resync your NTP server.
From the Mikrotik Newsletter:
In RouterOS v6rc3 and newer releases we have
added a wonderful new diagnostics feature –
ability to detect cable problems. For example, if
you have an apartment building with complicated
Ethernet wiring inside the walls or ceilings, and
you lose the link – previously, you would need
special equipment to pinpoint the location of
cable damage, before you open that wall, but
now – RouterOS will tell you these things:
• which cable pair is damaged
• at what length is the cable broken
• how is the cable broken – shorted or torn
This also works if the other end is simply
unplugged – in that case, simply the cable lenght
will be shown.
This works on SXT-G, RB711G, RB2011, RB750
series and other devices with the same switch
chips, and also the Cloud Core series devices.
Here is example output:
[admin@CCR] > interface ethernet monitor ether5
In the above example, cable is not shorted but
cut “open” at 4 meters lenght, all cable pairs
equally at same location.
From the UBNT Forums
major bugs fixed in this release:
IP addresses now correctly resolved and updated (IP-probing is employed when needed)
more graphics-card related lock-ups fixed
topology resolution behind routers improved
server IP-aliases related high CPU usage bug fixed
bugs in device-settings dialog fixed
mass-passowrd change bug fixed
user and device credentials encryption added for db-files and user-settings file
server’s MAC-address resolving on virtual interfaces related bug fixed
server’s reachablility from device is probed automatically to auto-diagnose “offline devices” problems
new features added:
redesigned UI with major visual and usability improvements
WLAN-Uptime and Frequency monitoring
Mass-configuration inspection for both pre-5.x and 5.x firmwares (modifying pre-5.x configurations will come with Beta4)
setup “wizard” with automatic network scan added
predefined “SSIDs” devices group
It is not recommended to test in a production environment. Test only on a small subset of devices, since there may be issues.
to test Beta 3, first, you will need to fully uninstall previous (Beta 2) release first, both server and client. On Ubuntu use “Purge”. If you have monitored any devices using Beta2′s server, please, stop monitoring them before you uninstall Beta2 and install Beta3.
if you see inconsistencies in the automatically resolved topology and you have active PoE configurations in it, please, do not perform mass-firmware updates with AC2 beta, this can cause permanent damage to some devices.
I had a permalinks plugin installed which screwed up my RSS feed. This has been removed and now fixed. If you want to check your RSS subscription and let me know if it’s working. Otherwise please re-subscribe by clicking subscribe in the upper right.