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] Зaщита прав cобственности
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Tue May 21 15:56:09 CEST 2013
* Antony Antony > 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 Not just the global one, as I mentioned earlier it had stopped responding to link-local pings as well. It seemed like the entire IPv6 stack was dead, to be honest. In any case, I rebooted it now and now it responds fine to IPv6 pings again, both to its global and link-local addresses. > Do you have another V6 router where you can plug it in Not at home, but I can connect it straight to my ISP's cable modem via a L2 switch (not behind my HGW as it is today). However my ISP does not use SLAAC, only DHCPv6 IA_NA - I don't know if the Atlas probes have gotten support for this nowadays? Otherwise I could always bring the probe to work and connect it there. Tore
- Previous message (by thread): [atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure
- Next message (by thread): [atlas] Зaщита прав cобственности
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]