v6.42rc [release candidate] is released!

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.42rc2 (2017-Dec-27 07:37):
*) dude - fixed e-mail notifications when default port is not used;
*) firewall - fixed “tls-host” firewall matcher;
*) firewall - limited maximum “address-list-timeout” value to 35w3d13h13m56s;
*) routerboot - fixed missing upgrade firmware for “ar7240” devices;
*) tile - fixed USB device speed detection after reboot;
*) traffic-flow - do not count single extra packet per each flow;

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 crash.

Admire the spirit, Christmas period and you are releasing new (RC) version. But looking at changes 4 out of 6 are fixes so this sounds more like 6.41.1 not 6.42.

kamillo - Fixes must be tested on rc tree before they are included in full version. Otherwise each and every version would be beta.

Is there a chance to support boot from VirtIO-SCSI in this release of CHR?

No problem with upgrade from 6.41rc47 to 6.42rc2 on hAP ac lite and from 6.41rc66 to 6.42rc2 on CHR under VBox.

Can you give more details about this?

TLS-host does not work for me!

Cha0s - Before the fix Traffic Flow, for example, instead of reporting 5 packets per flow reported 6 packets. Simply reported one packet more than flow has actually processed;
irghost - Can you provide an example of rule which you have tried out and seen that it is not working?

Дома hAP ac стоит, 2 часа с бубном танцев не привели к получению интернета из одноимённого отверстия с данной прошивкой, как заколдованный, не найден тебе узел и всё тут. Ну, руки у меня кривые конечно, но остальные устройства автоматом завелись, а это - нет



/ip firewall filter add action=drop chain=forward protocol=tcp tls-host=*.youtube.com

i never figure out how to setup that, so i will be cool to have some exemple form MT support

*) dude - fixed e-mail notifications when default port is not used;
does it means that dude development is unfreezed?
what abount dude api?
We have strange issue:
we have device with one service but dude shows 2 services

I don’t think you can use wildcards. Or to put it more correctly, I think you should use the domains defined in the certificate.
Youtube’s certificate does not contain *.youtube.com

Hi, would it be possible to activate / enable / support “airtime fairness” for Atheros wireless chipsets within 6.42rc?

fenomen51 - Please note that most of the users in the forum do not know Russian language. I recommend to send this report to support@mikrotik.com and provide confguration of your router which you had before an upgrade. We will test if we can reproduce this problem;
irghost, raffav, Cha0s - Seems that we have found an issue with new TLS matcher. We will try to fix it as soon as possible;
alexspils - Please note that this was just a single fix. More fixes will be available in future RouterOS releases, but we can not promise any ETA for them;
alexspils, anuser and everyone else - If you have suggestions or bugs reports related to RouterOS, then either create a new support topic or contact support. We will be happy to hear you out. Version topics are made to find out issues with concrete version - see the feedback about concrete version. Main idea is to help to users who want to upgrade.

I think every new function SHOULD have some examples on proper usage.

Best regards and happy holidays!

add some documents

+1 .. We know documentation takes time, but the rc features cannot be really well tested w/o at least basic suggestions

@strods why isnt wiki thedude changelog not updated?

There is a backlog of items in the changelogs to be documented in the WiKi and when you look at the Hairpin Nat page it is 7 years old and there has been a change in RouterOS (local port incl. WanIP) that comes in handy for many users of RouterOS.

However there was today change in the IPSEC page which now has an clear table of which equipment is supporting which encryption and makes it all very clear and easy to understand. :slight_smile: