MikroTik

*) winbox - allow to specify "any" as wireless "access-list" interface;

No, this was never changed. The only recent addition is that in /system routerboard settings it is now possible to
enable auto-updating of the firmware (curiously, it is disabled by default!).

When this option is enabled, immediately after boot the firmware version inside RouterOS is compared to the version
in the router, if different a firmware upgrade is done, the message that a reboot is required is logged as usual, but
no reboot is actually performed. So you still have to wait for the router to come up completely, login, and do the reboot.

It would be more friendly when the router would reboot automatically when it has done such an automatic firmware
upgrade (remember this happens before all the interfaces come up and interaction with other systems is started).

Just completed RB2011 from 6.42.1 to 6.42.2, all looks good so far, will monitor DHCP client issue and revert back.

Just one question though, I was under the impression it will no longer require to upgrade RoS and then after FW, i.e. requiring 2 reboots? I still had to upgrade routerboard firmware after ROS update, or do I have it wrong??

There are changes - related to new products.

*Please try to keep this topic strictly related to the problems which were not present in 6.42.1 and are in 6.42.2.

No NV2 changes in 6.42.2? There are enough topics with problems (6.42.1) ...

Upgraded from 6.41.2 on a CRS125-24G-1S to 6.42.1 yesterday and found this morning that "fasttrack" connections were dropping a large percentage of packets. Disabling the firewall rules that tagged the connection as fasttrack eliminated the packet loss. Upgraded to 6.42.2 today, and the problem still exists.

*) winbox - allow to specify "any" as wireless "access-list" interface;

So, what's the difference now between 'any' and 'all'?

hAP ac^2 - when willl you fix slow doawnload for 802.11ac?

uploading 400-500 Mbps
downloading - 200 Mbps...

IPsec on hAP ac2 is slowly compared to hEX

v6.42.2 fixes it, did you upgrade today with the new release?

Since firmware fixes for already existing products are very rare, we do not force upgrade on each reboot. Basically, if you do not see change in RouterOS changelog that tells "extra reboot required", there is no need for an upgrade.

We consider that it would not be a good idea to force upgrade and increase boot time significantly just so firmware would be upgraded. At the moment we are maintaining policy that:

1) We do not force upgrade;
2) If you really want to upgrade firmware every time, then either reboot device twice after RouterOS upgrade when auto-upgrade for RouterBOOT is enabled or do such process manually.

Currently implementing simultaneous upgrade would introduce more flaws than pros. However, of course we will always listen to customers complaints and ideas and will try to make upgrade and other processes in RouterOS/RouterBOOT as good as they can be in order to satisfy the biggest part of users.

*Please try to keep this topic strictly related to the problems which were not present in 6.42.1 and are in 6.42.2.

Currently implementing simultaneous upgrade would introduce more flaws than pros. However, of course we will always listen to customers complaints and ideas and will try to make upgrade and other processes in RouterOS/RouterBOOT as good as they can be in order to satisfy the biggest part of users.

disconnected, group key exchange timeout

disconnected, unicast key exchange timeout

Unfortunately it appears that IPv6 has broken.
I get a /48 prefix from the ISP using DHCPv6 and set addresses from the pool on 2 local interfaces, with advertise=yes.
Systems on these interfaces lose the default route after update from 6.42.1 to 6.42.2
After entering a manual default route the IPv6 connectivity works.
After releasing the IPv6 lease (and it automatically acquires it again) it works.
This problem has occurred in the distant past but it has returned.

*) winbox - allow to specify "any" as wireless "access-list" interface;

So, what's the difference now between 'any' and 'all'?

So why do we have one more option now? Do they behave in different ways?

Upgraded from 6.41.2 on a CRS125-24G-1S to 6.42.1 yesterday and found this morning that "fasttrack" connections were dropping a large percentage of packets. Disabling the firewall rules that tagged the connection as fasttrack eliminated the packet loss. Upgraded to 6.42.2 today, and the problem still exists.

RouterOS version 6.42.2 has been released in public "current" channel!

Before an upgrade:
...
3) Device has enough free storage space for all RouterOS packages to be downloaded.
...

@Chupaka
'Any' means any wireless interface
'All' is name of address list, which can also contain other interfaces (ethernet, SFP, etc.)

HTH,

IMO it's simple shortcut for those who don't want to create 'all-wireless-interfaces' list, nothing more.

Regards,

So, what's the difference now between 'any' and 'all'?

Be carefull, netwatch utility broken since 6.42.1. Up and down scripts does not execute.

...mentioned in the changelog.
And there has been a lot of discussion about it already!

netwatch utility broken since 6.42.1

Please, could you provide proof links?

Have you actually checked 6.42.1 topic?
search.php?keywords=netwatch&t=133535&sf=msgonly

Be carefull, netwatch utility broken since 6.42.1. Up and down scripts does not execute.

Be carefull, netwatch utility broken since 6.42.1. Up and down scripts does not execute.

/system scheduler
add disabled=yes interval=1m name=script1 on-event=\
    "/system scheduler disable script1\r\
    \n/system script run script1" policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-date=may/23/2018 start-time=00:00:00
add disabled=yes interval=1m name=script2 on-event=\
    "/system scheduler disable script2\r\
    \n/system script run script2" policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-date=may/23/2018 start-time=00:00:00

/system script
add name=script1 owner=admin policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=\
    "/log info \"script1 runs\""
add name=script2 owner=admin policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=\
    "/log info \"script2 runs\""

/tool netwatch
add down-script=\
    "/log info \"down, enable script2\"\r\
    \n/system scheduler enable script2" host=8.8.8.8 up-script=\
    "/log info \"up, enable script1\"\r\
    \n/system scheduler enable script1"

This update has bricked one of my HAP AC units to a reboot loop I had to use netinstall to restore it (first time for me)
After netinstall and upgrade everything seems fine

Thanks!

RB HEXr3 upgrade from 6.42 to 6.42.2
dude packet also active
Manual ugrade in windows dude.exe 6.42.2 , and cant log in
SAY: cant read database


edit

go back to 6.42.1 .. and again
cant read database .. well done mikrotik.. aaaaah

Hi
I wonder if VPNFilter malware threat is addressed in this release.
See https://www.symantec.com/blogs/threat-i ... ot-malware and https://blog.talosintelligence.com/2018 ... ilter.html for more details.

Apprently - it is not fixed in 6.42.2. I found logins as admin from different IPs allover the world to my CCRs1036 with 6.43rc11.
Moreover not only CCRs are affected as I found similar logins into my RB3011.

What is common - is that VPN server (pptp and l2tp) was enabled and accessible from internet on all affected devices.

Well first post says. Export and backup your config before upgrade In my undestanding that would include downloading dude database export to PC before upgrade.

Version 6.43rc17 has been released.
*) wireless - fixed wireless interface lockup after period of inactivity;
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;
*) wireless - improved client "channel-width" detection;

viewtopic.php?f=2&t=134713&p=663589#p663890