Probe 2092 shown as offline for a month
Hi there, My v1 probe #2092 has been showing as offline for a month, despite being powered up and pinging. Yesterday I power-cycled it, and it came back up and answers pings again, but the Atlas control panel still shows it as disconnected. Is there any troubleshooting I can do to get more information? I've verified that I can ping it from my internal network. There's no egress filtering which would be blocking it from talking outbound. I've just had my router log new outbound connections then power-cycled the probe again. I saw it successfully obtain an IP via DHCP (10:13:21), then 31 minutes later, connected to oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK times). I have verified that another box on the same network can connect to that IP & port: [davidp@columbia:~]$ telnet 193.0.19.12 443 Trying 193.0.19.12... Connected to 193.0.19.12. Escape character is '^]'. SSH-2.0-OpenSSH_5.3 Anything else I can do to provide more useful info? Cheers Dave P -- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
Hi Dave, On 2014/08/06 12:02 , David Precious wrote:
I've just had my router log new outbound connections then power-cycled the probe again. I saw it successfully obtain an IP via DHCP (10:13:21), then 31 minutes later, connected to oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK times).
Any chance there might be an issue with the DNS resolver that is used by the probe? Philip
On Wed, 06 Aug 2014 12:24:45 +0200 Philip Homburg <philip.homburg@ripe.net> wrote:
On 2014/08/06 12:02 , David Precious wrote:
I've just had my router log new outbound connections then power-cycled the probe again. I saw it successfully obtain an IP via DHCP (10:13:21), then 31 minutes later, connected to oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK times).
Any chance there might be an issue with the DNS resolver that is used by the probe?
The DHCP server gives out the IP of my internal gateway/router (a Linux box) as the DNS server to use; that's the box all other devices on my network use, too, so if it had problems I'd certainly have noticed! Presumably the probe attemptign to connect that one observed time means it resolved that hostname, no?
On 2014/08/06 13:51 , David Precious wrote:
The DHCP server gives out the IP of my internal gateway/router (a Linux box) as the DNS server to use; that's the box all other devices on my network use, too, so if it had problems I'd certainly have noticed!
Presumably the probe attemptign to connect that one observed time means it resolved that hostname, no?
I changed something in the probe setting to make it connect even if DNS resolving doesn't work. When that takes effect it will be possible to figure out what is going on exactly. Philip
On Wed, 06 Aug 2014 14:20:34 +0200 Philip Homburg <philip.homburg@ripe.net> wrote:
On 2014/08/06 13:51 , David Precious wrote:
The DHCP server gives out the IP of my internal gateway/router (a Linux box) as the DNS server to use; that's the box all other devices on my network use, too, so if it had problems I'd certainly have noticed!
Presumably the probe attemptign to connect that one observed time means it resolved that hostname, no?
I changed something in the probe setting to make it connect even if DNS resolving doesn't work. When that takes effect it will be possible to figure out what is going on exactly.
I see a connection now. In digging around more to get more logs of what's going on, I think I found the culprit: for security, I'd denied the probe from talking to my home server/gateway (but maintaining forwarding to elsewhere) as it has no business talking to that box (or anything else internal). However - that also stops it doing DNS from that same box - d'oh! In other words, looks like I was being an idiot and the problem was at this end! Thanks for your assistance - will keep an eye on the Atlas control panel to see it appear online. -- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
participants (2)
-
David Precious -
Philip Homburg