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
What’s new in 6.40.6 (2018-Feb-20 11:04):
*) btest - fixed TCP test accuracy when low TX/RX rates are used;
*) certificate - do not use UTF-8 for SCEP challenge password;
*) certificate - fixed PKCS#10 version;
*) chr - generate new system ID on first boot;
*) crs317 - fixed reliability on FAN controller;
*) defconf - fixed DISC Lite5 LED default configuration;
*) dhcpv4-server - fixed framed and classless route received from RADIUS server;
*) disk - fixed disk detach process;
*) dude - fixed e-mail notifications when default port is not used;
*) export - fixed “/system routerboard mode-button” compact export;
*) filesystem - implemented additional system integrity checks on reboots;
*) firewall - limited maximum “address-list-timeout” value to “35w3d13h13m56sâ€;
*) hotspot - fixed “dst-port” to require valid “protocol” in “walled-garden ip”;
*) hotspot - fixed Walled Garden IP functionality when address-list is used;
*) ike1 - fixed crash on XAUTH if user does not exist;
*) ike1 - fixed memory corruption when IPv6 is used;
*) ike1 - improved stability on phase1 rekeying;
*) ike2 - added support for multiple split networks;
*) ike2 - delay rekeyed peer outbound SA installation;
*) ike2 - improve half-open connection handling;
*) ike2 - kill connection when peer changes address;
*) ike2 - use peer configuration address when available on empty TSi;
*) ipsec - fixed incorrect esp proposal key size usage;
*) ipsec - properly update IPsec secret for IPIP/EoIP/GRE dynamic peer;
*) l2tp - improved reliability on packet processing in FastPath;
*) netinstall - improved LTE package description;
*) netinstall - properly generate skins folder when branding package is installed;
*) ovpn - fixed resource leak on systems with high CPU usage;
*) ovpn-server - do not periodically change automatically generated server MAC address;
*) ppp - do not disconnect active PPP connection after “idle-timeout”;
*) ppp - do not lose “/ppp profile” script configuration after other profile parameters are edited;
*) ppp - fixed “change-mss” functionality when MSS is not set on forwarded packets;
*) ppp - fixed L2TP and PPTP encryption negotiation process on configuration changes;
*) pppoe-client - properly re-establish MLPPP session when one of the lines stopped transmitting packets;
*) quickset - do not automatically change mode to CPE;
*) quickset - renamed router IP static DNS name to “router.lan”;
*) route - fixed DHCP/PPP “add-default-route†“distance†minimal value to 1;
*) route - improved reliability on routing table update;
*) routerboard - properly report warnings under “/system routerboard” menu;
*) scheduler - properly display long scheduler configuration;
*) sfp - improved SFP module compatibility;
*) sms - fixed minor problem for SMS delivery;
*) snmp - added IPv6 addresses support on default “public” community;
*) snmp - fixed bulk requests when non-repeaters are used;
*) snmp - fixed consecutive OID bulk get from the same table;
*) traceroute - fixed “/tool traceroute” results print;
*) traffic-flow - do not count single extra packet per each flow;
*) webfig - added support for proper default policies when adding script or scheduler job;
*) webfig - fixed backup loading from Webfig on RouterBOARD running default configuration;
*) webfig - fixed bridge port sorting order by name;
*) webfig - fixed MAC address ordering;
*) webfig - fixed router getting reset to default configuration;
*) webfig - fixed column ordering;
*) winbox - allow to specify “to-ports” for “action=masquerade”;
*) wireless - fixed wireless protocol mode restrictions if lockpack is installed and has limits for it;
*) wireless - removed unused monitor command from CLI;
*) wireless - updated “Australia”, “Czech Republic”, “UK 5.8 Fixed” and “United Kingdom” regulatory domain information;
Please keep this forum topic strictly related to this concrete RouterOS release.
Did you got problems with OSPFv3 on this version? After update a RB1100AHx2, some OSPFv3 neighbors doesn’t reach the full state. Neighbors that are running is because I disabled / enable OSPFv3 interface. I’ve done the same with all neighbors, but some doesn’t worked.
I tried to remove / add the OSPFv3 interface too, but the problem remains.
I didn’t do this test yet. One of the neighbors that wasn’t working, becomes to work after update (6.23 → 6.41.2). The other one still non working (no update).
I’ll test a downgrade on RB1100AHx2 to 6.40.5 to see if it’ll work.
I’ll do this in a light time, because it’s one of my main routers.
Does the “What’s new in 6.40.6” show what is new compared to the previous bugfix release 6.39.3 or only what is new compared to 6.40.5? Is everything that is in 6.40.5 also in 6.40.6? I want to see the complete list of what has changed between what I’m currently running (6.39.3) before I upgrade.
I’m pretty sure not everything in 6.40.6 is new compared to 6.42.rc30, so my question remains, “new compared to what?” (For example, the item “dude - fixed e-mail notifications when default port is not used” appears in “What’s new in 6.41.1” as well as “What’s new in 6.40.6”, but 6.41.1 is over 6 months old.)
If you look at the bugfix release tree changelogs you will see that the [bugfix] release immediately prior to 6.40.6 is 6.39.3. This implies that the only changes between 6.40.6 and 6.39.3 are the ones listed in the 6.40.6 “what’s new” list, but I have my doubts about whether or not this is true. This is what I would like MikroTik to clarify.
If you look at https://mikrotik.com/download/changelogs/ for the current release changelogs, you will see that 6.40.6 is not listed. So my best guess is that “What’s new in 6.40.6” is what is new compared to 6.40.5 and upgrading from the previous [bugfix] release of 6.39.3 to the current [bugfix] release of 6.40.6 will change a lot more than what is listed. But what exactly will change?
“What’s new in 6.40” lists what changed between 6.39.2 and 6.40. Some of those changes made it into 6.39.3, so I cannot look at the 6.40 list and say “all those things are also new in 6.40.6 compared to 6.39.3” nor can I say they are all not new.
I would like a list of what changed between 6.39.3 and 6.40.6 that includes everything that changed but does not also include things that did not change, so I can review the changes without worrying about things already in place on my systems. The changelog is supposed to provide this, but I think it does not.
*) tile - improved overall system performance and stability (“/system routerboard upgrade” required);
*) capsman - improved CAPsMAN responsiveness on systems with large amount of CAP interfaces;
*) wireless - added support for “band=5ghz-n/ac” (CLI only);
*) wireless - improved compatibility with specific wireless AC standard clients;
*) wireless - improved packet processing on ARM platform devices;
*) wireless - improved wireless scan functionality for devices with multiple wireless interfaces;
pietroscherer - Glad to hear that you resolved the problem. As far as I understand, you can not tell if problem was caused by this particular release. Is that correct? jgro, BartoszP - Changelog always shows difference between this version and previous one. Previous before 6.40.6 is “-1” - 6.40.5. This changelog shows difference between 6.40.5 and 6.40.6. For example, if you upgrade from 6.38, then you have to check - all 6.38.x changelogs, 6.39 and 6.39.x changelogs and 6.40 and 6.40.x changelogs. Beone - There are no silent fixes. If changes are not in changelog, then they are not in the release.
I know they are not in the release, but 6.41+ is having the whole new bridge implementation, which needs to stabilize first. Meanwhile we have production devices requiring at least the capsman and tile performance fixes, which are not available in bugfix. So my question is: can you release a bugfix having those fixes but not yet having the new bridge implementation? (a 6.40.7 so to speak)
