The minimum version of remote devices is 6.48.3You must read the changelog,
old RouterOS access are replaced on 6.4??? (do not remember) with another type of strong access, also API are changed
Thanks for trying. It prompted me to have another closer look at what was going on.Apparently agent "server" is the default.. so I have no clue, sorry.
Good to see you got sorted. Just a couple of quick questions if you are about - get a chance to answer.Thanks for trying. It prompted me to have another closer look at what was going on.Apparently agent "server" is the default.. so I have no clue, sorry.
I found the solution.... There were some NAT and Mangle rules I had created years ago to enable The Dude to talk to some remote mikrotik devices on ports other than 8291. These had malfunctioned/broken in the upgrade to 7.2. I'll have to go back and figure out why, but once I disabled these everything started working.
Also despite @rextended stating otherwise, and as I expected, Dude 7.2 is quite happy talking to older ROS versions. Just in case anyone else was wondering.
Good to see you got sorted. Just a couple of quick questions if you are about - get a chance to answer.
1. How Many ROS devices are you monitoring the the RouterOS service.
2. Do they all Stay "up/connected"
3. What Hardware/License Level - if you don't mind answering
Asking as we have stuck with an older version of dude and just reduced the connections of RouterOS as it was failing at the time with more than 50 connections ("RouterOS" runs on winbox port - 8291 - so suspect it's using a login/connection to do so). We run a P1 CHR which should have no such limits - but it certainly does on 6.46.6 (the version we are on, as we had things as old as 5.21 out there last time we assessed - not any more though)
any infor you can give would be great - cheers
Not sure... all I can say is that my Dude Server running 7.2.3 is still able to communicate with older ROS devices without any problem. I will try and upgrade it to 7.3.1 one evening this week and see if anything breaks.This night, after many issues, I've managed to upgrade my Dude Server to 7.3.1, and now all agent connections are broken with good old error: agent NameOfRemoteDevice routerOS version not same as dude servers (6.48.4 (stable)), next attempt at 20:57:24
Same on 6.49.6 devices
Any suggestions how to proceed without upgrading all agents to 7.3.1 at once and still not loosing sight on monitored services behind that agents ?
I might have given you some bum advice..... I don't use Dude Agents, but I think from doing some quick reading that dude agent does need to be same version as the server. Sorry I should have read your question more carefully.It CAN connect and monitor RouterOS device directly. The problem comes with the agent devices which are not the same version.