> Can I get more than one IPv6 address?
>
> A single IPv6 address can be assigned to your Linode for free.
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 last account activity. It was a temporary hack to shoe-horn v6 addresses into their management system.
Everything in ipv6 assumes a /64 is the basic unit of allocation. For example, the stateless autoconfiguration system that replaces much of DHCP assumes it has a /64 to work with.
Linode probably has 4 billion /64s to play with (with options on trillions more if they should need it), why not give out one per customer?
To my knowledge (and I may have missed something) Linode is one of the first VPS providers to do IPV6. So I thought this was awesome.
If lots of other VPS providers start doing IPV6, and don't charge for a /64, or charge less than Linode does, Linode will have to change their fees or lose customers. But until that happens, why bash Linode for an as-yet unspecified charge?
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:
"We'll also be rolling out support to have an entire /64 routed to one of your IPv6 Linodes, which you can then route wherever you please."
From what I remember, the instructions were that ISPs receive no less than /32, which should provide end-users either /48 or /56. End users use the remaining 8-16 bits to partition their networks in /64 subnets. /64 is the minimum routeable prefix, and is the prefix used for automatic configuration.
Linode offering /128 for free and /64 at a cost is ridiculous. Users will have problems to forward since that would require breaking the /64 into smaller networks (to have at least one distinct subnet at each end of the tunnel), which is not possible for radvd.
As a further datapoint, I have two systems with native ipv6, and each have a /64.
Even so though tunnel brokers give out /64's and having to pay for that with native support would be rather silly.
This will be a phased roll-out across the facilities, starting with immediate availability in Fremont, Newark in a week or so, followed by Dallas.
From the FAQ[1] page:
Fremont, CA: Yes
Dallas, TX: Soon
Atlanta, GA: No ETA
Newark, NJ: About a week
London, UK: Q4 2011