RouterOS version 6.42.1 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.1 (2018-Apr-23 10:46):
!) winbox - fixed vulnerability that allowed to gain access to an unsecured router;
*) bridge - fixed hardware offloading for MMIPS and PPC devices;
*) bridge - fixed LLDP packet receiving;
*) crs3xx - fixed failing connections through bonding in bridge;
*) ike2 - use “policy-template-group” parameter when picking proposal as initiator;
*) led - added “dark-mode” functionality for hAP ac and hAP ac^2 devices;
*) led - improved w60g alignment trigger;
*) lte - allow to send “at-chat” command over disabled LTE interface;
*) routerboard - fixed “mode-button” support on hAP lite r2 devices;
*) w60g - allow to manually set “tx-sector” value;
*) w60g - fixed incorrect RSSI readings;
*) w60g - show phy rate on “/interface w60g monitor” (CLI only);
*) winbox - fixed bridge port MAC learning parameter values;
*) winbox - show “Switch” menu on cAP ac devices;
*) winbox - show correct “Switch” menus on CRS328-24P-4S+;
*) wireless - improved compatibility with BCM chipset 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.
I have updated one 3011 and two CHR (Hyper-V) and so far so good. Took the ones that have a public IP first.
Don’t think this was a problem for me though as I block anyone, for 30 days, coming from internet trying to connect to Winbox port.
Could You explain: winbox - fixed vulnerability that allowed to gain access to an unsecured router - please?
What do You mean “unsecured router”? All versions under 6.42.1 are affected?
Upgrade one RB750Gr3, and three hAP AC Lite (one of them used as CPE). All fine and dandy. The first reboot took a little longer than what I’m used to, but nothing to write home about.
After reboot VM works fine, 2 hour later can’t get IP address from DHCP server, static IP don’t working, enable/disable iface/ dhcp client - without sucess. Reboot can temporarily fix this problem.
Here is my experience in upgrading from 6.41.3 to 6.42.1
Package, find new package, download , install and reboot.
This works fine. Software is up on 6.42.1
It takes about 2 min to upgrade
Then I go to routerboard.
Current Firmware 6.41.3
Upgrade Firmware 6.42.1
Click Upgrade
Do you really want to upgrade firmware? OK Nothing happens. no information, no new version.
For me this i a broken hardware upgrade, or at missing some in the process.
Do I need to upgrade hw in the rouerboard menu, or it need just another reboot?
Why does it not reboot and tell me that hw is doing an upgrade when click the upgrade menu in routerboard menu?
The same with missing line in log “Firmware upgraded successfully, please reboot for changes to take effect!” happened to me today on RB951G-2HnD.
Little scary on 50km away device Did the upgrade failed? Should I reboot or better not?
Anyway I sent the reboot command - and all seems fine - after reboot is firmware upgraded to 6.42.1.
Updated several RB2011UiAS-2HnD, RB1100Dx4 and hAP ac (also lite version) and so far everything looks ok.
In addition to previous messages in this thread, while updating firmware, all RBs wrote “Firmware updated, please reboot to take effect!” message in log.
This vulnerability isn’t much of a problem. The problem is administrators leaving their firewall services (API, Winbox, SSH, etc.) exposed to untrusted networks. It’s better to apply firewall filters to the input chain that will protect against this and other future attacks.
Did the upgrade failed? Should I reboot or better not?