[LINK] IPv6 doomed

Adam Todd link at todd.inoz.com
Mon Aug 25 19:07:37 AEST 2008


At 05:36 25/08/2008, Frank O'Connor wrote:
>At 12:41 PM +0800 24/8/08, Adrian Chadd wrote:
> >On Sun, Aug 24, 2008, Frank O'Connor wrote:
> >>  Mmmm,
> >>
> >>  Good pick-up.
> >>
> >>  IPv6 has a number of other advantages over IPv4, other than 
> address space.
> >
> >Most of which don't really matter today.
> >The rest of the world widely deployed DHCP; autoconf sounds great in theory
> >but seems to be missing 10 + years of commercial DHCP development/features.
>
>Horses for courses. Just had an experience installing a new router
>that I could have really used IPv6 auto-config for. (Basically the
>router manufacturer provided a 'user friendly' front end app for
>doing same ... just click and it does the work. Yeah ... right! Three
>hours later after I'd undone all the damn garbage it had wreaked in
>the settings and manually installed the damn thing - which I should
>have done manually in the first place.)

And this is why I would NEVER use Autoconfig on any kind of device, 
unless it was for the purpose of seeing what the Device considered AUTO.

Sure it's possible for a new device to call out (without even using 
DHCP) to find ip addresses on a network, mac addresses of other 
hardware and then configure itself to join the party, but do you 
REALLY want that kind of instability in your network?

The power goes out and all your devised renumber themselves, 
seemingly randomly.

DHCP is great for a roving environment where you don't need to know 
the workstations specifically.  but when you have printers that need 
to be identified and loaded into DNS, or gateway hosts that need to 
be on a specific address, you don't want them auto numbering and configuring!

Yes, yes, you can always have the device add it's 'name' to the DNS, 
if your DNS server is configured to do that, but most people have 
trouble knowing what a DNS is yet along configuring and loading data into one!






More information about the Link mailing list