[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
using "reserved" IPv6 space
- Subject: using "reserved" IPv6 space
- From: mysidia at gmail.com (Jimmy Hess)
- Date: Tue, 17 Jul 2012 01:16:32 -0500
- In-reply-to: <1342502946.6281.164.camel@karl>
- References: <CC29A9B4.8578D%[email protected]> <2059648.BTFFAkdkz4@lsdsrv> <4742592599634568524@unknownmsgid> <1342500058.6281.154.camel@karl> <CAAAwwbUOq3FNTOUd=f+90QDz03Bhcecu4vgzXB2sEBOQG-aXaQ@mail.gmail.com> <1342502946.6281.164.camel@karl>
On 7/17/12, Karl Auer <kauer at biplane.com.au> wrote:
[snip
> I'm not sure I follow the logic there. If the anycast router changes the
> packet will be resent to the new subnet anycast router eventually
> (assuming some layer cares enough about the packet to resend it). The
> "last known hardware address" doesn't matter any more or less in this
> scenario than it does in any other routing situation.
The pertinent discussion is not about "any other routing situation";
it's about first hop redundancy.
The "last known hardware address" is in the NDP table, so the packet
retransmissions likely wind up in the same place
Another problem is the subnet anycast address may find unwanted
routers that have to listen on it, including routers with only one
interface and incomplete routing info, and including some
unauthorized 5-port IPv6 router someone smuggled into the
building and plugged in somewhere.
By contrast, a real FHRP that implements failover either uses a
virtual hardware address, or a 'gratuitous arp' type mechanism, so
the packet retransmissions will go to the live failover partner.
--
-JH