i use W60G nRay to connect two buildings.
I have a strange issue with RouterOS 7.19.4 . After upgrading one or both devices from 7.19.1 to 7.19.4, the link between the wireless nodes are gone.
The Signal is still on a high level (80-100), but the MSC is at 0.
After downgrading both devices to 7.19.1, Signal and MSC are fine and the link is established.
It is noticeable that 7.19.4 has many “link downs” in the interface status. 7.19.1 has no “link downs” at all.
This is at first a user forum, meaning: users helping out other users.
Mikrotik staff sometimes comes in but not always and not everywhere.
You might be better of creating a support ticket with your findings (make sure to include supout.rif when the issue occurs) so they can investigate in detail what might be wrong.
I still believe that MikroTik should include a “known issues” in the release notes, and update that when such issues are found (“known issues: does not work on W60G - do not install it”).
(both the release notes on the upgrade server and in the forum should be updated)
Would not be good when you update your W60G outside of business hours and find the link down and a site visit required to downgrade it…
Also, you would expect the software to be tested in the lab before release…
Ah yes, and everyone reads those release notes, right ?
Most will simply, from the device, hit upgrade and boom…
“Oops, too late.”
I do agree this is one of the things which could have been found with proper regression testing.
But there are quite a bit of combinations of config and HW which then need to be kept active for those tests.
It’s not always practical to do.
Not saying this is something which has to be accepted. Just indicating it’s not always easy to prevent.
Well, in my opinion they should have a test lab that at least includes a pair of 60G devices linked to each other, and test if the link works after upgrade. It is not the first time that a general upgrade of a stable version causes issues on 60G devices!
Remember this is a minor upgrade to a stable version, it does not mention a change for 60G, but apparently still something has been changed. Maybe it was “arm - improved system stability when processing encrypted traffic”?
When you do a “check for upgrades” you get the release notes displayed. That is the place to warn the user.
Of course they could even decide not to show the upgrade to W60G users, I have seen a competitor do that but I do not know if MikroTik currently does that. But that would only work for users who upgrade from the device, not for those that upload packages.
This is a fundamental issue, since a link can’t be established on nray60 devices.
My setup is a really easy one, so if functionality would have been tested, Mikrotik itself would have recognised the issue.
It costed me at least some hours to get my link running again.
I’ve made a ticket including the link of this thread.
Sounds like:
“Here’s the latest stable update(no testing/development). But don’t use it.
Your device will lose its main function then”.
Assuming you can still reach the device (i.e. it is not at the other end of a link that is now dead): go to the MikroTik website https://mikrotik.com/download click on "download archive", click on 7.19.3, download the routeros package for the architecture of the device (in this case: arm64), and upload it to the device (in the files menu you can upload a file). When you have other packages than "routeros" installed, upload those too.
Then in the system->package menu click "downgrade".
I'm been having the same problem. I'm just bringing this up for the first time, and have spent ages trying to work out what was wrong - I thought it was my config rather than bad firmware.
It would be nice if they could make downgrades as easy as the upgrade, i.e. select the version you want from a drop down in the firmware upgrade section...
The issue presents itself with the pre-configured settings out of the box on an nRAYG-60adpair. Mikrotik really should have done a bit more testing on this before releasing, I would expect them to have a lab setup with at least some basic tests going on with all their devices in a basic configuration.
Great stuff..... any workaround? Slave is now on 7.19.4 and won't connect. Not reachable from my side. Master ist back to 7.19.3 - any settings possible to reach the slave somehow or is this "you won a looooong trip to visit your client for free?"
In all seriousness:
Next time, test in a lab environment or something more practical before upgrading ? Don't upgrade if not needed and certainly not when not tested if you can not afford the downtime it may bring.
If it works, it works.
?