RouterOS version 6.43.11 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.43.11 (2019-Feb-04 12:24):
Changes in this release:
*) ipsec - accept only valid path for “export-pub-key” parameter in “key” menu;
*) quickset - fixed “country” parameter not properly setting regulatory domain configuration;
*) smb - fixed possible buffer overflow;
*) w60g - fixed disconnection issues in PtMP setups;
*) wireless - improved antenna gain setting for devices with built in antennas;
*) wireless - show indoor/outdoor frequency limitations under “/interface wireless info country-info” command;
What’s new in 6.43.10 (2019-Jan-24 07:09):
(factory only release)
What’s new in 6.43.9 (2019-Jan-10 07:11):
(factory only release)
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 concrete RouterOS release.
WW Dish before upgrade: RSSI -49 on both ends, after upgrade -56 on one side, -59 on 2nd side
After a reboot one side was fixed at -49 RSSI again, but 2nd shows MCS 1 and signal level 20, RSSI -59 again.
After another reboot, it is back on -49 on both ends with MCS 8 and signal level 95.
Another issue iswith making supout.rif - after waiting for more than 10 minutes, it was stucked at 1%. When stopped and tried to run again, I just got an error message: Couldn’t start - busy.
They are fixing the places where commands can write to arbitrary files and thus can destroy internal configuration or open the built-in shell.
Another example was the telnet session log that was recently fixed.
Those bugs can be used by malware to cause more trouble and/or prevent removal of the malware, although they do not pose a security problem themselves.
One mans spam, is another mans meat.
To put things in perspective, in Newfoundland, the poor folk had to eat sandwiches everyday of lobster meat.
How awful.
If an interim release is deemed required by MT, then so be it.
I am just super happy they ignore ignorant comments.
I just marked your post as spam!
As for the topic at hand. I recently manually inserted a 2DB antenna gain after watching a recent MUM presentation in the UK (on my capacs).
Will the update automatically insert that gain??
Aren’t you still planning to integrate udpxy from openwrt into RouterOS? It depends only from libc, and compiles under any architecture easily, and a lot of users pleasing you to add, and when you claims “router should do routing and not being overloaded by 3rd party crap” - that’s it, just route for my TV’s udp multicast to http tcp stream, this action won’t eat CPU so much. You are don’t giving a chance to do anything, proprietary OS, no toolchains to compile, no ways to create packages, just metarouter - that is not useful on hAP.
Memory leak in proxy on HEX r3 still present. Behavior is the same as described in the 6.43.8 thread
With proxy disabled the memory usage is around 42mb. If you enable the proxy but don’t send any traffic the memory consumption stays at 42mb. As soon as you open the web proxy interface in winbox the memory consumption jumps to 64mb (still no traffic via proxy). As soon as any traffic flows via the proxy the memory consumption jumps to 102mb. At the same time, if you go and look at the proxy it says Total RAM Used: 996KiB. So something somewhere is leaking close to 60mb. This did not happen before on 6.42.7 or older versions.
