> Le 28 avr. 2016 à 00:28, Chris Buechler a écrit :
>
>>
>> Sure, I'm not helped by the transit provider which does not actually route
>> the /56 prefix to my link (savages!) but merely 'switch' it to me, expecting
>> ARP/NDP from
>> each of my connected devices, and me using one dedicated IP
On Tue, Apr 26, 2016 at 7:38 AM, Olivier Mascia wrote:
>> Le 26 avr. 2016 à 00:37, Olivier Mascia a écrit :
>>
>> It looks like as soon as I bring IPv6 to the party, my secondary starts
>> thinking it's MASTER instead of BACKUP. Sometimes on the WAN side, sometimes
>> on the LAN, sometimes both
> Le 26 avr. 2016 à 00:37, Olivier Mascia a écrit :
>
> It looks like as soon as I bring IPv6 to the party, my secondary starts
> thinking it's MASTER instead of BACKUP. Sometimes on the WAN side, sometimes
> on the LAN, sometimes both. Quite hard to describe, I'm still trying to
> build up a
It looks like as soon as I bring IPv6 to the party, my secondary starts
thinking it's MASTER instead of BACKUP. Sometimes on the WAN side, sometimes
on the LAN, sometimes both. Quite hard to describe, I'm still trying to build
up a reproducible test case on my 2.3 cluster. So out of the blue,