I am sorry Norman, it didn't work. I installed Dude 3.1 (choosing not to install the server files). When I run the dude it found that the server is running on local machine (local server is up and running and enabled all the time)!!I think that's in already. Just deselect server package when installing thedude.
Turn off server autostart still just to make sure I may be wrong though.
No make a version for Mac OSX!Please make a Linux version
we are already working on that.Also request: "Possibility to reboot all devices or change passwords at once"
Vote @ http://wiki.mikrotik.com/wiki/MikroTik_ ... e_Requests
Nice, Thank You!we are already working on that.Also request: "Possibility to reboot all devices or change passwords at once"
Vote @ http://wiki.mikrotik.com/wiki/MikroTik_ ... e_Requests
Great news... they added it a while ago.Two successive versions in a short time!, I was expecting a major issue resolved in one of these updates;
"SMTP Authentication "
For me this is a primary feature that needs to be introdced in the next version of The Dude.
Can we hope for it?
Agreed. ACKs should be autocancelled after transition to UP status. Should at least be an option...Example. i have chain of some hosts, one host is down, i hit "Ack", and forget it. After some time host is up, all is fine, but when host is down again, he is allready acknowledged. i think its wrong, and every time, when acknowledged host is up, he must be automatically unacknowledged.
Or maybe i can configure if somewhere?
First and foremost you have the best network management product on the market and it is free. I believe that if it was managed correctly you would expand your market dramatically and improve networking everywhere. Who is the original programmer of the dude? I am sure others are also interested to know...
I'd like a feature where bugs that are found can be requested to be fixed and they would get fixed with out desperation (for the user and the developers) on the other hand if you open the source this would not be such a high pressure situation. The neat and orderly position of the users would make these fixes trivial. It is easy to see that having a great management product simplifies users needs and benefits your long term position.
I understand the plans are to move to a database solution. This is a nice step in the right direction but people have been waiting months for simple bug fixes. I made a desperate plea which moved from the dude from 3.3 to 3.4 but I felt I was out of bounds asking for fixes for free software.
MikroTik is running in serious networks and has a real potential to crack the market open. It has gained significant ground by many people trying to make their network management enjoyable. The trouble is there has been no official word about the future and when things are going to be looked at.
I have been posting for quite a while helping where I can and I plan to continue to help. There are some great ideas and many worthy requests that should be implemented but the environment feels stale. The requests for upgrades and bug fixes keep coming...
Documentation has mainly been through this forum and some old wikis but I want to impress on you that this free product is the groundwork for something much bigger. I see the original intent was to create an environment that fosters usage of your products. That has worked wonderfully (if not than this plea is useless) but I also believe that it is time to move forward and let the users have what they want. The users want a place where they can see a coordinated attack on problems and solutions being offered in a shorter time span. (Go look at the guy with the as400 snmp issue, never solved). Sure you can't solve every problem but if you solved his trouble would he recommend router boards or cisco?
So my plea is for you to recognize that you have a wonderful product (which you should already know) and it is the foundation to much greater things but it needs nourishment. Make the right choices here. Make bug fixes a priority, add a schedule that has a release every 3 months or so and consider opening the source after all the dude is so sweet!!!
By looking at this forum, I am getting the impression that The Dude, while an excellent start, is not going anywhere very fast. It looks like development is at the authors whim.I am 100% with sweetdude regarding this issue. I almost daily check on MikroTik's site wishing there is an updated version for Dude.
Many users pray on that, but we can only hope and waitThe author should:
A. Make The Dude open source so that development can be much more robust.
What about ack/unack?I wish the ability to DISABLE a device on a nwtwork map.
The disabled device is not polled by dude and it doesnt send alerts.
thanks
iPad only has a small market share (only 3mio sold units).Hi All,
what about Dude for IPad?
Sonny
Actually it's not a same that i told you. Currently i have to do Unack manualy, but i wanted to have mode, when device will come back from Ack to normal mode automatically or to limit time of Ack mode. Cause I have alot of technical guys and they control and solving problem without me. One thing they cannot do - UnAck when they solve work.Ack Unack is made exactly for the purpose you describe. This is to mark a known problem, and unmark it when it's fixed. It's to keep the device from sending alarms during fixing time.
+11. Please Dude on linux............................................!!!!!!!!!!!!!!!!!!!!!!1
+1. Agree with you.Please finish command line support, many items are missing, once completed you would open up a wide range of possibilities with scripts. We may automatically add discoveries to our networks and create maps fully automatically.
Well, yeah, that's just, like, your opinion, manDUDE is dead isnt it?
I was joking, but that seems to be the reality. But ideally MT still fix bugs and/or make minor improvements in the shipping version...MT is developing new monitoring tool and they freeze development on Dude if Im not wrong.
You can add the dude router as device and monitor it. If you can't, perhaps firewall blocks winbox/etc ports?Is there any way to monitor in Dude router on which is Dude installed?
If you add your Dude as a device, at least ping should show up as probed service. If that does not work, something else is wrong.I will check the firewall but how can FW block ports when the dude is on that server? What shoul I allowed?
+1 add this fitur please!
Something in the firewall be my guess. ICMP should always be allowed by default, but if blocked that cause probe not work. If you able to ping, but not "connect" as a RouterOS device, I try an "accept" on TCP 8291 in firewall filter, with log enabled to find out the IP address Dude is using.status is unknown and Routeros can not connet even when is 127.0.0.1 allowed in firewall and ping is working. What could be problem?