VRRP failover and not having the route injected is a good point, although I could mitigate that with a lower lease time a little. I prefer to get V6 working. Plus, its dual stack we are talking about, V4 access is still available.
Maybe a VRRP-DHCPv6 relay state table share would be nice to handle that. Although V6 still needs a lot more attention to get to that point. -----Original Message----- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Baldur Norddahl Sent: Saturday, September 23, 2017 1:52 AM To: nanog@nanog.org Subject: Re: DHCPv6-PD -> Lack of route injection in RFC This method is lacking because you might have several routers eg. using VRRP and the backup router will not learn anything from a relay on the primary. Den 22. sep. 2017 14.02 skrev "Steve Teusch" <steve.teu...@rtr.guru>: I am running into venders that do not support injection of a delegated route when operating as a DHCPv6 relay (or server for that matter). Brocade supports this, but I am not finding this as part of any of the RFC's. This is to deliver home ISP service, so it is very important or return packets won't go to the client unless the route is manually added as a routing protocol is not an option. There should be a MUST activity for this somewhere. Anyone know what gives?
