v6.47.2 [stable] is released!

RouterOS version 6.47.2 has been released in public “stable” channel!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 6.47.2 (2020-Aug-13 06:39):

Changes in this release:

*) arm - improved stability when forcing 25G speed on unsupported interface;
*) crs3xx - fixed QSFP+ interface LEDs when using break-out cable for CRS326-24S+2Q+;
*) crs3xx - fixed QSFP+ interface linking after reboot for CRS326-24S+2Q+ (introduced in v6.47);
*) discovery - use “static” interface list by default instead of “!dynamic”;
*) fetch - show status “uploaded” instead of “downloaded” when uploading a file;
*) hotspot - do not verify Hotspot interface status when detecting if HTTP/HTTPS login method is allowed;
*) interface - added new builtin “static” interface list;
*) l2tp - fixed multiple tunnel establishment from the same remote IP address (introduced in v6.47);
*) lora - fixed “spoof-gps” parameter padding (introduced in v6.47.1);
*) lte - fixed dynamic DHCP client creation when editing APN profile;
*) ospf - fixed case when changing one distribution metric changed metrics for other distribution options;
*) ppp - fixed PPP interface editing for the first time after reboot or after 20 seconds;
*) qsfp - fixed break-out cable linking after reboot (introduced in v6.47);
*) routerboot - fixed memory test on CCR2004-1G-12S+2XS (“/system routerboard upgrade” required);
*) sfp - stabilized CRS212 SFP port functionality and improved monitoring of optical modules;
*) sftp - fixed “flash” directory access (introduced in v6.46);
*) smb - fixed file path validation (introduced in v6.46);
*) smb - fixed possible memory leak;
*) smb - fixed SMB server (introduced in v6.47);
*) smb - limit active session count to 5 per connection;
*) snmp - fixed “current” value reporting on CCR series devices;
*) snmp - fixed “fan-speed” value reporting on CCR series devices;
*) wireless - added support for U-NII-2 for cAP ac;
*) wireless - updated “indonesia5” regulatory domain information;
*) www - improved WWW service stability when receiving bogus packets;

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.

Are you guys serious? The second update, in the last couple of months, with problems you don’t expect at all. One core is constantly 100% loaded with something incomprehensible.

Please include the relevant CVE number for fixes like this, so we can independently evaluate the urgency of an upgrade.

not much here for me to get excited about… but good that they continue to seek and rectify bugs.

At the moment, the download has dropped. But I would like to know what it was, if there is any information.

Information was in the supout.rif file which you should have generated when the issue was present. As funny as it may sound, even we can not tell anything about the issue by looking at a screenshot (if you can call 360x176 pixels a screenshot) showing 100% unclassified load.

pe1chl, first one is not even a vulnerability, but related to directory accessing over SMB. The second one - it was possible to load one CPU core to 100% by sending a crafted packet to router’s www service. As always, you are safe if the service is not exposed to the Internet.

*) wireless - added support for U-NII-2 for cAP ac;

Can someone enlighten me about this one? I have 3 of these and one of them run channel ch54-5270 and this works and this is within U-NII-2 or I’m I just plain stupid after the vacation as my brain has yet to start working, which is most likely the case :slight_smile:

Edit: Ok I think I got the answer from Reddit. This is a US thing which explain why my EU units can operate in this band and also U-NII-3 if I want it to.

Why is my RB4011, changes 5G frequency from 5220 to Auto when I open wireless interface or Quick set window. & Crashes 5G indoor wifi.

I am Using “US” Version of RB4011

Just updated my CRS326-24G-2S+ switch from v6.47.1 to v6.47.2 and now I am not able to login to the switch using Winbox 3.24 to update the firmware.
Switch is functional but Winbox cannot connect to switch.

Update on my CCR1009-7G-1C-1S+ worked without issue

What is my option to fix my CRS326-24G-2S+ switch ? Netinstall ?

[edit – update] I removed the switch power supply waited for 2 minutes then re-powered … now I can login using Winbox and upgrade the firmware.

I don’t see any fixes for the w60g reliability issues introduced with v6.47 Any word on that?

What issues?

Constant disconnects. See for example:
http://forum.mikrotik.com/t/v6-47-1-stable-is-released/141227/120
http://forum.mikrotik.com/t/w60g-link-stability-and-erratic-rate-selections-since-ros-6-47/141321/1
http://forum.mikrotik.com/t/60ghz-link-unstable/141735/1

i can’t properly see your picture, can you make bigger for us

well, likely some script/task which has to run after startup. E.g. scheduled script downloading firewall rules? BGP with large table? etc…

Hi,
I am sorry but I am still having the same problem on this point :
*) l2tp - fixed multiple tunnel establishment from the same remote IP address (introduced in v6.47); any advice ?

Is this a bug? (Uploading file via SFTP from Mikrotik Router to remote server)

/tool fetch upload=yes url="sftp://server/path/file" user=example password=example src-path=file src-address=ip
failure: only http[s]/sftp supports src-address

hAP Lite - not enough space for upgrade

open image link ohne “t” (thumbnail)

https://c.radikal.ru/c39/2008/2c/6e9b16a53516t.jpg

Full image: https://c.radikal.ru/c39/2008/2c/6e9b16a53516.jpg

Thats a ~18 Euro hardware, dont expect much from such a device…

That may apply for other manufacturers but not for Mikrotik. It is expected that software release will work on every supported device, no matter the price.

Anyway, not enough space means most likely the RAM is almost full. Easiest way to fix this is restart the device and try it again. After restart, memory is usually pretty empty, allowing to store the packages.
If that does not help, there is always the “netinstall” way