v6.47.6 [stable] is released!

RouterOS version 6.47.6 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.6 (2020-Oct-21 10:41):

Changes in this release:

*) cap - fixed L2MTU path discovery;
*) crs3xx - fixed hardware offloaded LACP bonding on Ethernet interfaces for CRS354 devices;
*) crs3xx - fixed switch rules for CRS309 and CRS317 devices (introduced in v6.47.3);
*) defconf - fixed default configuration loading on RBmAP-2nD;
*) dhcpv4-client - fixed DHCP offer packet parsing with overload option present;
*) dhcpv6-server - properly save bindings when executing “make-static” command;
*) fetch - improved SSL handshake processing;
*) ike1 - allow using “my-id” parameter with XAuth;
*) leds - fixed LED type setting;
*) lora - expose “joinEui” un “devEui” values in the log;
*) lte - fixed multiple APN passthrough on R11e-4G;
*) lte - improved EARFCN reporting in 3G and LTE modes on Sierra modems;
*) lte - limit allowed APN count to 3 on R11e-LTE;
*) mpls - fixed duplicate “LabelRelease” message sending;
*) ospf - optimized LSA printing for smaller message sizes;
*) radius - added “Service-Type” attribute to Access-Request for IPv4 and IPv6 DHCP servers;
*) smips - reduced RouterOS main package size;
*) switch - fixed Ethernet padding for small packets;
*) user - improved WinBox and The Dude authenticated session handling;
*) vrrp - made “password” parameter sensitive;
*) w60g - general stability and performance improvements;
*) wireless - added support for US FCC UNII-2 and Canada country profiles for NetMetal series devices;
*) wireless - fixed incorrect wireless capability information in association response frames;

What’s new in 6.47.5 (2020-Oct-08 06:48):

(factory only release)


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.

This is now suffering the log messages on default configuration script we had in testing before:

system;error;critical error while running customized default configuration script: expected end of command (line 1337 column 53)

This happens without wireless package only.

On the version 6.47.6 command repartition (e.g. “/partitions repartition partitions =2”) causes the router’s cyclic reboot (about every 10 seconds). On versions 6.47.x situation the same.
Reset didn’t help, I’ve been able to repare it only with netinstall
On the version 6.46.7 this command works correctly

model: 951Ui-2HnD
revision: r2
firmware-type: ar9344
factory-firmware: 6.46.1
current-firmware: 6.47.6
upgrade-firmware: 6.47.6

I am having the same issue.

interesting bug fixes for our wireless clients

HEX with latest firmware and ROS v6.47.6
Wireless package disabled.
mikro.png

Will this fix the high battery issue with mobile devices? this started with the 6.47 versions, up to 6.46 the battery drain was normal on phones and tablets, it went up to 4x with the 6.47 versions.

Could you elaborate on the w60g improvements?

“error while running customized default configuration script: expected end of command (line 1337 column 53)”

RB450Gx4, everything worked great for months until I updated to 6.47.6. Wireless package installed since forever but is obviously disabled.

Edit: I found this on the 6.48 thread, however: http://forum.mikrotik.com/t/v6-48beta-testing-is-released/141139/1

The defconf issue is already resolved. Fix will be included in the next RouterOS release.

And also fix the log naming as I have posted both here and to support email before. (fix it for the new v7 as an minimum)
http://forum.mikrotik.com/t/logging-prefix-is-a-mess-sup-105353-sup-144261-waiting-for-mt-to-support-rfc-5424/111067/1
3 years and nothing has been done!!!

Look at this line:

system;error;critical error while running customized default configuration script: expected end of command (line 1337 column 53)

Is this an error message or an critical message.

Look at how wiki describes syslog messages: https://en.wikipedia.org/wiki/Syslog

Value	Severity
0	Emergency
1	Alert
2	Critical
3	Error
4	Warning
5	Notice
6	Informational
7	Debug

I have never seen any other system messing up logging prefix the way MikroTik does it.

It’s a critical error :wink: With value 2 (2 and 3 binary and-ed together).

In 6.47.6, nothing has changed since my last post.

http://forum.mikrotik.com/t/v6-47-4-stable-is-released/143158/52

Fix the Mac table via snmp!!! Not only can the poe port not be managed via snmp, but the Mac table is now not correctly returned!!!

I see no improvement here. My Oneplus drains like crazy, but GF’s Nokia doesn’t seem to have problems.
On the laptops I don’t know, They are used with power adapter.

It has been resolved before!
I would hope that when such mistakes are made, they are added to the regression testing done before releasing a new version, especially in [stable].

I can confirm the w60g link instability problem is fixed, I upgraded the Wireless Wire link that was the least stable on 6.47.4 from 6.46.6 to 6.47.6 and it’s still stable.

Yes I agree how does this not get noticed? I just updated two of my 3011 and only one had this issue and that is the one that has wireless package disabled. So it might be related to that?

On my CCR1009-7G-1C-1S+
updating from 6.47.4 to 6.47.6 went without one hicup

On my CRS326-24G-2S+
updating from 6.47.1 [long term] to 6.47.6 [stable]

  1. software update … at the 2 minute mark – after the update – could not login into Winbox
  2. BUT waiting to the 3 minute mark succeeded in login into Winbox for Firmware update
  3. After firmware update no problem login into Winbox at the 1 minute mark :slight_smile:

Updated RB1100AHx4 half a day ago - so far, everything is running without any problems.