v6.46beta [testing] is released!

Version 6.46beta6 has been 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.46beta6 (2019-Jul-04 11:53):

Changes in this release:

*) cloud - properly stop “time-zone-autodetect” after disable;
*) conntrack - properly start manually enabled connection tracking;
*) dhcpv6-server - made “calling-station-id” contain MAC address if DUID contains it;
*) fetch - improved stability when processing large output data;
*) hotspot - fixed non-local NAT redirection to port TCP/64873;
*) ipsec - improved stability for peer initialization (introduced in v6.45);
*) lte - do not allow setting 3G and GSM modes on LTE only modems;
*) lte - show “primary-band” only for LTE modems;
*) radius - fixed “User-Password” encoding (introduced in v6.45);
*) tr069-client - reconnect to ACS when “ConnectionRequestURL” is updated;
*) w60g - added “region” setting to limit allowed frequencies (CLI only);

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 expected or after crash.

My IPSec issues persist. (Though there are no more crashes.) Sent a reply with support output file to Ticket#2019070222004609.

DHCPv6 PD from radius works again. Thanks.

Hi

What was the issue here?

hotspot - fixed non-local NAT redirection to port TCP/64873

Thanks

CEPT has opened from 57 to 71 GHz, in the next ros release we can hope to have more channel or che radio chipset is ilimited up to 66?
Thank you

any chance to continue developing dude ?

sadly CEPT =/= local regulator

…and the 5Ghz wireless is still broken on RB4011 :mrgreen:

:mrgreen: :laughing:

Wishes for 6.46:

  • WinBox => CAPsMAN: Reboot button for CAPs
  • Will the new wireless driver package already be available?

Yes, I agree. It is annoying in CAPsMAN network to manual restart every AP. APs are updated automatically from CAPsMAN, and all APs have firmware autoupdate=yes, but still required additional manual restart for firmware update.

+1 for that

not strictly a [testing] topic, but the routerboot changelog looks kinda deserted:

https://wiki.mikrotik.com/wiki/RouterBOOT_changelog

now since 6.3-something the routerboot numbering is according to routerOS releases, its version keep on increasing, and we (or I) don’t know what has been changed, etc.
since the routerboot upgrade process requires an additional reload, i’d like to know whether it is worth doing it, or we can safely wait until the unit is restarted by something/somebody else.

I do agree that its not clear at all when to upgrade the routerboot. It should be listed at every new software if some are changed or not.
And the old paged should be updated or removed.

Other example:
https://wiki.mikrotik.com/wiki/Manual:Lua
It this page valid or not???

It is:

RouterOS v4 RC1 removes Lua support indefinetly

Then there are no need to keep the site :slight_smile:

They leaved clear that wiki’s page will not be updated…
But would be great to know the changes for every RBoot version, even if they are bump version.

Hi Folks,

Has been a long time since I have post here, but I need a help now!

Does mikrotik already support Openvpn with tls? This is because we need to use NORDVPN here in brazil and its a hard time doing it, so, please could you guys solve this problem to enable us to start to sell thousand of devices here by using nordvpn to override some internet problems???

Please advise @edmunds and others.

“ipsec - improved stability for peer initialization (introduced in v6.45);” Thanks for this Fix

System → AutoUpgrade not working since 6.45.x and later.

I have set up a ‘upgrade package source’ in our local network. Routers trying to access this source but always end up with ‘system, error, critical login failure for user xyz’.
There is no issue with 6.44 and earlier

Anyone else can repro this issue?