[atlas] Probe doesn't seem to automatically recover from IPv6 connectivity failure

Just thoughts. And can't really confirm it at the moment. 

I am having the feeling that it depends on the simultaneous reboot of the probe and the router and some timed boot sequences. I can not reproduce it at the moment but when the probe's USB was plugged in the router and the entire router unplugged and restarted IPv6 failed. With the probe plugged into a different power source no IPv6 problems occurred when the router was power cycled. 
Each device at its own reboot fine with me. The problem might be when the probe reboots and the router is an undefined state. 



Sent from my iPhone

On 23 May 2013, at 09:56, Antony Antony <antony at ripe.net> wrote:

> Dear Silber,
> 
> may be at your location the problem is a bit more frequent? The other place i was watching, Tore's probe, is happy for 3 days. I am not sure this time it is address configuration error. If you look at the graphs of your probe #4415. I see a different pattern now. It is not Yellow, can't sent error, any more. Compare it on the weekly graph, week 19-20 and now.  May be some other issue?
> 
> So far, from my experience, Red is not IPv6 address disappearing error. Only a series of good results and yellow is the sign.
> 
> For details, you could download the data and look at it more closely. For example, look at the measurement ID 2001 pinging the K-root. Now it is working fine. The last time the error occurred for a few measurements and it seems to have recovered on its own.  The timestamp of the error is "time":1369197942
> 
> Never the less, we are sure there is an IPv6 RA related problem that affect a few probes. We are trying figure out a solution. However, the harder part is to reproduce it in a controlled environment where we have access and create a solution.  
> 
> The wired thing about this bug is there is one place with two probes on a same router and only one of them occasionally run into this problem.
> 
> regards,
> -antony
> 
> 
> On Thu, May 23, 2013 at 05:09:27AM +0300, Sulev-Madis Silber wrote:
>> 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.
>>> 
>> 
>> 
>