Yaaaaay! =)

It has been a month since this announcement, so can you give us any updates? Has there been any progress you can mention? I don't mean to sound impatient, I'm just excited about (soon) having native IPv6 support on my Linodes! This thread (with nearly 37,000 views and more than 100 posts) shows that a lot of us are.

NetRange: 2600:3C00:: - 2600:3C03:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR: 2600:3C00::/30
OriginAS:
NetName: LINODE-US
NetHandle: NET6-2600-3C00-1
Parent: NET6-2600-1
NetType: Direct Allocation
NameServer: NS4.LINODE.COM
NameServer: NS1.LINODE.COM
NameServer: NS2.LINODE.COM
NameServer: NS5.LINODE.COM
NameServer: NS3.LINODE.COM
RegDate: 2011-02-07
Updated: 2011-02-07
Ref: http://whois.arin.net/rest/net/NET6-2600-3C00-1

OrgName: Linode
OrgId: LINOD
Address: 329 E. Jimmie Leeds Road
Address: Suite A
City: Galloway
StateProv: NJ
PostalCode: 08205
Country: US
RegDate: 2008-04-24
Updated: 2010-08-31
Comment: http://www.linode.com
Ref: http://whois.arin.net/rest/org/LINOD

OrgNOCHandle: LNO21-ARIN
OrgNOCName: Linode Network Operations
OrgNOCPhone: +1-609-593-7103
OrgNOCEmail: support@linode.com
OrgNOCRef: http://whois.arin.net/rest/poc/LNO21-ARIN

OrgAbuseHandle: LAS12-ARIN
OrgAbuseName: Linode Abuse Support
OrgAbusePhone: +1-609-593-7103
OrgAbuseEmail: abuse@linode.com
OrgAbuseRef: http://whois.arin.net/rest/poc/LAS12-ARIN

OrgTechHandle: LNO21-ARIN
OrgTechName: Linode Network Operations
OrgTechPhone: +1-609-593-7103
OrgTechEmail: support@linode.com
OrgTechRef: http://whois.arin.net/rest/poc/LNO21-ARIN

RTechHandle: LNO21-ARIN
RTechName: Linode Network Operations
RTechPhone: +1-609-593-7103
RTechEmail: support@linode.com
RTechRef: http://whois.arin.net/rest/poc/LNO21-ARIN

RAbuseHandle: LAS12-ARIN
RAbuseName: Linode Abuse Support
RAbusePhone: +1-609-593-7103
RAbuseEmail: abuse@linode.com
RAbuseRef: http://whois.arin.net/rest/poc/LAS12-ARIN

RNOCHandle: LNO21-ARIN
RNOCName: Linode Network Operations
RNOCPhone: +1-609-593-7103
RNOCEmail: support@linode.com
RNOCRef: http://whois.arin.net/rest/poc/LNO21-ARIN


For reference, Linode's snail address is:
Linode, LLC
329 E. Jimmie Leeds Road
Suite A
Galloway, NJ 08205

There has been progress. We typically don't announce ETAs for stuff, but it is coming.

-Chris

Also noticed this..

inet6num:       2a01:7e00::/32
netname:        EU-LINODE-201100201
descr:          Linode, LLC
country:        GB
org:            ORG-LL72-RIPE
admin-c:        TA2589-RIPE
tech-c:         TA2589-RIPE
status:         ALLOCATED-BY-RIR
mnt-by:         RIPE-NCC-HM-MNT
mnt-lower:      Linode-mnt
mnt-routes:     Linode-mnt
notify:         tasaro@linode.com
changed:        hostmaster@ripe.net 20110201
source:         RIPE

organisation:   ORG-LL72-RIPE
org-name:       Linode, LLC
org-type:       LIR
phone:          +16095937103
fax-no:         +16152504945
e-mail:         support@linode.com
abuse-mailbox:  abuse@linode.com
admin-c:        TA2589-RIPE
mnt-ref:        RIPE-NCC-HM-MNT
mnt-ref:        Linode-mnt
mnt-by:         RIPE-NCC-HM-MNT
changed:        hostmaster@ripe.net 20091102
changed:        bitbucket@ripe.net 20091106
changed:        bitbucket@ripe.net 20091110
changed:        bitbucket@ripe.net 20091110
changed:        bitbucket@ripe.net 20110128
source:         RIPE
address:        Linode, LLC
address:        Thomas Asaro
address:        329 E. Jimmie Leeds Road
address:        Suite A
address:        08205 Galloway
address:        UNITED STATES

person:         Thomas Asaro
address:        329 E. Jimmie Leeds Road, Suite A, Galloway, NJ 08205, USA
phone:          +16095937103
nic-hdl:        TA2589-RIPE
mnt-by:         Linode-mnt
changed:        tasaro@linode.com 20101119
source:         RIPE

We've been anxiously tuned for more than two months now, so can you give us any updates? I don't mean to sound impatient, but my organization wants to participate in World IPv6 Day on June 8 and we're hoping to do so with our Linodes! Maybe you can tell us whether Linode is expected to offer native IPv6 (in at least one datacenter) by then, or if we should start making contingency plans now? Thanks!

My response is the same as it was 4 weeks ago: We are actively working on IPv6. Beyond that, I can not comment on its arrival.

-Chris

Why don't you set up a HE tunnel now and prove out your solution. If native IPv6 occurs in time then you have the choice of switching your DNS and config to that or stick with the HE tunnel (if timelines are tight).

Doing this now will verify that such a solution is viable (at least for Jun 8th) or allow you to work on an alternate plan if it's not.

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)

Hi Sweh. We have been using HE tunnels for years, but not for our production services. The HE tunnel broker is a wonderful free offering, but I don't think it is appropriate nor intended for high traffic production services. HE says it is "oriented towards developers and experimenters". HE also offers "business class commercial native IPv6 service" in the Fremont datacenter where all my org's Linodes are hosted, but since we aren't HE's direct customer, it is Linode corp that has to do some setup for this to work.

Caker said that native IPv6 support was "imminent" a couple months ago, and today he confirmed that they are still "actively working on IPv6". So I'm still holding out hope that they'll implement it in time for World IPv6 day. It is a shame that they won't provide any ETA or transparency about where they are in the process, but I can understand their reasoning. At least the IPv6 allocations discovered by sleuths on this forum are encouraging!

Most ISPs have no IPv6 and will not have it for many years. Which makes the whole exercise completely academic. A lot of people here use linodes for testing and fooling around, so IPv6 at linode actually makes some sense. But I agree with caker that it will be many years before IPv6 would become useful for people running production servers.

...I don't think my modem is even IPv6 capable it's oldddddd.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Consumer modems still doesn't do IPv6 themselves but that doesn't stop you running it in pass-through mode and using ppp on your computer to connect. That's how most people do it.

_________________
Why can I not enter my IRC info in the forum profile?

Unless you live in asia, where they're starting in on their last /8 and that means each company can only get a single /22. So that pretty much means it's going to be useful for them PDQ.

Given that all the RIR's will be on their last /8 before the end of this year native IPv6 is a must. Tunnels give twice the routing problems, additional delays, additional unpredictability, and reduced MTU.

Everyone has dragged their feet on this far too long, there is no way of avoiding IPv6 any longer.

Conclusion doesn't follow from premis.


Funnily enough, I have lower latency between my home (New York) and my Linode (fremont) when using ip6 via HE tunnels

ip4:
rtt min/avg/max/mdev = 95.170/97.108/97.899/1.193 ms

ip6:
rtt min/avg/max/mdev = 79.150/81.967/84.056/2.033 ms, pipe 2

_________________
Rgds

Stephen

(Linux user since kernel version 0.11)