Time to try IPv6


It’s World IPv6 Day.  You can go to IPv6 right now with your DragonFly system.  If your ISP doesn’t support IPv6, you can try a sixxs or HE tunnel.  Also, nag your ISP about it.

Posted by     Categories: DragonFly, Goings-on     7 Comments
7 Comments on Time to try IPv6

Respond | Trackback

  1. Corey says:

    Why nag my ISP? My IPv4 still works fine. I mean, if you just want to play with it, then great, but unless you need a lot of externally-accessible IP addresses, where’s the benefit, the driver, for adoption?

    I think a good number of people and companies are asking the same question, hence the need for “propaganda” events like World IPv6 Day :)

    All that said, it’s good for OSes like Dragonfly to have IPv6 implementations, in case users do have a need.

  2. Zoey4Ever says:

    @Corey

    You do know that the IANA address pool is fully depleted since jan 2011? You can’t build any new houses on the net anymore because there are no v4 street numbers left.

    So I’m waiting for v6 only sites and I’m pretty sure this will come in the near future.

  3. Falling isn’t so bad, it’s the sudden stop at the end that causes problems. Everything’s great when there’s still some IPv4 addresses left; it’s when that suddenly stops that there’s going to be abrupt issues.

    It can be dealt with by private addressing and NAT, sure, but I don’t like being stuffed into a private network by my providers. I would lose the ability to have shiningsilence.com located where it is, for instance.

  4. Christian Sturm says:

    There are also some other benefits.
    http://en.wikipedia.org/wiki/IPv6#Comparison_to_IPv4

  5. Corey says:

    @Zoey: Yes, I know we’re out of IPv4 addresses. But apparently my ISP has enough; they are in no apparent rush. I run a private net in my house, and we do similarly at work. Therefore, no rush for me or my employer. I know though that this attitude contributes to the chicken-and-egg problem that IPv6 faces, but man…if it’s my money, and it is going to cost a good bit of it to go to IPv6, and I don’t get more in return for that effort, I’m not going to jump all over it.

    I did go out and do a little reading on it, and some of it kinda scares me. The irregular use of the bits in the address for all the special cases, the separation of address assignment from routing information…it just seems it could have been done more simply. Oh well, that ship has sailed I guess. I’ll just wait awhile longer, for the icebergs to melt, before I take a cruise.

  6. Winston Weinert says:

    Hopefully our friend Corey and his employer will not miss out on any new major web services launched (or perhaps expanded). It will become tricky to get legacy addresses for all the servers that require an address to function as it was designed to.

  7. Steve O'Hara-Smith says:

    One of the best reasons for IPv6 is that it’s getting hard to get a public static IP address at home, and even harder to get more than one.

    Anyone who has ever tried to get VoIP services up and running from inside a NAT environment will attest that it’s a nightmarish task because of the port mapping that goes on through the NAT device. There are workarounds and they can often be made to work but it would be so much simpler just to have a routable address. For VoIP purposes a tunnel isn’t good enough, the extra latency is a problem so yes I nag my ISP and have been doing so for some time now, meanwhile I run a tunnel.

    Many other things require ports opened for them (web servers, games consoles etc.) and as soon as there’s more than one in the network NAT and port forwarding isn’t enough. I don’t really want huge numbers of addresses at home, but more than one would make life a lot easier and IPv6 looks like the only way we can all have that. The sooner I can ditch IPv4 the happier I will be.

Respond

Comments

Comments