Re: IPv6 VIPs and deprecated flag

* Ryan O'Hara

> > On the other hand if the VIP is a /64 it is most likely the only
> > address in the prefix (i.e., backup routers do not have global
> > addresses configured at all) and thus the above consideration does
> > not apply.  
> 
> That is interesting. Thanks for the information.

Oh and by the way, having a prefix length attached to a VIP is a
totally non-standard Keepalived protocol extension which probably won't
interoperate with any other VRRP implementaiton.

> On a related note, has anyone tried this with SLAAC? I've been
> investigating some strange behavior with IPv6 SLAAC where keepalived
> will initially bring up a VIP with /128 prefix and correctly set the
> deprecated flag, but after a few minutes I see the keepalived netlink
> reflector report the global IPv6 address and VIP are "added" (which
> seems to correspond to the lifetime being refreshed). As this point
> the IPv6 VIP loses the deprecated flag and the load balancer ceases to
> work. Thoughts?

That sounds really weird, considering that the Keepalived address
you're adding is not assigned using SLAAC. Must be a bug or some
connection manager gone haywire, maybe? Unless you're configuring
Keepalived with a VIP that's the exact same address as the node would
self-assign from SLAAC, that is?

Tore

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape