Who is such a selfkiller to be willing to make an update over all network devices without prior reading of change log, observing forum and appropriate testing? Especially when he doesn't know why he needs to update?
Maybe it is some kind of fool but definitely not an administrator.
I don't know if this is pointed towards me but am going to answer anyway.
We've update the whole of our network exept dude and usermanager towards 6.37.1 in the last weeks after we found it works stable for all in the field units and routers at our central.
We are occurring no issues with this version nor do we see any alarming post in this forum.
So now two weeks later after our last units are updated and the network runs fine and we still see small issues in the dude with v. 6.34 we decided to give it a go.
Update dude to 3.37.1. And in fact it still works and the small issues we've had before up to now didn't pop up yet agains... so al fine.
Just now we'd wanted to re-use an old SXT for a new client we found the upgrade showed 6.37.2 as the latest 'current' but no change log apart from the warning that Dude is not functioning in this (which?) version anymore!
So this IS very confusing and makes me wonder what the issue is and in which version did this came up?
We've had lengthy discussion in this forum abt. upgrade procedures and it is esthablished that 'current' means stable and that as operator you'd better be on the conservative side so wait a bit and follow the forums. This is exactly what we did!
If this now would not be a proper procedure then tell me what it is? Only work with bug free version 6.36? And then still find a bug? With MT (like any OS) there is not something like a 100% bug free, problem free version. So we work by the guidelines and that's it.
Show your appreciation of this post by giving me Karma! Thanks.
Rudy R. Puister
WISP operator based on MT routerboard & ROS.