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

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. 

Thank you again

Daniel

On 17.05.2013, at 18:32 , Laurent Wattieaux <laurent at laurent-wattieaux.com> wrote:

> Hello,
> 
> Me too
> 
> I've the same problem.
>> I have noticed the same. 
>> I have a IPv4 and IPv6 enabled router. Every time I reboot the router I have to restart the probe.
>> 
>> 
>> On 16 May 2013, at 23:32, Sulev-Madis Silber 
>> <madis555 at hot.ee>
>>  wrote:
>> 
>> 
>>> Hello.
>>> 
>>> Probe (v2) doesn't seem to recover from all network failures
>>> automatically. It currently connects using IPv4 and reports IPv6 tests
>>> as "can't send". I can't ping probe on IPv6 and it seems like it doesn't
>>> talk IPv6 at all on that VLAN, although router sends RA's every minute.
>>> In web interface it says that it has IPv6 address (all other things
>>> under IPv6 are "Undetermined/Unknown") but it doesn't actually
>>> participate in network at all. Only router talks IPv6 in that network,
>>> according to tcpdump.
>>> 
>>> I think not recovering from IPv6 failures is a bug. Somehow, it still
>>> recovers from IPv4 failures. Problem appeared after I had it physically
>>> disconnected from Ethernet for some hours. Before that, probe also
>>> didn't have connection to internet for a day. I wish I would not need to
>>> pull the power every time this happens. Although it's rare occasion that
>>> anything is down here.
>>> 
>>> 
>>> Thanks.
>>> 
>>> 
>> 
> 
> 
> -- 
> Laurent Wattieaux
> Gsm: 06 86 67 62 30
> 
> <gprofile_button-32.png>