True, but it's all too easy to setup the first address, and it makes it much more deterministic. After all, you're right there setting the DHCP server options. It's not going to kill you to add one more item (static IPv6 address), especially when said device is probably sporting a static IPv4 address for the same reason.
It's a good idea to go out and register your own IPv6 address space, any way. http://www.sixxs.net/tools/grh/ula/ *ASB *(My XeeSM Profile) <http://XeeSM.com/AndrewBaker> *Exploiting Technology for Business Advantage...* * * Signature powered by WiseStamp <http://www.wisestamp.com/email-install> On Tue, Jul 13, 2010 at 6:58 AM, Ben Scott <[email protected]> wrote: > On Tue, Jul 13, 2010 at 1:07 AM, Jon Harris <[email protected]> wrote: > > I was only referring to the server needing a fixed address not any of the > > clients. I have always thought that you had to have at least some fixed > > point to refer to when using DHCP that being the server or more correctly > > the server's address. > > So was I. With IPv4, that's a practical requirement, because the > only way[1] to get an address automatically is DHCP, and the DHCP > server can't get its own IP address via DHCP. Chicken-and-egg. With > IPv6, the DHCP server *could* configure its own address via SLAAC, and > then just hand out DHCP options (like DNS servers) when asked. Or at > least, so I suppose. I haven't read the RFCs. :) > > [1] This is an over-simplification, but good enough for our purposes. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
