MikroTik

RouterOS version 6.42.10 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.42.10 (2018-Nov-14 15:04):

MAJOR CHANGES IN v6.42.10:
----------------------
!) upgrade - release channels renamed - "bugfix" to "long-term", "current" to "stable" and "release candidate" to "testing";
!) upgrade - "testing" release channel now can contain "beta" together with "release-candidate" versions;
----------------------

*) bridge - do not learn untagged frames when filtering only tagged packets;
*) bridge - fixed possible memory leak when VLAN filtering is used;
*) bridge - improved packet handling when hardware offloading is being disabled;
*) bridge - properly disable dynamic CAP interfaces;
*) certificate - fixed time zone adjustment for SCEP requests;
*) crs328 - improved link status update on disabled SFP and SFP+ interfaces;
*) crs328 - improved link status update on disabled SFP+ interface when using DAC;
*) crs3xx - fixed possible memory leak when disabling bridge interface;
*) defconf - automatically accept default configuration if reset done by holding button;
*) defconf - properly load default configuration after reset (introduced in v6.42.9);
*) health - fixed bad voltage readings on RB493G;
*) ipsec - fixed hw-aead (H) flag presence under Installed SAs on startup;
*) ipsec - improved stability when uninstalling multiple SAs at once;
*) ipsec - properly update warnings under peer menu;
*) led - added "dark-mode" functionality for LHG and LDF series devices;
*) led - fixed default LED configuration for SXT LTE kit and wAP 60G AP devices;
*) led - fixed power LED turning on after reboot when "dark-mode" is used;
*) ntp - fixed possible NTP server stuck in "started" state;
*) ospf - improved stability while handling type-5 LSAs;
*) romon - improved packet processing when MTU in path is lower than 1500;
*) routerboard - renamed SIM slots to "a" and "b" on SXT LTE kit;
*) routerboard - show "boot-os" and "force-backup-booter" options only on devices that have such feature;
*) timezone - updated timezone information from tzdata2018g release;
*) traffic-flow - fixed post NAT port reporting;
*) traffic-flow - fixed "src-mac-address" and added "post-src-mac-address" fields;
*) tunnel - made "ipsec-secret" parameter sensitive;
*) usb - fixed power-reset for hAP ac^2 devices;
*) w60g - fixed misleading license level requirement log message;
*) w60g - fixed "scan" functionality when in bridge mode;
*) w60g - renamed "frequency-list" to "scan-list";
*) winbox - allow to specify SIM slot on LtAP mini;
*) winbox - enabled "fast-forward" by default when adding new bridge;
*) winbox - show "System/Health" only on boards that have health monitoring;
*) winbox - show "W60G" wireless tab on wAP 60G AP;

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.

Thank you very much for this! With the bridge VLAN filtering memory leak fix, we can now test this for rollout on our network to replace the older 6.40.x long-term release.

What is about 2018101022007579?
support don't respond the second week
CCR still crash from EOIP packets

Thank you to the Mikrotik team for getting this "Long-Term" release out.

It solves some pain we were experiencing due to the Traffic Flow NAT bug.

A nice Thanksgiving week surprise! Happy holiday and God bless.

It solves some pain we were experiencing due to the Traffic Flow NAT bug.

Could you please provide more information about this bug?

anuser - IPFIX Traffic Flow did not report post NAT src/dst ports on some platform RouterBOARDs

Finally, thank you for sharing this wonderful news and the tips before upgrading.
Things need to be upgraded to be able to make it the competitions nowadays. I am currently working on redesigning Petstreetmall, but you can still purchase products such as heated pet beds which is perfect since it is starting to get cold.

cloud.mikrotik.com is very bad and slow resourse When Long term switches to cloud2.mikrotik.com?

The bridge VLAN filtering memory leak yet not fixed in CRS-226-24G-2s+

I can't update an RB4011 with this version. RB4011 states the minimum supported is 6.43.

I can't update an RB4011 with this version. RB4011 states the minimum supported is 6.43.

You can not downgrade below factory firmware.

Daylight Saving Time Offset for Europe/Dublin is +2:00, should it be 0:00, the same as London

Hi every one
I have a problem with 6.42.10 long term and I had with 6.43 too.
I have some mangles for route traffic for internet gateway, have 3 internet lines. Also using MK for dns too.
The problem is that when I update the ROS to 6.42.10 or 6.43 there will be a connection to all DNS IP addresses from every interface with no mangle like sstp or l2dp or Ethernet , although I have a rule in route that says the gateway for dns is what interface, BUT when I downgrade to 6.40.9 the problem is solved.
Maybe the route is not working. What is wrong with my config ?
You can see in picture.

Hi every one
I have a problem with 6.42.10 long term and I had with 6.43 too.
I have some mangles for route traffic for internet gateway, have 3 internet lines. Also using MK for dns too.
The problem is that when I update the ROS to 6.42.10 or 6.43 there will be a connection to all DNS IP addresses from every interface with no mangle like sstp or l2dp or Ethernet , although I have a rule in route that says the gateway for dns is what interface, BUT when I downgrade to 6.40.9 the problem is solved.
Maybe the route is not working. What is wrong with my config ?
You can see in picture.

Mind sending the Mangles/Routing rules/Routes as well?

Hi every one
I have a problem with 6.42.10 long term and I had with 6.43 too.
I have some mangles for route traffic for internet gateway, have 3 internet lines. Also using MK for dns too.
The problem is that when I update the ROS to 6.42.10 or 6.43 there will be a connection to all DNS IP addresses from every interface with no mangle like sstp or l2dp or Ethernet , although I have a rule in route that says the gateway for dns is what interface, BUT when I downgrade to 6.40.9 the problem is solved.
Maybe the route is not working. What is wrong with my config ?
You can see in picture.

Mind sending the Mangles/Routing rules/Routes as well?

Happy to see somebody care about my problem.

@MirhosseiniAmir could you please create a new topic for your question?

This problem is not related to this specific release (6.42.10).

Please do not post screenshots but state your issue as clear as possible, with examples, and with a configuration export ( Terminal > /export hide-sensitive ).

problem with this version on cloud system on rb750 and rb951. after update both ros and firmware cloud system stuck to previous public ip not properly recognizing new public ip and could not update mikrotik dns!!! had to upgrade to stable (6.43.7) to make it work again. STAY AWAY from this version if you manage remote systems which you cannot physically connect to router or you will be locked out!!!!

problem with this version on cloud system on rb750 and rb951.

That sounds like typical issue which happens, when you upgrade/downgrade without disabling cloud first. Recommended fix from staff: upgrade/downgrade back to original version, disable cloud, upgrade/downgrade to your target version, enable cloud.
There will be plenty of people like you nowadays as Long-Term is stuck on 6.42.x and uses old cloud, while Stable is 6.43.x and uses new cloud2. Those two clouds are not compatible and they do not override each other correctly as I suggested. On early release of 6.43, everyone was aware. Now, less and less people will know and this situation will become daily bread for everyone here on forum

problem with this version on cloud system on rb750 and rb951.

That sounds like typical issue which happens, when you upgrade/downgrade without disabling cloud first.

since when?
that has never happened to me from the time mikrotik implemented cloud system, accross ros updates. thats why it was so weird to me. and then why it recovered by upgrading it to next stable version? maybe mikrotik developers should put a script to disable cloud before upgrade and re enable it after if this causes a problem user cannot make a guess if this is going to crash after because it was enabled.

v6.43 includes changes for new IP/Cloud services. As mentioned in v6.43 changelog - you should disable Cloud DDNS service before an upgrade to v6.43 or later or before a downgrade below v6.43. With disabling DDNS you unregister device from cloud. Then after upgrade or downgrade you can re-enable Cloud services and re-register your device on it. This is how you make sure that your router is registered only on the new or old Cloud.

... you should disable Cloud DDNS service before an upgrade to v6.43 or later or before a downgrade below v6.43 ...

@strods: As I pointed out in previous text, this issue will happen more and more often, because people will migrate between Long-term and Stable without knowledge what was in 6.43 changelog. Keep in mind this is very unusual compatibility break. Could you please suggest to your colleagues to implement cloud differently, so this kind of issues cannot possibly occur?
My suggestion is following:
- when RB sends update to old cloud: update the value in old cloud + send background request from old cloud to new cloud2 to disable and delete entry in new cloud2
- when RB sends update to new cloud: update the value in new cloud2 + send background request from new cloud2 to old cloud to disable and delete entry in old cloud
This way, only latest entry will be pushed to DNS and you will prevent many people reporting this behavior as a bug, both here and on support email.
In the end, it might actually save your company more time, than it will be spent on implementing such feature.

but.... i did not upgraded directly to stable (6.43). i was on bugfix (6.42) and upgraded to long term when ddyns stopped working. without further actions of disabling cloud i then upgraded to stable and cloud came to life again.

Hello,

the wireless interface does not show the security-profile option when it uses nv2 protocol.
The problem is that the security-profile must be specified if it works with radius authentication even if nv2 uses its own "security".

Hello Folks!

Worked like a charm!
Thanks to that we are back patching again, at least for devices with clock speeds 300MHz+, those older devices has issues with 6.41.3+ versions.

There are still issues with low capacity in WiFi compared to other brands, but it is rock solid at our sites, below 80-100Mbit/s for p2mp NV2 using AC, hope this get fixed at some point. I hope MT focus more on link stability ptp, p2mp and get the speed up to competitors levels.

Performing a stepwise upgrade for many devices with very low RoS and firmware (6.34.7->6.40.9->6.42.10), CRS125, CCR1009, CCR1016, RB333, PowerBOX, SXT, SEXTANT, QRT-5, RB711, RB600, RB800 and DynaDish all works and performs normally.

But overall, I am happy again.

New version 6.42.11 has been released in long-term RouterOS channel:

viewtopic.php?f=21&t=143805