Ive been looking around to try and figure out how to monitor a device outside our network using dyndns. As far as n can see THE DUDE can only use IP’s and on the dyndns name. is it possible?
i found a .sh script that can give me the IP from the WAN device using:
either using
curl http://www.whatismyip.org
or
wget http://Www.whatismyip.com -O - -o /dev/null | grep '<TITLE>' | sed -r 's/<TITLE>WhatIsMyIP\.com \- //g' | sed -r 's/<\/TITLE>//g'
The idea is to try and use scp to copy a file with the IP to my ubuntu server running THE DUDE and uploading the IP for the device in THE DUDE (using command line or something). does anybody know if there’s a easier way to do this?
The dude will do a DNS lookup at set intervals and change the IP to match the returned result… I have not used it and the device should be down while the address does not match but it is there. Just put the FQDN in the DNS Names: field and set the lookup interval to a low value.
The server is on another remote network. They have an ADSL Internet connection, so the IP of their connection changes, because they don’t have a public IP.
I have set up a dyndns account with an updater installed on their network.
At the moment I set the agent address to the “public” IP address assigned to to their ADSL router, but that changes.
If I could let my agent connect via the FQDN then I won’t have to manually change the agent address configuration on my Dude.
Ahh yes so that should work, just set the dns update time very low like 2 minutes and set the polling up on those devices to 2 minutes or more with 3 failures then you should always get the IP address and probes should stay up.
