RouterOS version 6.45.3 has been released in public “stable” channel!
Before an upgrade:
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.45.3 (2019-Jul-29 12:11):
Important note!!!
Due to removal of compatibility with old version passwords in this version, downgrading to any version prior to v6.43 (v6.42.12 and older) will clear all user passwords and allow password-less authentication. Please secure your router after downgrading.
Old API authentication method will also no longer work, see documentation for new login procedure: https://wiki.mikrotik.com/wiki/Manual:API#Initial_login
Changes in this release:
*) certificate - renew certificates via SCEP when 3/4 of lifetime reached;
*) crs317 - fixed multicast packet receiving (introduced in v6.45);
*) hotspot - fixed default profile values not being used (introduced in v6.45);
*) rb4011 - fixed SFP+ interface linking (introduced in v6.45.2);
*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
*) supout - fixed SIM slot printing (introduced in v6.45);
*) wireless - improved U-APSD (WMM Power Save) support for 802.11e;
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 particular RouterOS release.
What exactly do you have in mind? The incorrect flagging of actually new GRE packets as invalid? If so, then no, this is not fixed in 6.45.3, but it can be worked around by adding protocol=!gre to the action=drop connection-state=invalid rules in the default firewall, or several other equally simple ways. If you mean that GRE “stopped working although it did before”, read the 6.45.1 and 6.45.2 topics, it has been discussed there up and through multiple times why this happens and how to fix it.
Board: RB4011iGS+5HacQ2HnD
Problem: on all ros 6.44.x-6.45.x on PPP client/server interfaces (L2TP, PPTP, PPPoE) appear at the same time small Tx Drops counters. On ros 6.43.16 works well on same config.
I have installed the update on my 4011 wired only router and had no initial issues. After the reboot and upgrade i updated the routerboard firmware and initiated the reboot. After the firmware update the device has not come back online. I am also remote to the device and will be looking at it later tonight when i get home from work. I will post or edit my findings here.
After i was onsite with the 4011, i was able to reboot one more time and the sfp+ dac linked to the switch without any other changes. I did have link on eth1 and 2 prior to the manual reboot.
For me its working. But first I have to remove all files from ‘Files’ Dialog. There was a file from broken update procedure of 6.45.2 which needs to be removed.
I got ~7.5MB free space which allow updating wihtout issues.
Unable to upgrade on HAP AC and WAP AC. Also appear unstable, seem to lack memory. Tried to remove files but without success. In Resources it states that I have only 3,3 MB free HD space… What to do?
RB4011 wifi 5ghz not solve, wlan1 crashes as always.
PS.
already gone the second year since the release of RB4011. But the problem has not been resolved.
[quote=marry070 post_id=742964 time=1564826336 user_id=146194]
v6.45.3 is released! but when I tried to update my system then it shows an error windows defender error 577, I really have no idea how to remove this error. if you have any idea about it then please share with me.
[/quote]
How are you updating? The device itself downloads the updates if you do it through Winbox so Windows Defender should not have any impact.
Just updated my RB4011iGS+RM from 6.45.1 to 6.45.3. I had skipped 6.45.2 as I’m using the SFP+ port for downlink into my network. I’ve used the “Download and Install” option from WinBox to perform the installation. After reboot, the SFP+ port will not pass traffic. Everything else works as expected when using the gbit interfaces.
6.45.3 claims to resolve the SFP+ issue… is anyone else using this configuration? I’m using a Cisco active DAC which was working without problems under 6.45.1.
edit: power cycle of the router after the upgrade finally resolved the issue. Fortunately this device is local to me…
Posted by spacex — Fri Aug 02, 2019 12:25 am [quote=spacex post_id=742726 user_id=127075]
Not fix dude snmp v3 ?
[/quote]
Posted by spacex — Sun Aug 04, 2019 2:32 pm
[quote=spacex post_id=743074 time=1564918334 user_id=127075]
Hello,
The dude snmp v3 problem not fix ?
[/quote]
No, since it is not mentioned in the change log - [i]Please keep this forum topic strictly related to this particular RouterOS release.[/i] - no need to repeat yourself.
emils response in the 6.45.2 topic still applies:
[quote]
As for SNMPv3 and GRE issues. We are aware of these issues and are working on resolving them. However we much rather release a quicker update with fewer bug fixes which may help other users than waiting longer for issues that takes longer to fix.
[/quote]