Hello, This mail may be of help: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2017-June/003329.html Background info: slide 6 of https://ripe74.ripe.net/presentations/74-ripe74-mat-atlas-update_v2.pdf Regards, Robert Kisteleki On 2017-07-12 21:44, Matthieu Herrb wrote:
Hi,
Here at Tetaneutral.net we're hosting a V1 Atlas probe since 2012 or so. A few weeks ago it started beeing marked as unconnected on the ripe atlas page : https://atlas.ripe.net/probes/523/
Since it's a v1 probe, I can only power cycle it to try to reconnect it, which I've done a number of times now, without success.
It's still answering to ping requests, both on its v4 and v6 addresses and I can see some traceroute-like trafic going out of it.
It's marked as "firewall problems suspected", but we don't do any firewalling on it. On IPv4 it's on a 1:1 NAT, all ports are open and forwarded in both directions, and on V6 it's routed without any filtering. Also we haven't changed anything on our infrastructure around the time it became disconnected.
I'm starting to suspect a firmware upgrade problem as the one mentionned by Alun Davis in https://www.ripe.net/ripe/mail/archives/ripe-atlas/2017-June/003329.html
Any suggestion before I send it back and ask for a new one ?
Thanks in advance,