*) Added - AES encryption method for snmp v3
*) Added - Dude now have configuration interface in Winbox/Webfig
*) Added - Network maps now are viewable from web interface (Webfig)
*) Agents - Now any RouterOS device can be used as The Dude agent. It no longer requires
server package and ROS login. (Agents need to have same version as Dude server)
*) Agents - Old agent section removed from client.
*) Improoved - Changed SSL connection timeouts. This will reduce SSL CPU load when secure sessions are used
*) Removed - Since default Winbox used in the Dude wasn’t fully compatible with all RouterOS devices, we removed it completely.
Other changes:
*) Fixed - Bandwidth test tool. (broken since v6.37)
*) Fixed - Auto-discovery was adding devices with non-usable characters in name field.
*) Fixed - Issues with link not changing color when traffic grows.
*) Some improvements for DB data write in store.
*) Removed - Link label will not change colour on link speed change.
*) Fixed - Allow users without FTP policy to connect to dude server (access to files will be restricted).
*) Fixed - Discovery stayed in “finishing” status.
*) Fixed - Devices showed device_performance even if the host were down.
*) Fixed - Snmpwalk were broken on X86 devices.
*) Fixed - History charts was flapping if the monitored device were down.
*) Fixed - v4 backup import fail.
*) Fixed - Multi-core devices showed CPU usage only from one core.
*) Fixed - Error on dude RADIUS authentication.
*) Fixed - In some setups dude server caused memory leak on X86/CHR.
*) Added - Dude server now supports spectral scan up to 7Ghz.
*) Fixed - Dude db-import failed if server was disabled at the moment when import of old db was initiated.
*) Fixed - Dude client stuck on “getting stuff” state.
*) Fixed - Disk name were changed on RB hEX if the dude was used on USB flash or mSD card.
*) Fixed - default files will be stored in dude files folder if the file system does not support symlinks (fat32)
*) Fixed - avoid going into loop (Dude client could get stuck in loading phase)
*) Fixed - File upload to dude/file directory caused client crash
*) Fixed - Background images could disappear on version change
*) Fixed - Minor changes in Dude fonts
*) Added - Dude icon in Winbox/Webfig
*) Fixed - Increased default ping packet size to 54bytes - there was some devices who wasn’t able to respond with 32 byte ICMP packets, this caused ping corruption.
*) Fixed - Typo “Authetication” → “Authentication”
*) Fixed - Changes wasn’t saved if done in Winbox - notification body.
*) Fixed - Bandwith test authentication problem
*) Fixed - Resolve Windows environment variables
To avoid some problems related to Dude, follow these suggestions:
*) It is suggested to use only ext3 file format for the Dude data directory, it’s more stable for the Dude.
*) Store your custom files Only in dude/files directory
*) Custom fonts should not be used
Since default Winbox is removed, you can add path to your Winbox.exe file with simple step:
Open Tools => [+] sign => in “Command” add your Winbox path, for Windows users use:
%HOMEPATH%\Desktop\winbox.exe [Device.FirstAddress] [Device.UserName] “[Device.Password]” http://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/Tools
Is anyone else having issues with the tools > Winbox tool not showing up on the client for the Dude? I tried version 6.38 and 6.39rc4 and am getting the same result. I upgraded from the previous version 6.37.3 and had no issues.
Open Tools => [+] sign => in “Command” add your Winbox path, for Windows users use:
%HOMEPATH%\Desktop\winbox.exe [Device.FirstAddress] [Device.UserName] “[Device.Password]”
and what about wine and linux? is it possible to use winbox in this way ?
Since default Winbox is removed, you can add path to your Winbox.exe file with simple step:
Open Tools => [+] sign => in “Command” add your Winbox path, for Windows users use:
%HOMEPATH%\Desktop\winbox.exe [Device.FirstAddress] [Device.UserName] “[Device.Password]” http://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/Tools
Since in our office we connect to Dude from different locations, could it be possible to add use the winbox.exe stored in a remote path?
I see i can run only a “command” so i tried to run a powershell script which calls the remote winbox.exe but no Arguments like [Device.FirstAddress] [Device.UserName] “[Device.Password]” are used correctly.
Also, I was having difficulty with the script calling the program to run from my desktop because of my firewall / malware rules on windows 10. I was able to get it to work successfully once I placed winbox.exe in the program files under the dude and used that location in quotation marks as it is written below. I imagine it will work in any location you choose with quotations, but I prefer it to live in the default location with the dude program, so here is what my command line looked like:
Having problems with connectivity to the Mikroti AP.
One Mikrotik is doing DHCP, routing,… the other is AP.
When upgraded both of them, I cannot connect to the AP (which is connected via cable in the main Mikrotik router). I can’t event ping the AP.
If I set STP to none on main router (now is rstp), I can ping and connect to the AP. On both of machines there are few VLAN intefraces. Why is this happening after the upgrade?
My Networks are evolving, Is there a way to move devices between maps? I’ve created a MAP call Legacy,
which I would like to park devices that are not active or expired. Maybe there is a better way, like a Hide flag??
→ winbox can be added manually via tools.
is it possible to use winbox in this way ?
