News for hackers. Stuff that matters.

A comment on Linode - IPv6 Status and FAQ. Parent comment

Re:Linode - IPv6 Status and FAQ by pieter on Thursday May 05, 2011 @05:44PM (#2519023)
Good to see they're responding to the criticism so fast. Handing out /116's seems a bit of a weird choice, but that's not really a problem.

I'd be interested in hearing how they handle the routing within the data centers. Is it all just ethernet, and whoever uses ND (IPv6's ARP) to announce an address gets data to that address routed, or is are there some kind of subnets in between? How do they avoid someone stealing an address in your pool?

[ Parent | on HN ]
Re:Linode - IPv6 Status and FAQ by jmillikin on Thursday May 05, 2011 @06:41PM (#2519189) 

  > Handing out /116's seems a bit of a weird choice, but that's not really a problem.
My guess is that they're routing a /64 to each physical machine, and then /116s to the virtual systems.

4096 addresses is much nicer than just one, so I'm thrilled to see this change. Switching over from a tunnel right now.

[ Parent | on HN ]
Re:Linode - IPv6 Status and FAQ by pieter on Thursday May 05, 2011 @06:47PM (#2519210) 

  > My guess is that they're routing a /64 to each physical machine, and then /116s to the virtual systems.
That doesn't really work, as the /116 is shared among all nodes in the same DC. It also doesn't explain how SLAAC works, as all nodes in the DC get an address from the same pool (2600:3c01::/64 for instance).
[ Parent | on HN ]
Re:Linode - IPv6 Status and FAQ by RyanKearney on Thursday May 05, 2011 @06:31PM (#2519164)
My guess is each physical machine will be statically routed blocks. The hypervisor will then statically route smaller blocks to specific VMs.
[ Parent | on HN ]