Date: Wed, 06 May 2009 11:25:25 -0400 From: Steve Bertrand <steve@ibctech.ca> To: af300wsm@gmail.com Cc: =?ISO-8859-1?Q?Odhiambo_=3F=3F=3F?=, =?ISO-8859-1?Q?=3F=3F?= <odhiambo@gmail.com>, John Nielsen <lists@jnielsen.net>, freebsd-questions@freebsd.org Subject: Re: Configuring an IPv6 router to assign addresses Message-ID: <4A01ABE5.5000508@ibctech.ca> In-Reply-To: <0016361e896051401204693fcf74@google.com> References: <0016361e896051401204693fcf74@google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
af300wsm@gmail.com wrote: > On May 6, 2009 8:56am, John Nielsen <lists@jnielsen.net> wrote: >> On Wednesday 06 May 2009 10:39:24 am Odhiambo ワシントン wrote: > > >> Is there a reason you need to control the addresses used by your clients > >> (other than the prefix)? I set up IPv6 on my LAN and while I have DHCPd > >> running on the router for IPv4 addresses rtadvd is all I needed for IPv6. > >> Clients assign themselves addresses based on the network prefix they > >> learn from route solicitation and their own MAC address. That's supposed > >> to be one of the "reduced administration" benefits of the new > >> protocol. :) > > > Thanks for reminding me of the flow in which this happens. Seems like I, > at sometime, got the idea that it was the router that dished back a > unique IP based on clients MAC and so forth. However, it seems to me now > that the router was only supposed to dish out the prefix, ie network id, > and the client would take that prefix and generate a unique IP based on > its MAC. Have a peruse of this RFC (stateless autoconfig): http://www.ietf.org/rfc/rfc4862.txt Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A01ABE5.5000508>