In order to improve Dude v6/v7 we will collect feature requests from this forum
If your desired feature is not yet implemented and you cannot find it in list below, you can create a separate feature request post with detailed description - and your feature request will be added to this post.
It will help to discuss each feature in its own topic in order to help developers to understand what should be done.
I really would link to see a dude integration with the google maps API. I imagined a specific field where you would put the location Address and when you hover the mouse over this icon the pop-up window would show the location on google maps. Here is a quick mockup that i made for these feature.
I would also like to request better device linkages. Being able to move the location that the link connects to on the device, being able to give a smooth curve or rigid angle to a link, moving the device label on the link. Pretty much anything that can keep me from needing to do this.
To represent multiple networks going to and from the same devices. E.G. A storage network and a data network for server clusters running off the same switch.
Network Maps:
It would be handy to have a user-option that can rotate through the Network Maps on say a 10 second/predetermined cycle showing all the elements laid out.
For a visual output in a SysAdmin’s office it could then bring to attention any devices down, especially where a Flash or Popup may lock to the Map a device has failed on.
In a few places we are looking at old refurbishing old WinXP Thin Clients (the type that erases an unsaved session on reset) to standalone Dude clients for this exact purpose. So far a static map of the main network is very handy but adding this would be one heck of a next step up!
Hello,
It would be awesome to add an automatic and manual export option of map as it was in the (very) old 4.0beta3 version.
The map could be sended by ftp, for instance…
I used to export this map and then create a planned task that send this page through FTP to a web site. I was then able to offer my users a simple view of our network…
Really essential
I’d like to have import/export between winbox ( Addresses.CDB / addresses.WBX ) and Dude. We have multiple engineers installing devices. Every once in a while we merge the winbox addresses so we all know each customer box(es). For firmware updates dude will be more effective.
Also access to multiple dude server instances from within one client session.
Finally, move devices from one network-map to another
/system scheduler
add interval=1d name=backup on-event=backup policy=
ftp,reboot,read,write,policy,test,password,sniff,sensitive start-date=
nov/04/2015 start-time=03:00:00
/system script
add name=backup policy=
ftp,reboot,read,write,policy,test,password,sniff,sensitive source=“# Set l
ocal variables. Change the value in "" to reflect your environment.\r
\n\r
\n:local hostname "dude";\r
\n:local password "pass-ftp"\r
\n:local username "user-ftp"\r
\n:local ftpserver "10.36.8.12"\r
\n\r
\n# Set Filename variables. Do not change this unless you want to edit the
_format of the filename.\r
\n\r
\n:local date ([:pick [/system clock get date] 0 3] \\r
\n. [:pick [/system clock get date] 4 6] \\r
\n. [:pick [/system clock get date] 7 11]);\r
\n:local filename "$hostname-$date";\r
\n\r
\n# Create backup file and export the config.\r
\n\r
\nexport compact file="$filename"\r
\ndude export-db "$filename.bkp"\r
\n\r
\n:log info "Backup Created Successfully"\r
\n\r
\n# Upload config file to FTP server.\r
\n\r
\n/tool fetch address=$ftpserver src-path="$filename.rsc" \\r
\nuser=$username mode=ftp password=$password \\r
\ndst-path="/rsc/$filename.rsc" upload=yes\r
\n\r
\n# Upload backup file to FTP server.\r
\n\r
\n/tool fetch address=$ftpserver src-path="$filename.bkp" \\r
\nuser=$username mode=ftp password=$password \\r
\ndst-path="/dude/$filename.bkp" upload=yes\r
\n\r
\n:log info "Backup Uploaded Successfully"\r
\n\r
\n# Delete created backup files once they have been uploaded\r
\n# so they don’t accumulate and fill up storage space on the router.\r
\n\r
\n/file remove "$filename.rsc"\r
\n/file remove "$filename.bkp"\r
\n\r
\n:log info "Local Backup Files Deleted Successfully"”
Hello. Here we are used to use The Dude as we think its an awesome network monitoring tool.
One little thing is really annoying me, which is monitoring BGP Routers.
When we enable the RouterOS checkbox, all those routes (more then 1.2 million) would be read by The Dude.
If I enable SNMP, this also occur, which makes The Dude go crazy when a link become unavailable and all those routes need to disappear from the router.
So, would be possible to create a checkbox to not import routes from these types of routers?
This would be really effective as we could monitor all those services behind these routers but with only this exception.
I did read about many interfaces (used to appear in a PPPoE Server) also make this kind of behavior.
Maybe two checkbox, one about PPP interfaces and another about Routes.
In addition to more granular user permissions, as requested by @ffrauter, could the users be authenticated using Active Directory, LDAP or RADIUS rather than just locally defined users in The Dude?
