Than try run dude on multi-core CCR. No old single core MIPS.I am on dude 6.47.8 without any problems ...
(Max connection speed is 1GB/s here)
just my 2c
Good news works with MMIPS 4 Threads. NO 4 core https://mikrotik.com/product/RB750Gr3.dude is running on a dedicated RB750Gr3 which has a 4-core cpu ...
I do not understand. How can you take away the functionality that is the main feature ... Cut the possibility of normal collection of information through ros_command & ros_info ... Some information is either not possible or difficult to obtain through SNMP. Also, how can you write this lie that can't repeat the problem. Are you holding us fools ??? This is a question for developers. Give at least one comment!reduce or remove all ros_command and ros_info used,
simply convert all to SNMP
like the uptime use
oid("iso.org.dod.internet.mgmt.mib-2.system.sysUpTime.sysUpTimeInstance")
than ros_command to obtain it
Who write "can't repeat the problem"???Also, how can you write this lie that can't repeat the problem.
For you there is no need, you already are if you read things that I have not written ...Are you holding us fools ???
And this is a user forum, not a support platform, if you do not have noticed that.This is a question for developers.
Are these enough?Give at least one comment!
Everything I wrote does not apply to you. I have just quoted you and fully confirm your observations on this issue. Also, my post only applies to developers.Who write "can't repeat the problem"???Also, how can you write this lie that can't repeat the problem.
For you there is no need, you already are if you read things that I have not written ...Are you holding us fools ???
And this is a user forum, not a support platform, if you do not have noticed that.This is a question for developers.
Write directly do support@mikrotik.com
Are these enough?Give at least one comment!
It's perfectly normal than the connection is open just for execute the command and then closed,
It's perfectly normal than the connection is logged on RouterBOARD log,
What you expect from this?
Sorry, but I misunderstand, you wroted continuosly without break...Everything I wrote does not apply to you
That is the Log of ONE RouterBOARD, not the Log of The Dude, or at most it is the RouterBOARD where The Dude is that self-interrogates...Here, look at this beauty. No wonder the dude is going crazy. And now imagine if the dude has a 3000 routerboard.
I do not understand why you were blown up by my posts. I have no complaints about you. Everything I wrote is for developers. Let them comment. And to write in technical support does not make sense for 10 years they didn't solve any problem about which I wrote on the dude.Sorry, but I misunderstand, you wroted continuosly without break...Everything I wrote does not apply to you
That is the Log of ONE RouterBOARD, not the Log of The Dude, or at most it is the RouterBOARD where The Dude is that self-interrogates...Here, look at this beauty. No wonder the dude is going crazy. And now imagine if the dude has a 3000 routerboard.
However it goes, each RouterBOARD has its own Log, not all 3000 are put together.
And if someone have 3000 devices, probably have more than one dude....
This is user forum, any complain?
Write to support@mikrotik.com
And again, you understand this?:
It's perfectly normal than the connection is open just for execute the command and then closed,
It's perfectly normal than the connection is logged on RouterBOARD log,
Where did you get what I didn't understand?Go ahead and write direct posts to the developers,
who can't wait to come here on this topic to see what you write,
but don't quote others when you do, or it seems that you write to the quoted...
I doubt that they will give you the slightest listen if you have not even understood the two bold lines, on previous post, I wrote to you.
Goodbye.
I don't understand this sentence, who should I call?If you call someone you are a juvenile jerk.
I don't understand this sentence, who should I call?If you call someone you are a juvenile jerk.
This is a user forum, and you keep to not understand, if you do not want opinons, do not write,
You still keep this behavior because you do not understand simply this two sentences:
It's perfectly normal than the connection is open just for execute the command and then closed,
It's perfectly normal than the connection is logged on RouterBOARD log,
Probably that is a new choice, instead to keep connection alive for thousand of devices, which will surely consume more memory to keep them all open.
You must understand that it is perfectly normal for Access Logs to be written to the remote device,
one for when The Dude connects to the remote device,
and one for when it disconnects.
You would like the service to no longer be logged in and any unexpected access wod not be noticed...
This is not a The Dude bug, is your problem, what you expect from support?
For not see anymore the access Log, simply put on /system logging on the info topi settings add !account
Has been a while since I put in my observations - so will do here.Hello.
I continue to use ROS 6.45.9.
Newer version The Dude does not work well.
Only on this version is the Dude server permanently connected to the MikroTik routers through the Dude client.
The version above is used to connect Winbox.
If you update the version, then the Dude server is constantly connected and disconnected from the MikroTik routers.
Information on map becomes irrelevant.
MikroTik routers logs are full of unnecessary information (connect/disconnect).
Why has the The Dude changed the way he collects information through Router OS?
So - Just Quoting Myself here - finally got a Chance to try something else.Have been Struggling with this issues for months - and have found my reason... but it's not a happy situation.
Have CHR with 4gb RAM and 4 Cores - nothing over the top.
Issue arises when i have Dude trying to reconnect to multiple ROS devices at the same time - CPU perfs out on one core, and as they use the winbox service for these connections now (historically was the dude service) All connectivity to the Dude flies out the window, including Dude Client and Winbox into unit. Perfs out for extended times.
The "Fix i have in place at the moment... disabling my allow for winbox connections from Dude... Obviously that entirely breaks monitoring for ROS functions, but having monitoring for all my devices (4k+) trumps having dude fall over because of a few hundred winbox connections.
Have re-eanbled for my core devices - but client cores and other structure are to be determined at this stage.
I also have a spare ccr 1016 with microsd slot floating around - will look to build it up quick at some stage to test, but have a couple weeks on the road coming up, so will have to to it after.
Hopefully this helps someone, and if anyone think's the info is pertinent, hand it over to the dev team (i don't even know where to start with contact - will be looking deeper once i have the CCR tested)
It's perfectly normal than the connection is open just for execute the command and then closed,
It's perfectly normal than the connection is logged on RouterBOARD log,
Probably that is a new choice, instead to keep connection alive for thousand of devices, which will surely consume more memory to keep them all open.
You must understand that it is perfectly normal for Access Logs to be written to the remote device,
one for when The Dude connects to the remote device,
and one for when it disconnects.
You would like the service to no longer be logged in and any unexpected access wod not be noticed...
This is not a The Dude bug, is your problem, what you expect from support?
For not see anymore the access Log, simply put on /system logging on the info topic settings add !account