We have published the first public test of our restarted project The Dude. At the moment it is just a refreshed version of the same Dude software that we had in v4b3, but is adapted to work correctly with RouterOS v6 with a few minor changes in it. This will be a base on which we will start building The Dude for the future.
The Dude server is now a RouterOS npk package that must be updated together with RouterOS
The Dude client is pretty much the same as it was before just with server side removed. If it will detect that servers side is running newer version it will offer to update it self to matching version.
Removed features:
Windows server
Language selection for The Dude client
Web interface
Note that new The Dude client wont work with older versions and vice-versa
The Dude server packages and Windows client application are available for download under: Tile, CHR and x86 selections in the RC release chain.
Renewed documentation for current versions of The Dude (still work in progress): http://wiki.mikrotik.com/wiki/Manual:The_Dude
page.jpeg Known issues in v6.34rc45(updated) (reported for fixing):
All entries below are already confirmed and reported to DEV for fixing.
High priority problems:
Device discovery tool does not work with Agents.
Low priority problems:
Adapt dude link labels to be able to show 10G traffic
speed and larger (snmp part left to fix)
Enhancement requests:
Add checkbox in dude client loader to allow upgrade/downgrade without prompting
user each time.
Add option to use functions and oids in notification messages.
Fixed issues and added features:
Leftovers of web interface configuration is not yet removed.
Dude does not know how to show ROS version (broken due to
changes in ROS, update needed)
In log settings configuration, sliders are broken.
When opening panel in separate windows error pops up, it
does not affect the usage tho.
When changing icon appearance on network map dude does
not assign right image in some cases.
Open panel separately broken.
Spectral scan may crash Dude client
SNMP walk crashes the dude client
Torch tool in dude also is broken
Use of ping tool causes the dude client to disconnect.
Any section export to CSV function broken, crashes the dude client
Bandwidth test tool graphs broken.
XML backup import fails.
Large DB export fixed.
Link label - Mastering type: ROS broken.
Scan tool - removed for now till it’s reworked.
Telnet tool - dude will throw out error if telnet client is not available on system where
dude client is installed.
Dude tool - Corrected dude.exe launch path. Now the client will look for executable
in it’s installation dir and not by some full path.
Added 10G link type - Will be added by default only for new installations.
Torch tool - fixed.
Added option to run dude client from shortcut in secure mode by adding argument “–secure”.
Corrected 10G link monitoring/counters for ROS devices. (snmp fix for this will come later)
Fixed issue where dude client would freeze if link label mastering type was snmp
and it was created or modified.
Ping tool - fixed local pinger.
Auto discovery tasks are now separated between network maps.
Fixed file upload to server.
SMTP authentication and tls options added!
ROS upgrade function fixed
Fixed server crash that some people where experiencing.
CHR host upgrade fixed.
DNS name resolving fixed in loader (will however work only after loader is upgraded to rc45)
Added db vacuuming option
Added progress indicator to import/export/vacuuming
Dude server by default on new installations is now disabled.
Hmm.. Did you realize that you only need to install Dude-server to one router?
Also, as “quick and dirty workaround”, it’s probably possible to install x86- or CHR-ROS to virtual machine running on your Windows-machine and run Dude there.
Yep, you definitely should avoid “Windows-only” solutions and try to do this platform independently from the begin. And web interface is usually the easiest way.. But let see what happens, I love this already.
Maybe in future we could re-implement it through standard Gettext (PO) not like we had previously, time will tell how difficult it is. This is just the first step to re-opening Dude development, anything is possible now.
Hi Mikrotik Team (and others using the existing version)
At the moment I (and a number of people I work with) use Dude 4.0B3 on RB450G units as dedicated low power local monitoring units in locations. These are running only the Dude and have a MicroSD card inside them for storage. Also as CCR’s have begun to replace 1100AHx2 and 1200 devices I would love to be able to move these into service as Dude nodes.
I know this would be more development work for the team however I have found the 450G platform has plenty of power to run a reasonably sized node and I believe the PPC devices could likewise provide a fantastic platform and continue to make use of this hardware going forward.
If other people currently use the 450G and its ilk or have a number of PPC units they want to press into additional service and would see serious use from the Dude then please bring your use cases into a new Dude topic on use cases for other hardware platforms and hopefully we can make a compelling case for inclusion.
I can understand completely why MIPSLE may not be a good candidate for this development effort and the SMIPS platform as well, but to me the new ARM (3011) PPC (1100, 1000, 1200, 850) and MIPSBE (450, 2011) make brilliant monitoring and network administration boxes that work wonderfully for the Dude.
I know myself I use 1100AHx2 units and 450G units as network access gateways coming from the NOC, in datacentres there will be standard routers for user / public traffic and then one of the above units (depending on site size etc) with ports into various switchports / network segments and making use of VLANS and direct connections to provide an inbound direct NOC route into each L2 domain. These boxes are ex network routers which have been replaced or upgraded and have plenty of cycles free to run the dude.
Please consider adding ARM, PPC, and MIPSBE into the supported architectures for Dude ROS Package.
What winbox is included ?
It does not open my saved sessions. I have changed default path maybe that is the problem. I want to try to symlink them. And menu bar is not showing and I can’t open an existing session file.
R.I.P. Windows server. Oh well, we can’t have everything.
But it brings one problem. Dude can export maps as images. With Windows server, another webserver on same machine could read exported images and make them available for including in webpage. It’s not possible with RouterOS Dude, because the images are somewhere on the disk where they are not accessible to user.
What about saving the images to dedicated directory (not in “files” with all the other stuff; assuming it currently uses the same folder structure as on Windows) and making that available using the RouterOS webserver? Just add a symlink, so that images would appear under http(s):///maps/., it would be enough.
