RouterOS version 6.49.10 has been released in the "v6 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.49.10 (2023-Sep-15 08:06):

*) www - improved service stability when receiving malformed 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 a router is not working as suspected or after some problem has appeared on the device

Please keep this forum topic strictly related to this particular RouterOS release.

*) www - improved service stability when receiving malformed packets;

Please release this same version as long-term.

Considering the actual state of v6(no-new features being added), MikroTik should sync all the releases of stable and long-term.
Some kind of freezing state, tying up both channels.

It would avoid misunderstandings of what is the purpose of correcting issues and new features.

Actually ROS6 is like the long-term version.

Regards.

Actually ROS6 is like the long-term version.

Factually yes. Technically no, if one has a device running v6 and channel set to long-term, 6.49.10 won't get installed (yet) even though 6.49.9 was declared as long-term at some point in the past.

The question is then: does MT QC staff feel that 6.49.10 might break something and they thus want to wait a week or three (to see if there's any negative feedback) before promoting the same version to long-term as well? Or is it only an oversight (as @fischerdouglas seems to think/fear)?

I understand your point, and it's an interesting question, so, in case that the answer would will be it's to make sure that nothing will break, it seems to be more like than "beta" instead of something "stable", in my opinion.

ROS 6 has been turned a bit weird, and the problem it's that much (I believe) people don't upgrade to ROS 7 due stability/functionality with the current config in their devices, that is comprensible.

For now maybe is best upgrading to stable channel with ROS 6 if you want get updates more quickly doing a manual update, of course by your own risk.

Regards.

@EdPa

Could you elaborate more what "stability when receiving malformed packets" means?

@EdPa

Could you elaborate more what "stability when receiving malformed packets" means?

That was my question also............. what precipitated the change, an edge case or something that affects general use???

Probably some minor vulnerability that makes the web-server crash

They can't write it clearly that if <censored> and then it happens <censored>.
Otherwise they would automatically reveal how to hack this still unknown bug...

However, the stupidity of opening the www or www-ssl ports to the world remains.
The default firewall rules prevent any such hack outside the internal network.

@EdPa

Could you elaborate more what "stability when receiving malformed packets" means?

This almost certainly means DoS / RCE from exposed www service. "Stability" in Mikrotik-speak means crashes.

Does it also come as long-term version ?

Does it also come as long-term version ?

Not yet. See post #4 above for further explanation.

I don't know why but after I update to6.49.10 and a reboot and upgraded the routerboard my Mikrotik Hap-AC3 died!
Only thing I could see was that the LAN icon in the front of the mikrotik flashed. Nothing else.

I had to reset the mikrotik and restore from backup.

The 6.49.10 has been promoted to the long-term channel.

Thanks! Next up long term 7.X ??

Back when 6.49.10 was stable
I got errors on the interfaces on my RB4011 (Rx Code Error)
And accordingly the interfaces jumped Down/Up
Rolled back to 6.49.8, and the problem went away

Perhaps this is an individual case

I have a hAP AC2 that refuses to upgrade. The upgrade worked fine on about 15 other devices, but the AC2 downloads the update, reboots, and then just comes up with 6.49.8 again. No mention of any upgrade in the logs whatsoever. Storage failure or something?

Netinstall

Hello
Since 6.49.10 i have troubles streaming my Cams in Homekit when i am outside from my Home (i.e. LTE or external WLAN).
Can this caused by the new enhancement: "www - improved service stability when receiving malformed packets;" ?
br, Richard

The enhancement is supposed to be only about service, provided by router itself (i.e. webfig). It shouldn't have anything to do with forwarded traffic (e.g. between your webcams and internet).

Hello
Since 6.49.10 i have troubles streaming my Cams in Homekit when i am outside from my Home (i.e. LTE or external WLAN).
Can this caused by the new enhancement: "www - improved service stability when receiving malformed packets;" ?
br, Richard

Everything is possible.
Since there is no log 6.49.9
And in 6.49.10 there are clearly some errors (Rx Code Error)
See Rx Stats/Tx Stats tabs on the WAN interface

This can be individual

Firmware and Software is on 6.49.10 .. ist there a way back for both ? or is only a software rollback necessary ? (sorry, it is my first time for a potential rollback) :-)
btw: it's also a RB4011iGS+5HacQ2HnD-IN ... but no errors RX or TX on the interfaces ?!?

Firmware and Software is on 6.49.10 .. ist there a way back for both ? or is only a software rollback necessary ? (sorry, it is my first time for a potential rollback) :-)

First, contact support and find out what exactly the problem is. (support@mikrotik.com or https://help.mikrotik.com/servicedesk/)
Send them supout.rif file

If the problem is confirmed
They will help resolve this issue

OK, created a support case :-)
thx !

OK, created a support case :-)
thx !

I have submitted a ticket (SUP-128685) 5 days ago with no response so far... as this is my first ticket with Mikrotik, what are the normal turnaround times here?
PS: Ticket done/closed ... was not a mikrotik related problem ;-)