MikroTik

RouterOS version 6.49.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.49.6 (2022-Apr-07 17:53):

*) led - fixed wireless signal strength led on Cube Lite60;
*) routerboot - fixed packet receiving in etherboot on Wireless Wire nRAY;
*) winbox - added missing "3GGP RAW" parameter under "Interface/Wireless/Interworking Profile" menu;
*) wireless - fixed GUD version in 3gpp information;

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.

hAP ac3 upgraded. All good

Updated SXT LTE Kit and hAP ac^2 from 6.49.5 to 6.49.6. No issues.

Still can't configure HT MCS for quad stream in CAPsMAN (/caps-man/rates/set 0 ht-supported-mcs=mcs-24,...), unlike outside CAPsMAN where it is possible (/interface/wireless/set 0 ht-supported-mcs=mcs-24,...).

Updated my RB4011 and Routerboard firmware from 6.49.5 to 6.49.6 . All went smooth and without issues.

Updated below models from 6.49.5 to 6.49.6. The up-gradation process went smoothly and didn't face any issues so far.

- 2 CCR-1036
- 3 RB4011
- 2 RB3011
- 1 RB2011
- 1 hAP ac3
- 1 hEX
- 1 RB450G

Was this meant to be the new long term release?
Why would you run the cube lite 60 and the wireless wire nray on anything but long term?

Updated soft- and firmware on these models without any issues:
RB4011iGS+
RB1100AHx4
RB750GL
RBD52G-5HacD2HnD (hAP ac2)
RBD25G-5HPacQD2HPnD (Audience)
CCR2004-1G-12S+2XS
CCR1009-7G-1C-1S+
CRS112-8P-4S
x86

The Dude Server is now inside Extra packages on already supported platforms.

Updated soft- and firmware on these models without any issues:
CCR2004-1G-12S+2XS

Did you a downgrade beyond the factory-firmware?
Our CCR2004's came with a pre-insalled V7...

Updated soft- and firmware on these models without any issues:
CCR2004-1G-12S+2XS

Did you a downgrade beyond the factory-firmware?
Our CCR2004's came with a pre-insalled V7...

No, I didn’t do a downgrade before. Our CCR2004s had version 6.x pre-installed.

Hi!
I did an upgrade of a few HEX PoEs, CAP ac, WAP ac, WAP R ac, CRS309, CRS305. 6.49.5 > 6.49.6 All went smooth.
The upgrade on my both HEXs boxes just failed first, then I realized, thats probably the result of the missing Dude package.
@MT:
1. I am probably not the only one using HEXs boxes as lightweight (fanless, low volume, and low power consumption) network monitoring/log server for small remote locations, so Dude is a very much appreciated feature, please don´t ignore it completely! (You still sell hardware made for Dude!)
2. Maybe ROS should give us a meaningful error message if a package is missing. (The upgrade hangs instead while showing something like "calculating download size".)

Thanks!

Any issue CCR1072 and GLC-T modules?

Hello,
I think Mikrotik has problems with czech words at the name of SSID. Ubiquity has no problems with czech diacritics like "přízemí" (ground floor).
UBNT shows on the other side same, like in setup. But I setup it on Mikrotik and the phone saw it like "p%9zem9" on new Galaxy A52. On the notebook Lenovo is ok.
Can you please fix it? Thank you :)

You have to use proper encoding for unicode. Try this:
https://r-1.ch/mikrotik-unicode-ssid-generator.php

You have to use proper encoding for unicode. Try this:
https://r-1.ch/mikrotik-unicode-ssid-generator.php

Thank you :)

Hello,
I think Mikrotik has problems with czech words at the name of SSID. Ubiquity has no problems with czech diacritics like "přízemí" (ground floor).
UBNT shows on the other side same, like in setup. But I setup it on Mikrotik and the phone saw it like "p%9zem9" on new Galaxy A52. On the notebook Lenovo is ok.
Can you please fix it? Thank you :)

There is also a long time ongoing issue of MikroTik mobile app, not only Czech characters, but every special characters (i.e. degrees °) used everywhere (mostly in comments in our case) are broken when you touch it (edit) via mobile app. I think it is related to your issue as well.

Have two CAP AC, both in bridge ac mode. Updating 6.49.3 to 6.49.6, first unit is ok, second one bricked. It happened second time in a row, before the same unit was bricked updating 6.49.2 to 6.49.3, have restored it with netinstall... Main router and Dude server on virtual windows PC updated ok.

What is going on? How to prevent this? It is pain in the neck to restore it from such crash. Never have problems with updating mikrotiks before, using them for year at home and my job.

Have two CAP AC, both in bridge ac mode. Updating 6.49.3 to 6.49.6, first unit is ok, second one bricked. It happened second time in a row, before the same unit was bricked updating 6.49.2 to 6.49.3, have restored it with netinstall... Main router and Dude server on virtual windows PC updated ok.

What is going on? How to prevent this? It is pain in the neck to restore it from such crash. Never have problems with updating mikrotiks before, using them for year at home and my job.

Hi SergeS,
I had the same issue with one device, it was a factory reject. Netinstall did not help. I just throw if out of a window after tenth brick.

Have two CAP AC, both in bridge ac mode. Updating 6.49.3 to 6.49.6, first unit is ok, second one bricked. It happened second time in a row, before the same unit was bricked updating 6.49.2 to 6.49.3, have restored it with netinstall... Main router and Dude server on virtual windows PC updated ok.

What is going on? How to prevent this? It is pain in the neck to restore it from such crash. Never have problems with updating mikrotiks before, using them for year at home and my job.

I had the same issue with one device, it was a factory reject. Netinstall did not help. I just throw if out of a window after tenth brick.

NitInstall helped me, twice. But I am looking for the way how to perform firmware update more traditional way.

NitInstall helped me, twice. But I am looking for the way how to perform firmware update more traditional way.

The same situation with hap ac2. Nothing helped. Idk what's the problem.

And in English that would be?
Using google translate

hello friends of the group, has it happened to someone that they have updated a RouterBOARD 750G r3 to version 6.49.6 and it stops saving configurations, that is, when it is turned off or restarted, it returns the last changes after the update. solution???

Hola Amigo! It's the only two words I know in Spanish! Welcome to our forum!

hola amigos del grupo, a alguno le a pasado que han actualizado una RouterBOARD 750G r3 a la versión 6.49.6 y deja de guardar configuraciones, es decir cuando se apaga o reinicia vuelve atrás los últimos cambios después de la actualización..Por favor alguna solución???

NY guess is out of storage. Have seen this as well on the same model.

Do Netinstall. And then restore your backup. 10 minutes total.

Hello. I am a new user of mikrotik hAP lite device with fw.6.49.6.
But on official site there are a new version 7 and also there is still old 6 version.
Can someone please, tell me should i upgrade my device to 7 version or there will be some new updates for 6 version?
I beg my pardon if there was answer already somewhere on site, did not find it.
Thank you all!

Hello. I am a new user of mikrotik hAP lite device with fw.6.49.6.
But on official site there are a new version 7 and also there is still old 6 version.
Can someone please, tell me should i upgrade my device to 7 version or there will be some new updates for 6 version?
I beg my pardon if there was answer already somewhere on site, did not find it.
Thank you all!

Hi
If you don't need BFD or some other not implemented options, then you can easily upgrade to v7.
You can check roadmap for v7 here.

Or better, do not install 7 on hAP lite, kep 6.49.6

Thank you all for answer!

Upgraded today successfully from 6.49.0 LtAP, PowerBox, BaseBox 2 and BaseBox 5.

I'm thinking that ROS 6 will be not receive more updates and all is for ROS 7. I'm not sure if I will do upgrade to ROS 7 yet.

Regards.

So, are ROS stable releases only v7 now ?

So, are ROS stable releases only v7 now ?

ROS6 Stable is also stable.
So is ROS6 Long Term.

Main focus will be on ROS7 but I suspect security issues will still be implemented in ROS6 as well.
There are far too many devices simply not capable of running ROS7 reliably, so I am not convinced they will drop ROS6 that soon.

There are far too many devices simply not capable of running ROS7 reliably, so I am not convinced they will drop ROS6 that soon.

the only device that can't run ROS7 reliably, in my experience, is the Hap-Lite/RB941/RB931.
i have ROS7 running on TILE, ARM, ARM64, mips, mmips, and PPC, and it's been very stable and performant so far (no OSPF, MPLS, BGP and PPPoE)

Dear MikroTik,

Can we have some clarity, apparently you do not recommend running v7 on mAP Lite:
https://help.mikrotik.com/docs/display/ ... ifications

Note: We do not recommend running v7 on RB411l, RB411u, or RBmAPL-2nD.

Is cAP Lite also affected as both devices are almost identical save the usb port: https://mikrotik.com/products/compare/R ... RBcAPL-2nD

Will you be recommending the mAP Lite stays on v6?

Will you be recommending the mAP Lite stays on v6?

Don't they dare ! It simply works and pretty well too !

But use that as base and then see how many devices have less resources then that small matchbox.
Quite a bit.

There are far too many devices simply not capable of running ROS7 reliably, so I am not convinced they will drop ROS6 that soon.

the only device that can't run ROS7 reliably, in my experience, is the Hap-Lite/RB941/RB931.
i have ROS7 running on TILE, ARM, ARM64, mips, mmips, and PPC, and it's been very stable and performant so far (no OSPF, MPLS, BGP and PPPoE)

RB751U-2HnD for sure. You can upgrade to v7, but it blow up the CPU then idle.

hAP Lite, hAP Lite TC and hAP mini are the weakest (SMIPS+32MB RAM) MT machines that I know. mAP Lite, and cAP Lite and hAP ac Lite, etc etc are totally different (MIPSBE)

Check https://mikrotik.com/products/matrix

Any Chance of new update for v6

What is missing or wrong in current v6 that would warrant a "new update for v6"?

Radius Attribute Fix for PPP Accounting which is not sending Delegated IPv6 Prefix!!!

Did you fix it? Or what is your post about?

There will be no more updates in version 6? Do I have to go to version 7?
EL DONCITO.

No, if v6 works fine and you do not need any of the new stuff added in v7.

No, if v6 works fine and you do not need any of the new stuff added in v7.

I can't agree more, its a mess and too busy fixing the bon-fires of V7 now up to 7.5 and crickets for V7 Long Term as its a never ending bug fix.

Hi,

I upgraded my routerboard in a 6hex to this release. Before it was I think v6.48.something. Since then, the temperature is higher by 7°, from 39°C to 46°C. is this something that can generally be observed? Should it trouble me?
in the CPU graphs I cannot see any change, perhaps since all kernels are reported seperately thus just a bit underground noise to be seen, no trend.

Hi,

Did someone had issue with PPTP after upgrading to this version?

Regards

It's time you use another protocol ...
Whatever, if you're no specific on what problem you have...

In 6.49 i've found some issue with expect scripting via telnet.
Right after sending password, terminal and session is closes unexpected.

Expect script:
```
#!/usr/bin/expect -f
set timeout 120
set env(TERM) dump
spawn telnet [lindex $argv 0]
expect "Login:"
send "[lindex $argv 2]+ct80w80h\r"
expect "Password:"
send "[lindex $argv 3]\r"
expect "*@*]*>"
send "/export file=config.rsc \r"
expect "*@*]*>"
send "/tool fetch address=[lindex $argv 1] dst-path=\"[lindex $argv 0].cfg\" src-path=config.rsc mode=ftp upload=yes user=\"user\" password=\"password\"\r"
expect "*@*]*>"
send "quit\r"
```
expect version 5.45.4

All routeros before 6.49 works fine.

Release 6.49.7
What's new in 6.49.7 (2022-Oct-11 17:37):

*) branding - fixed execution of "autorun.scr" file when installing branding package (introduced in v6.47);
*) routerboot - prevent enabling "protected-routerboot" on unsupported factory firmware versions;
*) routerboot - properly reset system configuration when protected bootloader is enabled and reset button used;
*) system - improved handling of user policies;
*) wireless - fixed disconnection of connected client while running background scan on wAP ac and wAP R ac devices;
*) wireless - fixed missing wireless interface on some RB921GS-5HPacD devices;

Good catch
I thought MT had stopped developing 6.x ;)

The list of changes certainly doesn't warrant a new topic announcing new stable release ... or does it, Mikrotik? Well, certailny doesn't touch anything I'm using on my MT devices, so I'll skip this release unless MT comes up with a different list of changes.
@Jotne, this is what you'd call "development"? It's bug fixing ... don't get me wrong, it is important, but let's call it what it is ... a maintenance release.

Works good on all our routers in the production networks.
But to be honest, its a sad upgrade, no extra thread and not even the new NetWatch was implemented.

Thats by far the saddest upgrade I have ever seen.

... not even the new NetWatch was implemented.

That would be new functionality, certainly not fit for a bug-fix release numbered 6.49.7 ... it would IMO warrant at least 6.50, but that's probably not gonna happen. I fully support MT for their full commitment to bring v7 to decent functionality and stability level.

On a quick note: the time interval between 6.49.6 (released 2022-04-13) and 6.49.7 (released 2022-10-13) is exactly 6 months ... the low number of items in change list might indicate that 6.49(.7) is ready to be "upgraded" to long-term release channel.

Works good on all our routers in the production networks.

This is not how to upgrade.
1. Upgrade to a version not have any public release.
2. Upgrade just some hour after first post about new version.

For a production network.
After any new release, wait some weeks. See what other writes about it on this forum. Do a test on a router not in production with same setup and hardware as in production. Then if all works and no big errors are reported, then you should do the upgrade. And only if new version has some new that you need or a bug fix that helps (could help) you to get a more stable network.

Someone has to be the guinea pig ...

New version v6.49.7 has been released:

viewtopic.php?t=189970