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] 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 ]
Sulev-Madis Silber
madis555 at hot.ee
Thu May 23 04:09:27 CEST 2013
Here it goes again?! Global address unpingable and probe is even marked as disconnected, maybe it will try to reconnect over IPv4 later. Nothing like this happened before. Something is broken there I'm afraid. It's all the same router and everything. 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 ]