This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] half dead v1 probe ?
- Previous message (by thread): [atlas] Probe does not request IPv4 address via DHCP
- Next message (by thread): [atlas] half dead v1 probe ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matthieu Herrb
ripe-atlas at herrb.eu
Wed Jul 12 21:44:15 CEST 2017
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, -- Matthieu Herrb
- Previous message (by thread): [atlas] Probe does not request IPv4 address via DHCP
- Next message (by thread): [atlas] half dead v1 probe ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]