Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 6.45beta6 (2019-Mar-05 08:51):
Changes in this release:
*) bridge - fixed possible memory leak when using “ingress-filtering=yes” on bridge interface;
*) certificate - added support for ECC (Elliptic Curve Cryptography);
*) certificate - force 3DES encryption for P12 certificate export;
*) crs3xx - correctly display auto-negotiation information for SFP/SFP+ interfaces in 1Gbps rate;
*) crs3xx - fixed auto negotiation when 2-pair twisted cable is used (downshift feature);
*) dhcp - fixed dual stack queue addition;
*) dhcpv4-server - added “vendor-class-id” matcher (CLI only);
*) dhcpv6-server - use MAC address for RADIUS user when “allow-dual-stack-queue=yes”;
*) ethernet - added support for 25Gbps and 40Gbps rates;
*) fetch - improved user policy lookup;
*) gps - increase precision for dd format;
*) ipsec - fixed dynamic L2TP peer and identity configuration missing after reboot (introduced in v6.44);
*) ipsec - use “remote-id=ignore” for dynamic L2TP configuration (introduced in v6.44);
*) ipv6 - do not allow setting “preferred-lifetime” longer than “valid-lifetime”;
*) lte - added passthrough interface subnet selection;
*) lte - added support for manual operator selection;
*) lte - do not show error message for info commands that are not supported;
*) lte - do not show “session-uptime” if session is not up;
*) lte - improved R11e-4G modem operation;
*) lte - renamed firmware upgrade “path” command to “firmware-file” (CLI only);
*) lte - reset LTE modem only when SIM slot is changed on dual SIM slot devices;
*) lte - show alphanumeric value for operator info;
*) lte - show correct firmware revision after firmware upgrade;
*) lte - use secondary DNS for DNS server configuration;
*) ppp - added initial support for Quectel BG96;
*) rb4011 - fixed ether10 failing to auto negotiate link speed to 1Gbps;
*) sfp - fixed S-35LC20D transceiver DDMI readouts after reboot;
*) sms - improved delivery report logging;
*) snmp - added “dot1dStpPortTable” OID;
*) ssh - use correct user when “output-to-file” parameter is used;
*) switch - fixed possible crash when interface state changes and DHCP Snooping is enabled;
*) tile - improved link fault detection on SFP+ ports;
*) winbox - added “use-local-address” parameter in “IP/Cloud” menus;
*) wireless - fixed incorrect IP header for RADIUS accounting packet;
*) wireless - updated “india” regulatory domain information;
*) wireless - updated “new zealand” regulatory domain information;
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.
*) bridge - fixed possible memory leak when using “ingress-filtering=yes” on bridge interface;
How did this bug manifest itself?? Been using this setup for a while and didnt notice any issues, on the other hand I dont really monitor that closely.
is there any chance to add some internal variables to dhcp-server alert script? like in dhcp-client script.
need to send alerts with mac and ip to messengers and some APIs..
I reported this problem to mt support.
It occured on my CCR1009 when vlan-filtering was enabled and frame-types set to admit-only-vlan-tagged.
In 24h it filled up the 2GB RAM ending in a kernel panic / reboot
6.45beta6 seems to have fixed this issue.
Waiting fix for BGP Withdraw on multihoming PE-CE, mt said must rewrite bgp module, so do it ASAP it’s a very important matter.
this issue not exist on other brand router and it’s use more than 10 years software.
A lot of mikrotik device running mpls now and a lot of them on production.
6.45beta6 kills SPF+ port in RB4011iGS+5HacQ2HnD-IN.
I’m using the Maxxwave MW-SX+MM-US in the SFP+ port of the RB4011iGS+5HacQ2HnD-IN. With 6.45beta6 the SFP tab under interface its all empty and SFP+ is not functional. Tried a different Maxxwave MW-SX+MM-US and same issue.
Downgraded to 6.44 (Stable) and SFP tab under interface is filled up correctly and Maxxwave MW-SX+MM-US is normally functioning.
Also, 6.45beta6 in CCR1016-12S-1S+ with Maxxwave MW-SX+MM-US in the SFP+ port works fine.
There are .ax Chipsets available for a while now. I guess all WISP vendors do at least some testing in Lab now. So they have to touch wireless package to make them work.
Don´t cry for next new Hardware, we had to wait over 12 Month for new Arm Chipsets to get running in most cases, most here had buyed 802.11n Hardware until there is no working 802.11ac available from Mikrotik, Wave2 is completely unsupported (most available devices from MT has Wave 2 Chipset).
So don´t cry for something new, cry for something working.
You probably wont see MT to tweak Wifi-HW to an extend where it will be realy good for WISP usage (HW-accelerated TDMA, GPS-Sync …). With .ac you are more or less limited to what the chipvendor does to get higher performance (plain 802.11 mode with rts/cts). So the only senseful option at the moment is to shop where this tweaking has bin done (anyone still did not manage to realize this?).
With 802.11ax the chipsetvendors have to put a lot of stuff into the chipset which helps WISPs. There is Scheduling, there is OFDMA. MT do not have to implement it. It is just there and it is vendor neutral. This is the way to go as fast as possible.
And this features will not work without working driver, and since MT write there own Drivers this features need to implement.
With own Drivers there is nothing out of Box from the chipset.
