RouterOS version 6.42.4 has been released in public “current” channel!
Before an upgrade:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 6.42.4 (2018-Jun-15 14:14):
*) bridge - allow to make changes for bridge port when it is interface list;
*) bridge - fixed FastPath for bridge master interfaces (introduced in v6.42);
*) certificate - fixed “add-scep” template existence check when signing certificate;
*) chr - fixed adding MSTI entries;
*) chr - fixed boot on hosts older than Windows Server 2012 when running CHR on Hyper-V;
*) chr - fixed various network hang scenarios when running CHR on Hyper-V;
*) console - fixed script permissions if script is executed by other RouterOS service;
*) dhcpv4-server - fixed DHCP server that was stuck on invalid state;
*) health - changed “PSU-Voltage” to “PSU-State” for CRS328-4C-20S-4S+;
*) health - fixed incorrect PSU index for CRS328-4C-20S-4S+;
*) ipsec - improved reliability on IPsec hardware encryption for RB1100Dx4;
*) kidcontrol - fixed dynamically created firewall rules order;
*) led - added “dark-mode” functionality for hEX S and SXTsq 5 ac devices;
*) led - fixed CCR1016-12S-1S+ LED behaviour after Netinstall (introduced in v6.41rc58);
*) led - use routers uptime as a starting point when turning off LEDs if option was not enabled on boot;
*) ppp - fixed “hunged up” grammar to “hung up” within PPP log messages;
*) quickset - added missing wireless “channel-width” settings;
*) quickset - added support for “5ghz-a/n” band when CPE mode is used;
*) snmp - added remote CAP count OID for CAPsMAN;
*) snmp - fixed readings for CAPsMAN slave interfaces;
*) supout - added “partitions” section to supout file;
*) usb - properly detect USB 3.0 flash on RBM33G when jumper is removed;
*) userman - improved unique username generation process when adding batch of users;
*) w60g - improved RAM memoy allocation processes;
*) winbox - added missing “dscp” and “clamp-tcp-mss” settings to IPv6 tunnels;
*) winbox - allow to specify full URL in SCEP certificate signing process;
*) winbox - by default specify keepalive timeout value for tunnel type interfaces;
*) winbox - show “scep-url” for certificates;
*) winbox - show “System/Health” only on boards that have health monitoring;
*) winbox - show firmware upgrade message at the bottom of “System/RouterBOARD” menu;
*) wireless - enable all chains by default on devices without external antennas after configuration reset;
*) wireless - improved Nv2 reliability on ARM devices;
To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device
Please keep this forum topic strictly related to this concrete RouterOS release.
Hey there, many thanks for the latest release though it looks like I am getting a 404 not found for ARM (rb3011) through your download page. I might just be a very keen bean!
Does it fix the “lost space after upgrade” issue on CCR?
(when upgrading 6.42.1 to 6.42.3 on a CCR split into two 64MB partitions a lot of diskspace remains in-use after the upgrade and not enough space is left for another upgrade)
Donkeyrollerz - You tried to download version while it was still being released. pe1chl - Version fixes all the problems mentioned in changelog. There are no hidden fixes.
So how is the indicated problem going to be fixed?
Users who have installed 6.42.1-6.42.3 on CCR are effectively at a dead end.
Having to use netinstall on all those “bricked” routers is simply not acceptable!
Either a fix package or an included fix in a later release is required.
As it is now, I can no longer upgrade my two CCR that are on 6.42.1 because that disables future upgrades on them.
Can anybody make me a solution / script so after the ROS upgrade the unit either in the same reboot, or thereafter reboots again to update the fw version?
Now each and every unit has to be rebooted twice. which is a pain if you have to do big amounts…
It’s tested & working just fine on 2 ROS devices I own.
It’s not my script but I find it usefull.
The only bootloop possible is one caused by the new bootloader not being properly written. Which didn’t happen to me on 30-40 RC updates.
If bootloop happens, just netinstall the router again and make sure to have backups available. I backup my router configs daily using another script that sends the backup config files over email.
Bad day = netinstall + restore backup.
It’s probably less than 1% chance to get a bootloop, though.
Well, I am not of yesterday. I have to try it first. I made some scripts myself in the past but just as script that I’d copy and paste in a terminal window when we upgrade units.
But sometimes on the new cpu’s the scripts are processed so fast some setting that in a ‘step by step’ try out work fine in a ‘one script’ just don’t perform. Then I tried to build in more delay times and we tried this, then that. And next time there is a new ROS the bloody script language is changed again and nothing works anymore… (I usually use ROS upgrades to keep record which units have had other configuration changes as well. After 12 years of working with MT we still learn new things each time which makes us to change the general OS setting of all the CPE’s..
So yeah, I am going to try something like this on a unit on my desk first… then another unit, and another, before in the field…
I just don’t understand why both the OS and the fw can’t be upgraded in one go…
I’m also not a fan of the labeling of firmware by RouterOS version. Previously, after updating RouterOS, I could easily see if firmware was outdated and choose to do a 2nd reboot. Now it always appears outdated, even if there were no changes between versions.
