v6.45.9 [long-term] is released!

RouterOS version 6.45.9 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.45.9 (2020-Apr-30 10:25):

Changes since 6.45.8:

*) arm - improved watchdog and kernel panic reporting in log after reboots on RB3011 and IPQ4018/IPQ4019 devices (“/system routerboard upgrade” required);
*) capsman - fixed “certificate” parameter updating on CAP;
*) certificate - fixed certificate verification when flushing CRL’s;
*) chr - added support for file system quiescing;
*) chr - enabled support for VMBus protocol version 4.1;
*) chr - improved system stability when running CHR on Hyper-V;
*) console - prevent incorrect type interfaces appearing in command hints;
*) crs3xx - fixed frame forwarding after disabling/enabling bridge hardware offloading for CRS354-48G-4S+2Q+ device;
*) crs3xx - fixed interface statistics for CRS354-48G-4S+2Q+ and CRS354-48P-4S+2Q+ devices;
*) crs3xx - fixed switch rule “dst-port” parameter for IPv6 traffic on CRS305-1G-4S+, CRS326-24G-2S+, CRS328-24P-4S+, CRS328-4C-20S-4S+, netPower 15FR devices;
*) crs3xx - improved SFP+ DAC cable initialization for CRS326-24S+2Q+ device;
*) defconf - added welcome note with common first steps for new users;
*) discovery - do not send CDP and LLDP packets on interfaces that does not have MAC address;
*) health - fixed maximum SFP temperature reading under ‘/system health’ menu;
*) hotspot - fixed redirect to log in page (introduced in v6.45);
*) ike1 - rekey phase 1 rekeying as responder for Windows initiators;
*) ipsec - improved system stability when handling fragmented packets;
*) led - added “dark-mode” functionality for CRS105-5S-FB;
*) lte - added “phy-cellid” value support for LTE-US;
*) lte - fixed IP type selection from APN on RBSXTLTE3-7;
*) lte - improved system stability when performing firmware update on R11e-LTE6;
*) sniffer - fixed minor typo in “host” menu;
*) snmp - fixed “ifSpeed” reporting for tunnel interfaces;
*) snmp - fixed “routeros-version” value returning from registration table;
*) snmp - fixed UPS battery voltage value scaling;
*) ssh - added support for RSA keys with SHA256 hash (RFC8332);
*) system - correctly handle Generic Receive Offloading (GRO) for MPLS traffic;
*) system - improved system stability when forwarding traffic from switch chip to CPU (introduced in v6.43);
*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
*) traceroute - improved stability when invalid packet is received;
*) webfig - added default configuration confirmation window to WebFig;
*) webfig - allow skin designing without “ftp” and “sensitive” policies;
*) webfig - do not show WebFig menu when opening ‘Check For Updates’ in Quick Set;
*) winbox - added “Options” parameter support for DHCPv6 client and server;
*) winbox - added 160Mhz extension channel support for CAPsMAN;
*) winbox - added support for “Tools->WoL” menu;
*) winbox - do not show “Revision” parameter under “System/RouterBOARD” menu on devices that have only one revision;
*) winbox - fixed “ARP” parameter inheritance from “CAPs Configuration” configuration;
*) winbox - fixed “Bands” parameter display for LTE interfaces;
*) winbox - fixed “DSCP” parameter value setting;
*) winbox - fixed “Frequency” and “Secondary Frequency” parameter inheritance from “CAPs Channel” configuration;
*) winbox - fixed “Passthr. MAC Address” parameter display “LTE APNs” menu;
*) winbox - fixed “Switch” menu on CRS354-48P-4S+2Q+;
*) winbox - fixed “dst-port” unsetting in “IP->Hotspot->Walled Garden” menu;
*) winbox - fixed “invalid” flag presence under “System/Certificates/CRL” menu;
*) winbox - fixed automatic “IPv6->Firewall->Address List” table update;
*) winbox - increased limit of multi-entry fields to 100;
*) winbox - made “none” the default value for “Security Profile” parameter when creating a new “Wirelees->Connect list” entry;
*) winbox - renamed “Memory used” to “HDD used” for HDD type under “Tools->Graphing->Resource Graphs”;
*) winbox - renamed “Routerboard” to “RouterBOARD” under “System/RouterBOARD” menu;
*) winbox - show “System/RouterBOARD/Mode Button” on devices that have such feature;
*) wireless - added “skip-dfs-channels” parameter;
*) wireless - allow using FCC “U-NII-2” frequency range for hAP ac2 and RBwAPGR series devices;
*) wireless - fixed default “antenna-gain” setting on SXT 2 devices;
*) wireless - improved 5GHz interface stability on RB4011iGS+5HacQ2HnD and Audience;
*) wireless - improved compatibility for “ETSI” wireless country profile;
*) wireless - improved system stability on hAP ac^2;
*) wireless - updated “bangladesh” regulatory domain information;
*) wireless - updated “indonesia4” regulatory domain information;
*) wireless - updated “south africa” regulatory domain information;

For a full changelog please visit https://mikrotik.com/download/changelogs

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.

Skins in web-interface stopped working after upgrading to 6.45.9. Checked on 2 different architecture routers.
If the skin is assigned to a specific group (read only for example), a user of this group after login to web interface will see all elements, even the ones that were deselected in skin. If the skin is selected manually in Design Skin menu, everything looks ok for this user.

Is it just for us or not?

How comes 6.45.9 contains a fix for something introduced in 6.46? In case the bug was “backported” from 6.46 it would be good to know what 6.45.x versions are affected.

There’s obvious probability of it being present at least in 6.45.8 as it was released after 6.46. Then again as 6.44.6 was released before 6.46, so it is quite probable, that 6.45.8 is the only one affected in long-term tree - presuming “introduced” is pointing to right version…

Sorry for the confusion. The fix was backported to 6.45.9 by mistake, but the fix does not cause any harm. There is no issue with shutdown execution on Hyper-V before 6.46. I will remove the entry from changelog.

Sorry, but are where any news about OSPF stability in this release?
Especially with OSPF MD5 auth…

Someone tested this on ARM platform yet? hAP AC2 ? How is compared with 6.45.6 Stable for ex?

Updated one of my hap ac² which is used as a switch and AP. No issues so far, I’m getting ~300 Mbps TCP download speed on a 5GHz 2x2 device while it used to be in the 200-250 Mbps range before (6.45.8 long-term). Still not as fast as the competition, but it looks like an improvement.

hAP ac² + Dell Vostro 7590 (Intel® Wireless-AC 9560)
mt_min_6.45.9_2.JPG
mt_max_6.45.9.JPG
mt_max_6.45.9_2.JPG
mt_min_6.45.9.JPG

Is that with or without capsman? What’s your result with a single TCP stream?

What meen this? I dont understand.. Improvment or downgrade from what version? Explain.

Clear improvement regarding LT 6.44.6
max.JPG
8m.JPG

Upgraded my hAP ac2. All seems fine. Not experienced issues. Seems stable.

Long-term v6.45.9 broke both 2.4 and 5GHz wifi on wAP ac (RBwAPG-5HacT2HnD). It simply refuses to boot up after Netinstall.
Repeated Netinstall process produces same result.

Back down to Stable V6.46.6, and it’s working again.

(My wAp ac running as CAP under RB493G as CAPSMAN. Have not been able to upgrade firmware on wAP ac except via Netinstall).

MTeeker That must be something specific to your particular unit. We have 8 wAP ac units here also running as CAPs, successfully upgraded all of them to 6.45.9 from 6.45.8 two days ago (both RouterOS and RouterBOOT), no problems so far.

You wrote “Back down to Stable V6.46.6”, so I guess you tried switching to 6.45.9 from 6.46.6. Do you have RouterBOOT also upgraded to 6.46.6?

It’s good to know that it only happened on my box, given your successes on eight other wAP ac’s.

As a matter of fact, I upgraded routerBOOT to 6.46.6 earlier when I flashed v6.46.6. RouterBOOT remained 6.46.6 when I tried 6.45.9. Not sure if this was the cause of my failure.

Lastly, are you able to upgrade firmware on your wAP ac normally. For some reason, I have not been able to. Henece Netinstall. And I have not been able to find out why.

Regards,
MTeeker

Absolutely. Upgraded RouterOS on all 8 units from CAPsMAN, and once they all came back online rebooted once again to upgrade RouterBOOT (they all have /system routerboard settings set auto-upgrade=yes). All went smoothly.

Gonna throw this up in the lab but any updates on the weird OSPF issues that were introduced 6.44.6 and upwards ? We had to go back to 6.44.5 as we’d get adjacencies seemingly stuck . Only thing that brought it back was either disabling/re-enabling the instance or rebooting the router.

Do you test it for OSPF problems or no? I don`t understand.

Busy testing at the moment to see if I can reproduce the issue that happened in 6.44.6 on 6.45.9
We had routers with adjacency for weeks running that would all of a sudden start acting up.