Nothing doing.. Syslog is empty after reboot, font has no national symbols… And no answers from techsupport..
Ok. Understood. Any other Mikrotik device that is recommended to run The Dude on?
That’s great.
What do you mean with this comment?
Dude is running on the RB750Gr3 and after reboot the LOG is gone but all other collected data is still there. I have DUDE switched off on the moment and can activate it to see if the log can be rotated/saved so that it will be accessible if needed.
Ok, thanks for the useful feedback. As the device is about 60/70 euro in NL I will give it a try to purchase one and try to install The Dude on it. I hope it is working and sufficient to monitor my 12 Mikrotik devices. Once I’ve some experience and results I will post it in this thread.
Dude on Hexr3. MT devices running 6.38 .5 ( soon 6.30x ) Is it OK to run DudeServer rc .. or should I stick to the same Dude server as
on all the networked devices. Any issues with running RC Dude server a couple versions above the Networked MT devices?
Running dude on hex with 6.39 smoothly. Poling about 50 devices so far.
Hello team .
Long time ago i run dude server in windows machine, since then i adapt this shoft under my needs, now it monitors about 100-200 switches, and OLT,ubnt,windows, mikrotik units, the all work good, but windows machine is no longer need on that network so i biught a 750gr3, install dude with no problem and runa few devices, i don’t know but when i click to cnahge snmp profile on mikrotik devices all dude-client hag-up and close. Since i didn’t find the page where i can change the default port for dude client.
Also it is possible to migrate from windows to mikrotik devices.
Some advices ?
Are you running latest version? I haven’t noticed such issues with snmp setting configuration.
For a while no TheDude uses the same port as Winbox. It cannot no longer be changed separately from that.
https://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/MigrationToNewDude
Hello.
I have migrate succesfully from windows to 750gr3 box, is is fast enought to keep working with this.
Migration was easy and keept all my setting : except…i don’t know why but devices like ubnt and bdcom OLT unit’s monitor’s verry vell, but switches like alcatel and dell show’s the snmp status but when i build a link i noticed that in snmp tab => interfaces it is empy. But snmp wal work’s fine, community is right one, i see all the data i need form the switch, still in the ethernet tab under snmp is empy.
On other ubnt devices all are ok. From wich side to dig.
Strange…
seem’s to me this is a similar problem
http://forum.mikrotik.com/t/snmp-problem-whit-rb260gs/107552/1
also can be and update for this thread
https://forum.mikrotik.com/viewtopic.php?f=8&t=116508&p=597555#p597555
Why oh why is Mikrotik so utterly useless at providing documentation and instructions for new users? I have a hEX with 32GB of flash memory and The Dude server installed. The purpose is specifically to allow us to evaluate whether The Dude will fill our requirement for a program to monitor a rapidly growing network of WISPs with Mikrotik routers and CPE units. I have the Windows client installed on a Windows 10 laptop. The laptop is directly connected to the hEX unit. The whole arrangement fails at the first hurdle as I am completely unable to get the client to connect to the server following the instructions (minimal) in the Wiki manual. If it can’t do this easily, what can anyone expect if we were to adopt the software for production purposes? I am simply fed up with struggling with the difficulties of coping with Mikrotik firmware & tools. Cheap & cheerful is all very well on a small scale but it is hopeless when you need to scale up an operation.
We could, of course, sign up with one of the suppliers that offer monitoring & control software for WISPs, but that is a commitment of several thousand dollars per month and eventually ten of thousands of dollars per month. It is much more likely that we will move away from relying on Mikrotik routers except for niche purposes . Instead, we will swap to an alternative source which offers management tools that work and we can rely upon. Well that is asking a bit too much. Still, even though most of us have a love-hate relationship with Ubiquiti, their tools tend to work (eventually!) and their documentation/support is far better.
Really, beforre yealing here that anything is wrong.. be shure to read properly manual not for mikrotik but for L2 and routing properties too. I read your post twice and i really don’t understand what you really want from your notebook 
I think here are more seriously problems like hundred of unit’s without monitoring after migrating on hex device. THINK..how many laptops run by this units
and yeah.. by the way. almost forgot…google give’s as answer second link .
https://wiki.mikrotik.com/wiki/Manual:The_Dude
some miracles happen here i think
Please read what I wrote carefully. Then get someone without any prior knowledge of The Dude to follow the instructions given in the Wiki on how to (a) install The Dude server on a hEX, and (b) install The Dude client on a Window 10 machine - remember that The Dude client is only available on Windows. Finally, start up the client and try to connect to the server. There isn’t a 1% chance that this will work. One reason is that the default port in the client is wrong. The references to users & passwords are ambiguous. In practice, I suspect that the default Windows 10 firewall configuration will block the attempt. And so on. There is no reason why it should be necessary to know anything about routing to get a basic server & client working together.
My comment/complaint was aimed mainly at Mikrotik support. I don’t care about what it is possible to do with Mikrotik equipment if you are prepared to spend enough time learning the quirks of RouterOS. I have to take a commercial decision as to whether it is worth making a commitment to buy thousands of units per year with the implications of having to cope with the support problems that arise when our users start to change settings, etc. I have previously commented on the side effects of making changes in QuickSet. My interest in The Dude is as a tool for mass upgrades and configuration monitoring. Using the hEX was just a simple test because I had a spare one available. I didn’t want to waste time setting up a dedicated virtual machine or a CCR for the experiment. If The Dude doesn’t pass the most basic test, then why devote more time to what is likely to be a dead end?
The larger point is that for deployment of such equipment on a large scale it is essential to have management tools that work reliably and are properly documented. Like many other operators we use a mixture of Mikrotik and Ubiquiti equipment. There are many times when I despair of the problems caused by Ubiquiti’s firmware and software, but they understand the market and are trying to do the right thing. I don’t think that this is the case for Mikrotik. Cheap and cheerful isn’t adequate when you have to worry about support on a large scale.
To reinforce the point, go to the manual page which describes how to change the server settings: https://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/Server_settings. This bears no relationship at all to the Webfig page accessed via: Dude > Server Settings that you get on the hEX with 6.39.1. The latter consists of a single page with no tabs and a large number of unexplained entries in boxes. Either the documentation is completely misleading or something has gone gravely wrong with the mmips version of The Dude.
I suspect that there are a lot of other features in 6.39.1 that have not been properly converted to mmips architecture. As a simple illustration, try to use the Terminal interface with Chrome. It flashes continuously. The same happens with MS Edge but not Firefox or Brave. I have also encountered problems with the default firewall rules, etc, etc.
The particular annoyance is that this whole thread was designed to announce the possibility of using The Dude on the latest version of the hEX, yet it is clear that the combination has never been properly tested other than by insiders who know the system too well to ask whether the documentation and features actually match.
It is you, gah789, who did not passed the test. Not the dude. I would like to see you how you are complaining about the building materials and technical documentation for them when your house is not standing as tight as expected. If you lack experience invest into getting the knowledge or hire an experienced consultant. Complaining about yourself here will not help you much…
For the sake of Mikrotik I hope that you are not expressing the view of their Support team. In English there is a standard business precept - the customer is always right. The spirit is important - don’t abuse your customers no matter how stupid you may think that they are. Mikrotik is a company that relies upon its community forum to support its products. Forums that are populated by people who are more concerned to demonstrate their superior knowledge than to help are more likely to drive away business. I appreciate the dilemma faced by Mikrotik support in handling issues of this kind, but in commercial terms it is foolish to treat even inexperienced customers as idiots.
I come back to my basic point. I have a business requirement to test The Dude on a medium for which use of the new hEX is convenient. I am unable to access the server despite following all of the manual advice rather carefully. In my view, either (a) the documentation is incomplete or wrong, or (b) there are problems with the mmips implementation of the software. What do I do next? I don’t have days to waste on the problem. If I cannot resolve it quickly, I will file the experience, conclude that Mikrotik is clearly not ready for commercial deployment on a reasonable scale to meet our needs, and get on with something else.
As for the rest, you might think about how this interchange might appear to the rest of the world. Certainly, I haven’t encountered this kind of attitude in dealing with problems with Ubiquiti equipment - and there are enough of them! The last time I checked Ubiquiti had about 4 times the gross revenue of Mikrotik in a sector where they directly compete. Perhaps there is a lesson for someone to learn from that. Telling me to hire a consultant may be self-serving and is certainly foolish. I am not going to do that and the suggestion that a consultant is required for a not very complicated matter is further evidence of the limitations of Mikrotik equipment in a commercial context.
I have no relationship to mikrotik company and I am expressing just my own humble opinions. Nothing more. Comparing with you, I run the dude (also) in 750Gr3 immediately without any problems including the data migration. And I haven’t needed to check the documentation at all for that. Maybe because I am playing with dude for years? Spending a lot of time to gather a knowledge? Definitely yes. I understand your reasons to go by other way. It’s your choice. I was talking about experience and not about any mental insufficiency like the idiocy is. Your words about that, not mine.
Sure you can decide whatever you believe is the best for you. Maybe the dude is really not mature enough to be implemented by you. Select whatever better and cheaper solution you want.
And please, think again what you do when asking for help… No technical info about your network structure, nothing about how the dude running device is configured, nothing but kicking around and telling to the world that you were not able to understand documentation. Well. What else have you expected as an answer?
Allow me to give you one advice. If you have to fulfil a business requirements, do it professionally. Otherwise you will be failing again and again.
I just bought 2 of these 750gr3 things because the first place I ordered one from was unable to ship for 2-3weeks. So I ordered another from elsewhere. Big mistake, can’t get either one to install Dude, so now I have an extra one and the project is over a month late.
I inserted a 64Gb microsd chip. I formatted it to ext3. I updated the routeros to 6.39.1, I downloaded the dude for mmips 6.39.1.npk and put it on the sd chip disk1. I reboot the system and login with winbox and Dude is not running, the wiki says it’s supposed to start running after reboot!
I get: “bad command name dude (line 1 column 2)” when I input “/dude print”. The terminal does not like the word “dude”.
I would really appreciate some assistance