There's no firewall / ACL, anything on the way, just pure L3 device. Probe worked properly, then disconnected without any logical reason with that notification received. Probe is pingable on both IPv4 and IPv6 from outside, proper (so there's no L3 issue on the way). Probe itself resets all incoming TCP connections from my IP address located in another ASN (probably due to firewall at the probe). On traffic mirrored from the probe I see ocasional NTP queries to some servers, so "something" on probe runs. Nothing else. You do not provide any access to probe for hosts to check anything directly, so I expect you can manage fully (as this is something running any kind of Linux?). As probe has public IPv4/IPv6 address, you should not have problem reach it. Unfortunatelly, probe is located on remote datacenter with limited physical access. Also this is not a solution of problem - with reboot you probably loose anything to diagnose causes of this problem. What checks did you performed at your side before sending such email? You don't have any kind of "emenergency" probe management, like SSH shell access directly to the device? What do you see in *your* logs about affected probe before it was disconnected? With regards, Daniel On 22.7.2014 11:17, Alastair Strachan wrote:
Hello Daniel,
Thanks for your email.
It would appear there is something on your network blocking the probe from connecting outside your network. Could I ask you to double check to ensure there is no security/firewall rule that has been updated or needs updating to allow the probe a clean connection outside your network.
I would also recommend trying a complete power recycle on the probe.
Thank you for taking the time to host a RIPE Atlas probe.
If you have any further questions, please let me know
Kind Regards,
Alastair Strachan
RIPE Atlas Team
RIPE NCC Customer Satisfaction Survey Tell us about your customer services experience by filling out the anonymous, three-question RIPE NCC customer satisfaction
survey:https://www.ripe.net/contact/survey/satisfaction-cs/
On 18.7.2014 05:40, RIPE Atlas wrote:
Dear RIPE Atlas probe host,
Thank you for participating in RIPE Atlas!
We have noticed that your probe is not connected to our infrastructure and has been disconnected since 2014-07-11 03:15 UTC. Could you please check whether everything is set up correctly on your side? If it is, and your probe is still reported as disconnected when you log in at https://atlas.ripe.net, please reply to this email so that we can follow up.
You can review the instructions for setting up your probe at https://atlas.ripe.net/getting-started
If you have any questions, please contact us at atlas@ripe.net
Best regards,
RIPE Atlas Team
********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.