Live data from Hacker News

Linode launches native IPv6 support

blog.linode.com

31–40 of 53 posts

Re: Linode launches native IPv6 support

#31

> Can I get more than one IPv6 address? > > A single IPv6 address can be assigned to your Linode for free. I hope this is a misunderstanding -- if not, it's actually a huge step backwards. The current solution for IPv6 in linode (HE tunnel to static IPv4 address) gives each node a full /64. It could be argued that this is a bit excessive, but it seems fairly typical, and lets you do useful things like serve multiple…

Is there a guide somewhere to get HE working with Linode?

Just follow the HE tunnel setup instructions like you would for any non-linode host or border router.

Re: Linode launches native IPv6 support

#32
While the geek in me thinks this is really super cool, the realist in me wonders why on earth I would need an IPV6 address _now_. All though we're "out" of IPV4 addresses, no hosting company has run out (I can still get all the IPV4 based VPS's & dedicated servers I want). Maybe I care 4 years from now, but I'm not sure I really care now... except it is really cool.

Re: Linode launches native IPv6 support

#34

> Can I get more than one IPv6 address? > > A single IPv6 address can be assigned to your Linode for free. I hope this is a misunderstanding -- if not, it's actually a huge step backwards. The current solution for IPv6 in linode (HE tunnel to static IPv4 address) gives each node a full /64. It could be argued that this is a bit excessive, but it seems fairly typical, and lets you do useful things like serve multiple…

I think we should give Linode the benefit of the doubt on this for now. Depending on how their instances are isolated from each other, it may be difficult to handle prefix delegation all the way down through the individual hosts into the guests. Even Google had some hacks when they first started bringing up IPv6 support. For example, GMail would display class E addresses instead of the v6 addresses when you viewed la…

As I understand it, they don't yet have any automation for setting up /64 prefix routes yet, so every /64 deployed has to be manually added to the router configs. Anyway, you're free to set up your own routing rules using that /64 to forward subnets of it on to different linodes.

Re: Linode launches native IPv6 support

#35
post #21
post #18

Earlier quoted context omitted.

The owner of Linode (caker) has clarified on IRC stating that the /128 will be provided to each node, however they will also provide a /64 per datacenter, per account upon request for a nominal fee. The /64 will be routed to your /128 so that you can control how the addresses in your /64 are handed out. The fee has not been disclosed, yet.

So in short it isn't a misunderstanding and they want to charge you per item for something that, for all intents and purposes, is like a single drop of water in an ocean.

They want to charge you for the static route you've added to their (finite) router memory, and the administrative overhead for adding it when they don't have the process automated yet.

Re: Linode launches native IPv6 support

#36
post #11
post #4

Wow, just one IPv6 address for free, pay for the rest. Granted, you're paying for addresses pooled among hosts with failover, which could be well worth paying for. But come on Linode, a single IPv6 address allocation is ridiculous. Update: Found this post by caker (linode guy) http://forum.linode.com/viewtopic.php?t=7055&highlight=i... He mentions a third option involving a /64, does not mention if it will cost extra…

For perspective: IANA instructs RIRs to allocate no less than a /32 to each customer. That leaves 32 bits for those customers to resell smaller subnets, usually /64. 32 bits is as much as the entire IPv4 Internet, so they can sell as many /64 subnets as there are individual computers on the IPv4 Internet. So even if Linode only bought 1 of these /64 subnets, they would have 64 bits of address space to allocate to the…

Linode has a /30: http://whois.arin.net/rest/net/NET6-2600-3C00-1

Re: Linode launches native IPv6 support

#37

While the geek in me thinks this is really super cool, the realist in me wonders why on earth I would need an IPV6 address _now_. All though we're "out" of IPV4 addresses, no hosting company has run out (I can still get all the IPV4 based VPS's & dedicated servers I want). Maybe I care 4 years from now, but I'm not sure I really care now... except it is really cool.

This is the perfect time to get practice using IPv6, so you're not scrambling when it _does_ get scarce :)

Re: Linode launches native IPv6 support

#38
post #37

While the geek in me thinks this is really super cool, the realist in me wonders why on earth I would need an IPV6 address _now_. All though we're "out" of IPV4 addresses, no hosting company has run out (I can still get all the IPV4 based VPS's & dedicated servers I want). Maybe I care 4 years from now, but I'm not sure I really care now... except it is really cool.

This is the perfect time to get practice using IPv6, so you're not scrambling when it _does_ get scarce :)

That's a really good point. Although if it's just for practice I's rather wait for it to come to EC2 and just pay by the hour to practice.

Re: Linode launches native IPv6 support

#40
post #36
post #11

Earlier quoted context omitted.

For perspective: IANA instructs RIRs to allocate no less than a /32 to each customer. That leaves 32 bits for those customers to resell smaller subnets, usually /64. 32 bits is as much as the entire IPv4 Internet, so they can sell as many /64 subnets as there are individual computers on the IPv4 Internet. So even if Linode only bought 1 of these /64 subnets, they would have 64 bits of address space to allocate to the…

Linode has a /30: http://whois.arin.net/rest/net/NET6-2600-3C00-1

That's equivalent to 4 /32 subnets, or 2^34 = 17,179,869,184 /64 subnets. I think they could afford to give each customer a /64.

IPv6 subnets don't really get smaller than /64. The way the routing is configured, the first 64 bits are "network address" and the last 64 bits are the "interface address". One /64 subnet has 2^64 addresses, about 18.4 quintillion.

Post reply on HN