Hello,
is there a possibility to get notified if the probe has lost IPv6 connectivity?
At the moment it seems to me, notification only works if the connection is down
with both protocols.
Regards,
Thomas
Hi RIPE-Atlas team,
my ripe probe 2303 shows as being up and running, it is connected in a NAT
environment.
The probe does not show data for the Built-Ins (e.g. No data available for
2303 / 1009 for this time period) as well as is not participating in
measurements.
Can you check/confirm that it is not broken or advise what I would need to
do to make it work like other probes please?
Thanks & Regards
Henry Schaefer.
[image: Verizon Business Ready] <http://www.verizon.com/business>
Henry Schaefer
Verizon Business Markets
Elisabethstraße 29-31
12247 Berlin, Germany
O +49 (0)30.7669.1525 | M +49.173.262.8459
henry.schaefer(a)de.verizon.com
[image: Facebook] <http://www.facebook.com/verizon> [image: Twitter]
<http://twitter.com/verizon> [image: Instagram]
<http://www.instagram.com/verizon>
======================================================================
Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig - Vorsitzender des Aufsichtsrats: Francesco de Maio
Hello,
Since this week based on report [1], [2] from Martin we were able to
observe his issue, which he reported and by using Atlas SW Probe 5010
and older, we noticed that in CLI probe is running and that it is doing
something, but on the RIPE website, it shows that probe is disconnected.
Can you please check probes IDs (1000585, 1000243) and what it took so
long to show that it is connected? Both of those probes were shown as
connected at the same time - 20:22) on Tuesday? We noticed that in some
cases if you were using the latest version 5020 and register a new
probe, it is working within a few minutes.
However, we pushed to all our Turris OS version updated Atlas SW Probe
to version 5020 and some of our users noticed similar maybe the same
behavior. A probe was running on the router, but it was disconnected
for almost an hour (probe ID 1000036)
The router is working in all cases, ping, dig connection is OK.
I'm wondering if this issue isn't on server side.
In reg_init_reply.txt were following data:
WAIT
TIMEOUT 115
Do you know how to debug it more?
[1] https://forum.turris.cz/t/turris-os-5-0-0-is-released-in-hbt/12733/149
[2] https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/38
Looking forward to hearing from you,
Jan
