RouterOS version 6.46.2 has been released in public “stable” 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.46.2 (2020-Jan-14 07:17):
*) chr - improved stability when changing ARP modes on e1000 type adapters;
*) console - prevent “flash” directory from being removed (introduced in v6.46);
*) console - updated copyright notice;
*) crs305 - disable optical SFP/SFP+ module Tx power after disabling SFP+ interface;
*) defconf - fixed “caps-mode” not initialized properly after resetting;
*) defconf - fixed default configuration loading on RBwAPG-60adkit (introduced in v6.46);
*) lora - fixed packet sending when using “antenna-gain” higher than 5dB;
*) lte - fixed “cell-monitor” on R11e-LTE in 3G mode;
*) lte - fixed “earfcn” reporting on R11e-LTE6 in UMTS and GSM modes;
*) lte - report only valid info parameters on R11e-LTE6;
*) ppp - fixed minor typo in “ppp-client” monitor;
*) qsfp - do not report bogus monitoring readouts on modules without DDMI support;
*) qsfp - improved module monitoring readouts for DAC and break-out cables;
*) routerboard - added “mode-button” support for RBcAP2nD;
*) security - fixed vulnerability for routers with default password (limited to Wireless Wire), admin could login on startup with empty password before default configuration script was fully loaded; ) system - fixed ".auto.rsc" file execution (introduced in v6.46);
*) system - fixed “check-installation” on PowerPC devices (introduced in v6.46);
*) traffic-generator - improved memory handling on CHR;
*) webfig - allow skin designing without “ftp” and “sensitive” policies;
*) webfig - fixed “skins” saving to “flash” directory if it exists (introduced in v6.46);
*) winbox - automatically refresh “Packets” table when new packets are captured by “Tools/Packet Sniffer”;
*) winbox - fixed “Default Route Distance” default value when creating new LTE APN;
*) winbox - removed duplicate “join-eui” and “dev-eui” parameters under “Lora/Traffic”;
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 particular RouterOS release.
*) security - fixed vulnerability for routers with default password (limited to Wireless Wire), admin could login on startup with empty password before default configuration script was fully loaded;
Don’t forget to update the Security blog. During writing this the blog has not been updated.
[admin@switch] > sy pa up do
channel: stable
installed-version: 6.46.1
latest-version: 6.46.2
status: Downloaded, please reboot router to upgrade it
[admin@switch] > file print
# NAME TYPE SIZE CREATION-TIME
0 skins directory jan/01/1970 02:00:09
Nothing seems to download in quite a few MT devices
LeftyTs, the downloaded files are no longer visible in /files section when using Package Updater. You can still reboot the device and it will upgrade. Or use /sys pac upd cancel to free the storage.
That is just plain silly!
Now when I check for new version and click Download, or after uploading files using FTP, I cannot even check if the files were loaded completely before doing a reboot!
Please undo this change, it serves no useful purpose and has many disadvantages.
This is very bad idea! It’s extremely important to check that all required packages were downloaded correctly before update. Missing packages may result in completely inaccessible router.
Packages are not some sensitive “system files”, you can download them from Mikrotik website and they are digitally signed. I don’t see any security reason to do this, they are protected enough already.
Agreed. Our network runs a complicated script to automatically upgrade units only to releases that have passed our testing and been made available on an internal server. The script takes pains to ensure that all files have been downloaded completely before automatically rebooting. Now it appears that you have introduced an unadvertised change that will cause the script to fail. (Ironically, this is a second order effect, because at the same time you also broke /system upgrade entirely so that they cannot even begin to execute.) This change has no obvious benefit to users, while actively impeding them (both scripts and humans) from ensuring that an upgrade Is complete and correct before installation reboot.
