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

Hi Tore,
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.

Olaf Maunz, Now I see IPv6 on you probe V6 measurements are working again. May be it rebooted on its own. I will look into the details later.

Laurent Wattieaux, could you please let me know your Probe ID. You could drop me a private mail if you prefer that.

We have seen this on couple of probes, however, yet figure out the details and a solution. We know the place were we saw the issue, it repeats. So it is good to have few more cases reported. May be we can use your help to debug and solve the problem. Thanks for all reports. 

We will increase the priority of chasing this bug. So far the symptom is after a reboot, some time later the probe unconfigure all V6 addresses. The case were we saw it most frequently was using a Fritz Boz 7270; i think.  There is no userland client for RA so it is a bit hard to debug. We are trying add code to report the RA announcements seen by the probe. 
regards,
-antony




On Sun, May 19, 2013 at 04:57:39PM +0200, Tore Anderson wrote:
> * Daniel Karrenberg
> 
> > Thank you for letting us know and also for speaking up to let us know
> > this happens to more than one of you. We will look at this after the
> > holiday weekend. In the meantime it would help to know the type of
> > the routers and details about your IPv6 routing configuration.
> 
> FYI, in case you want to debug this problem present on a live probe, it
> appears to be the case for probe 121 at the moment. It's connected
> behind an AVM Fritzbox using SLAAC. No other devices connected to it
> have a similar problem.
> 
> The probe should have had the IPv6 address
> 2a02:fe0:cf16:70:220:4aff:fec6:cd7a (which actually shows up on the
> probe's web page), but it does not respond to anything - not to ICMPv6
> NS from the local link to the aforementioned address, nor to
> fe80::220:4aff:fec6:cd7a. No responses from its link-local address is
> seen when pinging ff02::1 either. All the default measurements says
> "Cannot send".
> 
> If you have no use for this debugging opportunity, let me know and I'll
> reboot the probe and see if its IPv6 connectivity comes back then.
> 
> Tore
> 
>