RouterOS version 6.44.1 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.44.1 (2019-Mar-13 08:38):
Changes in this release:
*) bridge - fixed possible memory leak when using “ingress-filtering=yes” on bridge interface;
*) certificate - force 3DES encryption for P12 certificate export;
*) dhcp - fixed dual stack queue addition;
*) dhcpv6-server - use MAC address for RADIUS user when “allow-dual-stack-queue=yes”;
*) e-mail - fixed missing “from” address for sent e-mails (introduced in v6.44);
*) gps - increase precision for dd format;
*) gps - removed unnecessary leading “0” for dd format;
*) ipsec - allow identities with empty XAuth login and password if RADIUS is enabled (introduced in v6.44);
*) 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 - do not show “session-uptime” if session is not up;
*) lte - fixed LTE interface band setting on RBSXTLTE3-7 (introduced in v6.44);
*) rb4011 - fixed ether10 failing to auto negotiate link speed to 1Gbps;
*) winbox - added “use-local-address” parameter in “IP/Cloud” menu;
*) wireless - fixed antenna gain setting on RBSXT5nDr2;
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.
Any ideas why in a LHG XL 5 ac wireless interface, even though wmm-support=disabled in the wlan1 interface, when I monitor wlan1 the interface shows wmm-enabled: yes? Is this a ROS bug?
I am seeing a lot of dropped Forwarded packets as INVALID.
These are packets that should have hit the New connection from a local device in the address list. But are getting dropped.
Also
IPSEC connection between offices is now dropping pings.
Call from another Tech.
We found that routing between 2 subnets was getting flagged as invalid. Had to add a pass rule for anything from Subnet1 to accept Forward to Subnet2 and the reverse.
Seems 6.44.1 broke some stuff.
Guess we are back to the days where we can’t “just download the latest firmware.”
Queries to the DNS name .sn.mynetname.net return the IPv4/IPv6 addresses of the router. If you select “use-local-address” the IPv4 returned will be the local one in the WAN interface, not the IPv4 that the Cloud service sees.
…
Fixed the Title!!
v6.44.1 [could be stable] is released!
I always wait for a couple of days to see if you are happy with a new firmware! Please don’t change your habits LOL.
This looks like a case of the problem already mentioned in post #2 in this topic and in several posts (by me and others) in the 6.44 topic.
For some reason there is no reaction at all from MikroTik, although they often post replies to such reports in release topics.
There also is no hint of a change in the connection tracking functionality anywhere in the release notes.
@Pe1chi
It boggles my mind that MT does not understand the word stable in a full context.
Specifically they obviously (and keep proving it), need a “stable” of beta testers for firmware before public release.
By that I mean a mix of thoroughbreds, like yourself, mkx, sob, etc… and some mixed breeds like myself for example.
Throw in a few dark and/or wild horses like chupka, sebastia, and gotsprings for example and they would same themselves a lot of unnecessary grief.
Updated my Hap AC^2, also getting lots of invalids dropped, but these drops are ACKs and ACK,FINs, so not sure these should be in the “New” connections.
Further to above, it seems to be only from the wireless side, no drops in log from my ethernet connections, my wireless is not part of bridge config
I can confirm the “Loose TCP Tracking” is completely broken in this release (and perhaps 6.44, didn’t test it extensively). Previously established connections are treated as INVALID regardless of the setting.
That already happened in 6.44 as I noticed when I upgraded my home router.
There I always have >10 established TCP sessions and they all failed when I did the upgrade, which did not happen before.
