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/ripe-atlas@ripe.net/
[atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
- Previous message (by thread): [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
- Next message (by thread): [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue May 21 09:42:54 CEST 2013
Hi, We'll work on fixing this issue. Please, if someone has a reilable way of reproducing the condition, send it to atlas-bugs at ripe.net. Thank you! On 2013.05.21. 7:37, Sulev-Madis Silber wrote: > Update. > > After pulling the plug, ICMP ping suddenly works from everywhere? WHAT? > > And probe runs all fine tests again... If you power cycle the probe, then it restarts it state too, meaning DHCP leases, SLAAC, whatever. That works all the time, but it's not very convenient... and it should be fixed. Cheers, Robert > On 2013-05-20 06:33, Sulev-Madis Silber wrote: >> What the hell is going on there? It's in "can't send" state again. And I >> somehow remember I could ping it outside of it's /64, now I can't. It >> doesn't respond. However now it answers to ICMP ping (inside of it's >> /64) and also talks NDP like it should. >> > >
- Previous message (by thread): [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
- Next message (by thread): [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]