Hallo Jan,

According to RFC 4861, section 6.3.6 and 6.3.7, ipv6 supports a default
router list, so router fail-over seems to be is built-in and the ipv4
shared default gateway virtual-ip setup combined with gratuitous ARP no
longer seems necessary?

Anne

Jan Kasprzak schreef op 7-11-2013 11:22:
>       Hello,
>
> is there anybody who uses heartbeat for HA Linux routers with IPv6?
>
> We use a pair of Linux routers with heartbeat. For IPv4, it works and it
> is simple: on each VLAN, the routers use a virtual IPv4 address, held
> by the active router. Network hosts use this address as a default gateway
> (either statically configured, or learned via DHCP). When the failover
> happens, the virtual IPv4 address is taken over by the newly active router,
> gratuitous ARP is sent by this router, and the packets start almost
> immediately froling through the newly activated router. The routers
> even share the netfilter conntrack table using conntrackd.
>
> For IPv6, the situation is more difficult: As with IPv4, both routers
> share a global virtual IPv6 address, held by the active router.
> However, we use a stateless autoconfiguration (SLAAC) on several VLANs,
> so the active router runs radvd(8), and advertises itself as a default
> gateway. The problem is that radvd does not advertise this global virtual
> IPv6 address as the default gateway, but it uses its own link-local address
> instead, as required by RFC 4861 section 6.1.2. When the failover happens,
> only the global IPv6 address is migrated, and clients attempt to use
> the old link-local IPv6 address instead.
>
> How do you configure HA IPv6 routers with RA/SLAAC? Would for example
> be using a link-local virtual IPv6 address feasible? Can radvd be
> configured to use a particular LL address in advertisements out of
> several LL addresses available?
>
>       Thanks,
>
> -Jan Kasprzak
>


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to