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 suddenly lost IPv6 connectivity
- Previous message (by thread): [atlas] Probe suddenly lost IPv6 connectivity
- Next message (by thread): [atlas] Upcoming "Measurements Tools" Workshop for LIRs: 19 September, in Amsterdam
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Aug 11 17:02:19 CEST 2014
On 2014/08/11 16:47 , Ondřej Caletka wrote: > Dne 11.8.2014 15:06, Ondřej Caletka napsal(a): >> Hi, >> >> strange thing happened today. My probe v2 #3467 suddenly lost IPv6 >> connectivity and reconnected to the control server using IPv4. The probe >> does not even respond to ping6 ff02::1%eth1 sent from the router. >> >> I wonder what could cause such behavior. I will try to reboot the probe >> once I'll reach it. > > Hi again, > > at 16:09, the probe started to respond to ping6 again. Strange. According to our logs your probe lost its IPv6 address around 11:43 UTC and got it again around 14:10 UTC. The most likely cause is that the probe didn't receive and router advertisements during that period. The probe lost its default route around 10:19 UTC. There is however the issue that the Linux kernel on the v1 and v2 probes has a bug that it may get in a mode where it doesn't receive router advertisement multicasts anymore. So if it happens again, it may be worth replacing the probe with a v3 probe. Philip
- Previous message (by thread): [atlas] Probe suddenly lost IPv6 connectivity
- Next message (by thread): [atlas] Upcoming "Measurements Tools" Workshop for LIRs: 19 September, in Amsterdam
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]