Slashdot Mirror

← Back to Stories (view on slashdot.org)

One Less Reason to Adopt IPv6?

Posted by ryuzaki0 on from the adopt-a-puppy-instead dept.

alphadogg writes "For a decade, IPv6 proponents have pushed this upgrade to the Internet's main communications protocol because of its three primary benefits: a gargantuan address space, end-to-end security, and easier network administration through automatic device configuration. Now it turns out that one of these IPv6 benefits — autoconfiguration — may not be such a boon for corporate network managers. A growing number of IPv6 experts say that corporations probably will skip autoconfiguration and instead stick with DHCP, which has been updated to support IPv6."

8 of 174 comments (clear)

  1. But... by gzerphey · · Score: 5, Funny

    from the adopt-a-puppy-instead dept


    But puppies don't have a "gargantuan address space" or end-to-end security. Trust me, puppies leak all the time.
    --
    I don't have a microwave. I do, however, have a clock that occasionally cooks shit.
    1. Re: But... by Bogtha · · Score: 5, Funny

      Not to mention the fact that sniffing is a constant problem.

      --
      Bogtha Bogtha Bogtha
  2. DHCP in an IPV6 world by morgan_greywolf · · Score: 5, Interesting

    DHCP in an IPV6 world is a buggy whip. It's not necessary. An IPV6 device can discover its own IP address and gateway router and subnet mask (if necessary) without the help of any servers because it's built into the protocol stack.

    DHCP doesn't give a network admin any more control over a network, either. That's just a silly statement. How does having a server doling out IP addresses make it any easier to control a network? It's not a like a device *must* be set to use DHCP. It's not difficult to figure out what IP address ranges a DHCP server is not doling out and use that, even on IPV4.

    --
    My blog
    1. Re:DHCP in an IPV6 world by igjeff · · Score: 5, Insightful

      DHCP does a whole lot more than that.

      The reality of the situation is that stateless autoconfig in IPv6 is one way to get basic networking connectivity setup, DHCP is another. Depending on your situation, the phase of the moon, and any of a number of philosophical viewpoints held by the network admin, stateless autoconfig might or might not get used. *shrug* Even with stateless autoconfig, DHCPv6 might also get used to configure other information that is not handled by stateless autoconfig (DNS servers, NTP servers, any of a huge list of other things).

      The important point to remember, though is *2 YEARS*. That's how long we have until the IPv4 address space is fully allocated at the top level. It may take a little longer (months?) before people start really feeling any pain from that at the end-user level. But its the critically important point for people to realize. Can you be ready for IPv6 in 2 years? You need to be. If its gonna take you 2 years to get IPv6 functioning in your network, then you need to start *NOW*.

    2. Re:DHCP in an IPV6 world by markom · · Score: 5, Informative

      DHCP doesn't give a network admin any more control over a network, either. That's just a silly statement. How does having a server doling out IP addresses make it any easier to control a network? It's not a like a device *must* be set to use DHCP. It's not difficult to figure out what IP address ranges a DHCP server is not doling out and use that, even on IPV4. I beg to differ.

      DHCP combined with modern network infrastructure allows network administrators complete control over all addressing issues in the network - including preventing non-DHCP hosts from participating in the network (called DHCP snooping) and location-based services ("DHCP option 82"). DHCP is so much more than just a kludge to get an IP address to the host. Scalability of DHCP allows network administrators to append information such as DNS, NTP, TFTP (for IP Telephony/TV) server information and so much more - default gateway, static routes just to name few. All this is pretty much lacking from IPv6 autoconfiguration.

      That's why we tend to like DHCP ;-)

      Marko
      CCIE #18427
    3. Re:DHCP in an IPV6 world by afabbro · · Score: 5, Insightful
      The important point to remember, though is *2 YEARS*. That's how long we have until the IPv4 address space is fully allocated at the top level. It may take a little longer (months?) before people start really feeling any pain from that at the end-user level. But its the critically important point for people to realize.


      Son, they've been saying that for 15+ years.

      Yes, there is a limit. But once IPV4 address space at the "top level" becomes scarce, it will be handled according to the rules of any scarce commodity - it'll become more expensive. That will encourage efficiency, free space from wasteful users, etc. Then we'll get close again, lather rinse repeat, etc. We will eventually hit the point of "full" but it's not like in September 2010 suddenly there will be no more routable IPs for the next system that needs one.

      --
      Advice: on VPS providers
    4. Re:DHCP in an IPV6 world by asuffield · · Score: 5, Informative

      The important point to remember, though is *2 YEARS*. That's how long we have until the IPv4 address space is fully allocated at the top level. It may take a little longer (months?) before people start really feeling any pain from that at the end-user level. But its the critically important point for people to realize. Can you be ready for IPv6 in 2 years? You need to be. If its gonna take you 2 years to get IPv6 functioning in your network, then you need to start *NOW*.


      About once a year I investigate the current state of ipv6 support, and every time so far I have found every major operating system (including linux-based ones) to be inadequate to the task of deploying ipv6. The software support is just not there, on both the system and application levels. Sure, I can configure ipv6 interfaces on hosts and even have some of them set up tunnels and talk to each other, but it is entirely impossible for me to configure a non-trivial network without ipv4 support on every host and still expect it to work, so there's no damned point.

      NAT is the solution to the address space problem. Get used to it, because ipv6 has spent the last five years failing to become a solution. When we finally run out of ipv4 addresses, we aren't going to switch to ipv6, we're going to switch to using NAT at the ISPs. You won't get an internet-routeable address for anything other than a server, after that happens - regular DSL lines will be allocated an address from one of the private ranges and NATted onto a smaller pool of routeable addresses as they leave the ISPs network.

      It's going to come down to a choice between a technology that has spent years going nowhere and a technology that has spent years being used as the solution to the problem. I know which way the ISPs are all going to jump.
  3. Why Not Both by maz2331 · · Score: 5, Insightful

    Autoconfig is a nice default for something that "just works" without much need for an admin to plan out the network, and DHCP is great for tighter control where needed. What's wrong with having both options available?