v6.47.9 [long-term] is released!

RouterOS version 6.47.9 has been released in public “long-term” 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.9 (2021-Feb-05 15:22):

Changes since 6.47.8:

*) bgp - fixed VPNV4 RD byte order;
*) branding - fixed LCD logo loading from new style branding package;
*) crs312 - fixed missing SwOS firmware on revision 2 devices;
*) crs3xx - correctly filter packets by L2MTU size;
*) crs3xx - improved system stability when receiving large frames for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (introduced in v6.47.5);
*) defconf - fixed default configuration loading on RBcAP-2nD and RBwAP-2nD;
*) hotspot - fixed “idle-timeout” usage with RADIUS authentication;
*) hotspot - fixed special character parsing in “target” variable (CVE-2021-3014);
*) package - do not include multiple The Dude packages in HDD installer;
*) snmp - fixed “send-trap” functionality;
*) webfig - fixed new interface addition;
*) winbox - fixed enable/disable button presence for “Bridge/Hosts” menu;
*) winbox - renamed IP protocol 41 to “ipv6-encap”;
*) winbox - show “System/Health” only on boards that have health monitoring;
*) winbox - use health values reported by gauges for “System/Health” menu;
*) wireless - renamed “macedonia” regulatory domain information to “north macedonia”;
*) wireless - updated “indonesia5” regulatory domain information;

For a full changelog please visit https://mikrotik.com/download/changelogs

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 specific RouterOS release.

Is DoH now part from longterm 6.47.9 (i am coming from 6.47.7 stable) ?
br, Richard

roe1974 - DoH support was already added in v6.47.

I cant see memory leak on DoH is in the fixed log!!!
Until its fixed, I do not recommend use DoH

what is this “memory leak” ?
I use DoH since 6.47 with more or less no problems… (ltAp, R4011)
br, Richard

Do a search in goolge (or at the forum) for “mikrotik doh memory leak”
Yes it work, but have a look of used memory every day and you see it goes up and down.

Eks
http://forum.mikrotik.com/t/v6-47-stable-is-released/140100/338

Thank you for promoting 6.47 to long term - had a lot of success with this release stream - has given me an opportunity to easily rollback/forward between 6.48.x while work continues - safe and easy fallback to 6.47 :slight_smile:

Got it installed on my RB4011/CRS112/2xcAP ac/wAP ac (coming from 6.478.1), will monitor. Upgrade went very smooth!

Totally concur!
Thank you!

I updated to this version and enabled DoH. So far everything seems to work as expected. Will keep an eye on the memory usage.

Awesome been waiting for the “real” stable release. Long term it is!!

Thank you for not breaking the IKE 2. On the stable version, dynamic connections with LTE, without real IP addresses disappear, I don’t know how to solve.

Bug (/system health) in WebFig and Winbox for the Mikrotik hEX RB750Gr3
Firmware v6.47.9
Bootloader v6.46.7
WebFig and Winbox
(/System health) from WebFig and Winbox does not display system voltage or system temperature
Terminal
(/system health print) does display system voltage and system temperature
Does the bootloader need to be updated?

Try rebooting to find out?
Your bootloader wasn’t even on latest for the 6.46 minor release; 6.46.8 was previous.

It’s hard to call this a bug for sure when your bootloader is a minor-release behind.

Upgraded firmware to v6.47.9 still no display from WebFig (/system health)

It’s been 84 years…
Have been waiting for long-term 6.47.X to release, so I could upgrade to it directly from stable 6.46.5 on RB760iGS and cAP AC, given how poor a lot of recent stable 6.47.X (and .48, oh man, oh god) releases were received. But, generally speaking, is it a good idea (meaning “is it safe?”) to do both things at the same time - to upgrade to next major version (from .46 to .47) and to hop to different release tree? Well, there are backups of course, so it’s just my curiousity itching.

I’ve been in a not-too-dissimilar boat.

I’ve been waiting for a good time to hop to long-term as well. I held off on the 6.48 jump really hoping 6.47 would get promoted to long-term. I’m glad i did. Just upgraded my whole infrastructure, some of it was on 6.47.8, the rest (wifi/caps) was all 6.46.8.

Now everything is happy all together on a single slow-moving and hopefully well-understood train. :slight_smile:

We live good with a very lazy update strategy. So we will install 6.46.8 for some months from now. As a long time MT user …

I was hoping for at least an 6.46.9 version if not more, with more fixes than with added features.. Oh well.

Hello,
Switch have broken sfp module after resetting to default switch CRS309-1G-8S+ with 6.47.9
We had similar situations with CRS326-24S+2Q+, after firmware upgrade UBNT 10g modules stopped working.

How to deal with such situation in future? It is not possible safely to upgrade o reset the switch. Has anyone similar experience?

Thanks, Albertas