[188035] in North American Network Operators' Group
Re: IPV6 planning
daemon@ATHENA.MIT.EDU (Mark Tinka)
Sat Mar 5 16:47:05 2016
X-Original-To: nanog@nanog.org
To: Laurent Dumont <admin@coldnorthadmin.com>, nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Sat, 5 Mar 2016 23:46:59 +0200
In-Reply-To: <56DB4D6C.9080504@coldnorthadmin.com>
Errors-To: nanog-bounces@nanog.org
On 5/Mar/16 23:19, Laurent Dumont wrote:
> Hiya,
>
> We are currently considering deploying IPv6 for a Lan event in April.
> We are assigned a /48 which we then split into smaller subnets for
> each player vlan. That said, what remains to be decided is how we are
> going to assign the IPv6. Basically, it seems that are two ways, one
> SLAAC where the endpoints uses RA to generate it's own IP and DHCPv6
> which is basically DHCP but for IPv6.
>
> Large events like Dreamhack have used SLAAC and the feedback has been
> mostly positive. Can anyone comment regarding past experiences with
> IPv6 gotchas and things that you don't really expect when running
> dual-stack on a large-ish network?
SLAAC is the way you want to do, as DHCPv6 does not give you a default
gateway.
If you want IPv6 DNS resolvers, DHCPv6 is a good option, which means a
hybrid of DHCPv6 and SLAAC is reasonable.
Mark.
