Hello.
I run the dude on my rb333 with no problems, but when i use the dude on my rb133c it runs for a short time and then the rb133c crash. Then i have to shut down the dude and wait 5-10min before the rb133c starts up again or i have to do a power cycle.
When the rb133c crash, its also lost in winbox and telnet.
Anyone else having a problem with rb133c and the dude?
Regards
Brian Houge
Denmark
Your problem is the RB133’s CPU being way to slow to handle the DUDE.
I had DUDE running fine on a RB532A, but as my configuration grew, it started crashing until it wouldn’t work at all. Best is to run DUDE on a PC based router, or Windows PC.
If you use DUDE for notifications, I wrote a script to only send notifications, and make use of a PC Router for running the DUDE. If a power failure occurs, I still receive notifications, but can’t access the network map, which is better than nothing.
I’m sure a RB1000 would be much better for DUDE, but it is still rather pricey.