RouterOS version 6.46.4 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.4 (2020-Feb-21 11:26):
Important note!!!
The Dude server must be updated to monitor 6.46.4 and v6.47beta30+ RouterOS type devices.
The Dude client must be manually upgraded after upgrading The Dude server.
To get RouterOS data from the devices, The Dude now requires RouterOS to be 6.46.4 or v6.47beta30+.
Changes in this release:
*) arm - improved watchdog and kernel panic reporting in log after reboots on RB3011 and IPQ4018/IPQ4019 devices (“/system routerboard upgrade” required);
*) branding - allow forcing configuration script as default configuration (new branding packet required);
*) branding - fixed “company-url” and “router-default-name” survival after system upgrade;
*) branding - fixed WEB HTML page survival after system upgrade;
*) certificate - fixed certificate verification when flushing CRL’s;
*) chr - fixed graceful shutdown execution on Hyper-V (introduced in v6.46);
*) console - fixed script with “dont-require-permissions=yes” execution without sufficient permissions;
*) crs3xx - fixed frame forwarding after disabling/enabling bridge hardware offloading for CRS354-48G-4S+2Q+ device;
*) defconf - added welcome note with common first steps for new users;
*) dude - updated The Dude to use new style authentication method;
*) health - fixed maximum SFP temperature reading under ‘/system health’ menu;
*) ike2 - fixed DHCP Inform package handling when received on PPPoE interface;
*) lte - added interface name prefix for logging events;
*) lte - added “phy-cellid” value support for R11e-LTE-US;
*) lte - do not allow using empty APN Profile names;
*) lte - improved all APN session activation after disconnect on R11e-LTE;
*) lte - use APN from network when blank APN used on R11e-4G;
*) snmp - fixed “routeros-version” value returning from registration table;
*) snmp - fixed UPS battery voltage value scaling;
*) ssh - added support for RSA keys with SHA256 hash (RFC8332);
*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
*) telnet - improved telnet compatibility with other client implementations;
*) user-manager - fixed signup enabling (introduced in v6.46);
*) webfig - added default configuration confirmation window to WebFig;
*) webfig - do not show WebFig menu when opening ‘Check For Updates’ in Quick Set;
*) winbox - completely removed old style authentication method;
*) winbox - fixed “invalid” flag presence under “System/Certificates/CRL” menu;
*) wireless - improved compatibility for “ETSI” wireless country profile;
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.
dude - updated The Dude to use new style authentication method;
i have updated (packagees, dude & routerboard) the dude Server and all clients but the dude Server can’t connect.
RouterOS Status: std failure_ not allowed (9)
bevore upgrade it works…
everything works fine except RouterOS login and also link statistics based on RouterOS
Have you updated the Dude client on your computer? 6.46.4 has to be installed manually, as older versions cannot connect to RouterOS 6.46.4 to do autoupdate as it has usually been.
I tried to connect with Dude 6.46.3 and it also failed. Connection succeeded after dude-install-6.46.4.exe was run.
To get RouterOS data from the devices, Dude now requires RouterOS to be 6.46.4 or newer. The other stats and of course Ping will still work. This is due to security measures being strengthened.
It looks like Dude server cannot make RouterOS connections to other devices and ends up with STD failure, when RouterOS connection is made in context of limited user account. Previously it was possible with only “read” + “dude” permissions.
Now it has to be at least “read” + “dude” + “winbox”. After I added “winbox” permission and clicked “Reconnect”, connection state changed to OK and all RouterOS data became visible again.
After updating in arm an RB4011 has stopped working, there is no response in any ethernet. Recovered with netinstall. Perhaps any problem while updating. Second Rb4011 without problems
How do we take advantage of this? Looking in ROS and haven’t been able to find anything and I’ve also looked at the branding manager and couldn’t see anything.
This happens to me on HAP ac2, RB951Ui-2HnD, HAP Lite, even with a user that has full permission. I don’t see this problem on CHR, CCR, HeX.
All devices are running 6.46.4 fw + rb fw.
Only devices behind the hex (dude agent) show this error.
CCR1036 - CRS328 - hAP ac lite - 2X RB2011, Upgraded without problems.
Usage: home network with caps-man, l2tp/ipsec, Fail-over, load balance, Dude, hotspot, userman, Dynamic Routing mark,
Auto backup to FTP server and Email, Report to SMS, Email, Telegram and Log Server,…
