Well i suppose i should say my dude client stop responding whilst it is connected to the dude server and i try to open the device settings.

We had about 6 machines each with dude installed checking our system. i have however recently been experimenting with the server functions and had the rest of the machines connect to my machine and my machine be the server.

However, i am currently trying to run a different configuration. we pulled out of one of our towers an RB532 and replaced it with a RB433. well i updated that RB532 to v3.30 and installed dude 3.6 on it. i client to it and have setup one device, our core router.

now everytime i open the device settings on this device the client stops responding.

Please if someone could help me with this

This has happened to me before but i wasn't able to find out why. I ended up removing the device i added and renamed it after i added it back. Since then it hasn't crashed. Wasn't sure if name was long or some characters cant be used. Does this sound like it could be the issue?

This used to happen in 3.x version of the dude, if you waited long enough you would see some crazy number of services discovered... deleting the device and re-adding was the solution.

well then, i suppose i should try the v4 of the dude server

I wonder if it will work on a 5 series board