hello, i'm beginner ,
any one can help me with this error?
i can't find a solution thx
RouterOS status connection time out (6)
As winbox connection seems to work just fine, even under high latency connections, then it must be something specific to the Dude client, right? The thing is that the other Dude functionalities work fine, in my exprience the only issue is when the Dude tries to obtain the information related to the remote RouterOs version.Hello, the same thing happens to me and I am connected to the RB through a VPN, I receive all the snmp and log data but the connection through port 8291 does not work, it says Timeout, but I noticed something in my log while trying to connect, I attach a photo
My mikrotik are connected to satellite services, the best latency is between 700 and 1000ms, and the but is between 1500 and 3000ms.
I don't think it is due to latency because it does loggin and then logout ...
Hello Sir, I am an inmarsat certified engineer and I have been integrating mikrotik in this type of networks for a long time, the problem you present is due to latency, I do not know in which band you are using the terminals but so far the Ku-Ka band is the one that offers in lower ping, between 600 and 800ms and I can assure you that not even with that ping you will be able to integrate RouterOs in the Dude, you will have to opt for SNMP, good luckIs there any specific timeout for RouterOs query? The other functionalities of the Dude work fine under high latency (satellite), only RouterOS query seems to fail.
That is very interesting. I am using maritime IGX (ka band) with latencies aroung 1 sec. But the thing is that I am also using ka band in ground terminals and RouterOs in the Dude works just fine... Fair to say that in this case the latency is lower, 600 ms aprox.Hello Sir, I am an inmarsat certified engineer and I have been integrating mikrotik in this type of networks for a long time, the problem you present is due to latency, I do not know in which band you are using the terminals but so far the Ku-Ka band is the one that offers in lower ping, between 600 and 800ms and I can assure you that not even with that ping you will be able to integrate RouterOs in the Dude, you will have to opt for SNMP, good luckIs there any specific timeout for RouterOs query? The other functionalities of the Dude work fine under high latency (satellite), only RouterOS query seems to fail.
They are my guesses but it could be said that as it is based on a connection of the RouterOS operating system, perhaps it requires a certain degree of latency to be able to function in its own way, I will tell you this because in satellite terminals when you use mikrotik and try to ping from new terminal It will show you a time out and it is not because you do not have ping but because the latency is very high and does not adjust to the system parameters, perhaps the link by Dude in RouterOS works in the same way.That is very interesting. I am using maritime IGX (ka band) with latencies aroung 1 sec. But the thing is that I am also using ka band in ground terminals and RouterOs in the Dude works just fine... Fair to say that in this case the latency is lower, 600 ms aprox.Hello Sir, I am an inmarsat certified engineer and I have been integrating mikrotik in this type of networks for a long time, the problem you present is due to latency, I do not know in which band you are using the terminals but so far the Ku-Ka band is the one that offers in lower ping, between 600 and 800ms and I can assure you that not even with that ping you will be able to integrate RouterOs in the Dude, you will have to opt for SNMP, good luckIs there any specific timeout for RouterOs query? The other functionalities of the Dude work fine under high latency (satellite), only RouterOS query seems to fail.
And why only RouterOS fails and not the other probes in the Dude?
Yes, perfectly clear, thanks!They are my guesses but it could be said that as it is based on a connection of the RouterOS operating system, perhaps it requires a certain degree of latency to be able to function in its own way, I will tell you this because in satellite terminals when you use mikrotik and try to ping from new terminal It will show you a time out and it is not because you do not have ping but because the latency is very high and does not adjust to the system parameters, perhaps the link by Dude in RouterOS works in the same way.That is very interesting. I am using maritime IGX (ka band) with latencies aroung 1 sec. But the thing is that I am also using ka band in ground terminals and RouterOs in the Dude works just fine... Fair to say that in this case the latency is lower, 600 ms aprox.Hello Sir, I am an inmarsat certified engineer and I have been integrating mikrotik in this type of networks for a long time, the problem you present is due to latency, I do not know in which band you are using the terminals but so far the Ku-Ka band is the one that offers in lower ping, between 600 and 800ms and I can assure you that not even with that ping you will be able to integrate RouterOs in the Dude, you will have to opt for SNMP, good luckIs there any specific timeout for RouterOs query? The other functionalities of the Dude work fine under high latency (satellite), only RouterOS query seems to fail.
And why only RouterOS fails and not the other probes in the Dude?
I hope I have explained myself well.