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 ]
Antony Antony
antony at ripe.net
Tue May 21 15:39:15 CEST 2013
Hi Tore, Yes I was hopping just unplugging the Ethernet cable would fix it temporally. and we can reproduce it again. It seems that was not enough. So lets reboot, unplug the USB an replug it, and if the problem re-appear shortly after that you could try to move to another v6 router? The logs show the laster time it for ~6 hours ors and then the probe dropped its Global V6 address Do you have another V6 router where you can plug it in regards, -antony On Tue, May 21, 2013 at 10:15:01AM +0200, Tore Anderson wrote: > * Antony Antony > > > Could you please unplug the ethernet cable and re-plug again? I want > > see if it repeats systematically. The last time after a reboot your > > probe had a Global V6 address for about an hour (~64 minutes) and > > after that the probe unconfigured all V6 addresses. > > Done. Note that I did not unplug the USB cable, so the probe remained > powered all the time. > > Tore > >
- 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 ]