RouterOS version 6.47.7 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.47.7 (2020-Oct-27 13:27):
Changes in this release:
*) crs3xx - improved system stability on CRS354 devices;
*) defconf - improved default configuration generation on devices without wireless package installed;
*) poe - fixed automatic PoE firmware upgrade procedure;
*) poe - improved PoE-out status detection;
*) wireless - updated “kazakhstan” regulatory domain information;
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.
On the version 6.47.7 command repartition (e.g. “/partitions repartition partitions =2”) causes the router’s cyclic reboot (about every 10 seconds). On versions 6.47.x situation the same.
On the version 6.46.7 this command works correctly
HEX PoE with a 48V power supply did not immediately load the connected equipment, nor does it. It takes 3 to 5 minutes to determine whether to turn on power.
He mentions a SUP id so clearly he contacted support.
I think it is good to warn users about such a potentially fatal bug on the forum even after having contacted support.
I use several devices with partitioning but they have been partitioned on older RouterOS versions and still work fine.
But I really like to know when that kind of fatal problem would happen before I initialize partitioning on a remote device.
(I have not yet tested if it really is a common problem or “only” happens for him)
Hmm, seems rather a small list of improvements and no mention of making hot chocolate and routing simultaneously.
It should be a MT trademark to include at least one juicy sexy update item per version…
Update went butter smooth,all in all everything works fine. System didn’t reset itself this time as it was the case with 6.47.2 and 6.47.3.
Hap Ac. Updated from 6.47.3 to 6.47.7
I took the plunge and updated my RB3011 from 6.46.6 (Testing) to this latest “stable”
Upgrade process without any issues, now I will be looking out for “interface resets/flaps” that have plagued me over the latest span of releases. It seemed the 6.46.6 (Testing) proved stable concerning these interface “flaps”
Not so successful. CRS354 is STILL useless.
I can’t count on this unit at all. I am waiting for fix couple of months and honestly I am starting be a little bit disappointed.
Can actually someone really do something about it ?
It is about time.
For what it’s worth, my w60G link of two 60G wAPs at ~205m is still considerably less stable on 6.47.7 (with the apparent improvements from 6.47.6) than it was on 6.45.9.
Sure the range is basically maxed out here and it’s not supposed to work perfectly anyway, but 6.45.9 really seemed to cope with that much better.
Update: It’s seems to only have gotten less stable on 58GHz channel, 60GHz one has improved somewhat. Looking better right now than 58 on old firmware. Better beamforming patterns of phased array maybe? Will keep monitoring in next weeks.
Might want to connect using the MAC address instead of IP.
Can you please share the config (/export hide-sensitive file=anythingyoulike) of this cAP ac?
There still is a “bad user experience” due to the wireless changes in the 6.47.x version.
I got a new “wAP ac” to use as an access point. Unpacked it, connected to it, immediately updated it from the 6.44 it came with to 6.47.7
Now want to do the wireless settings. It is set to “manual-txpower” and “no_country_set”.
So I want to change that to “regulatory-domain” and “netherlands”, but the device won’t let me make that change because “the antenna gain value 0 is not valid”.
However, there no longer is an antenna gain input field so there is no way to correct that.
This can only be fixed by going to the command line mode and setting the antenna gain to 2. Not user friendly, the GUI should offer the option to make that change and store the settings.