Automatic IPv6 due to broadcast

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Mon Apr 23 11:27:53 CDT 2012


On Mon, 23 Apr 2012 11:23:14 -0400, Chuck Anderson said:
> > On Mon, Apr 23, 2012 at 06:38:09AM -0700, Owen DeLong wrote:
>> In a lot of cases, enforcing that all address assignments are via DHCP can still be
>> counter-productive. Especially in IPv6.
> If a specific managed environment provides DHCPv6 and doesn't provide
> SLAAC, and the policies of said environment forbid static addressing,

That's totally different from Owen's "in a lot of cases".  Incidentally,
there's absolutely nothing preventing a DHCPv* server from being configured to
always hand out the same IP address to a given MAC address, making it
effectively static (in fact, I've seen more than one site that carries nailed down
DHCP entries for servers, just to ensure that even if the server gets borked and
decides to DHCP itself, it will still come up with the "right" address anyhow).

> how can enforcing the use of DHCPv6 be counter-productive?

Remember, Owen was talking about "in a lot of cases". I suspect Owen was saying
that if you enforce that all source addresses are ones that the DHCPv6 server
handed out, you just broke a host that tries to do RFC4941 addresses or other
similar things.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20120423/1aafe44e/attachment.bin>


More information about the NANOG mailing list