I use Dude4 on a laptop with Windows7 Ult. 64bit to monitor about 30 Mikrotik/RouterOS PCs. I connect to the internet through 2 connections at home. One is an USB HDSPA modem 7,2Mbit, which I use mostly on travel, and second is my home LAN ISP through a router. When I use the modem (typically slow speed), Dude runs very well, no latency on services’ events, Winbox starts immediatelly, SNMP data is rapidly updated. BUT when I use my LAN ISP (no matter with/out my router), Dude services time out too much, Winbox often stops at “Connection Info” (logging to ... port 8291) and after a while > ERROR occurs > “router has been disconnected”. Otherwise, ping to sites, download/upload, torrent speed, are good and stable, so the ISp would not act about my complains. When I connect through a free Wifi spot in the city, everithing is OK, so I must believe that the problem is not in my hardware/windows config, but in my ISP. Could somebody please give me a clue, where is the problem? How could the provider interfere? Could it be a session limit which is exceeded by Dude ping services? Is it possible that the port 8291 is blocked somehow only from time to time? Is it possible to be a cable problem - my dog has bitten the FTP cable partly?
Thanks in advance!
Now I’m obliged to use the modem entirelly, and my traffic limit will exceed soon.
There are a multitude of things that could be causing your issues at home from just high latency or simple QOS monitoring by your ISP. The best way to set it up is to have a computer in the network running the DUDE monitor and then connecting to that machine remotely via web or the DUDE client. This way you also have the ability of keeping track of status’s even when your home computer is not up and running. You will still get a history of anything that happened and you can also setup alerts for when something does happen.
What type of ISP do you have at home. DSL, Cable, Wireless??? Cable and wireless providers are going to be the worst for running this type of service as their QOS policies will cause you many headaches. The big thing to remember is that the traffic that the DUDE generates is going to look like virus or attack activity to an ISP and there is a good chance that their system will automatically throttle your connection.
Most companies will not talk to you about their throttling policies as it is a very sticky and legally grey area. You can try to google search your isp for what ports and services they block and sometimes you can find some vague info about their throttling policies. In general however every ISP states that it is against their terms of service to host any type of server on their service and for very good reason. Technically the DUDE is a server and you probably will not get any help from the ISP to try and support it. That is why it is better to have the server on the network and connect to it remotely. Keep in mind that I say all of this while running the operations side of a small market ISP.
