Implementando IPv6

jmginer · 18 Ene 2013

Hola! estoy estudiando las opciones para implementar IPv6.
He pensado en asignar como mínimo un /112 a cada cliente. Esto son: 65535 IPv6.

Es decir, un grupo de cuatro dígitos hexadecimales completos:

Desde: 2a03:c7c0:0:0:0:0:0:0
Hasta: 2a03:c7c0:0:0:0:0:0:ffff

Como digo la idea es asignar dicho bloque a cada cliente, no a un VPS concreto de tal forma que el cliente puede enrutar sus IPs al VPS que quiera.

Por desgracia, SolusVM no trabaja así. Pero, ayer me decidí a contactar con el soporte de SolusVM. Les envié este mail (en espanenglish):

Dear support,

I claim about the IPv6 service, is a problem of concept, you can not assign same as IPv4.

/32 is the minium IPv6 network provided by RIPE, and I want provide a /112 to each customer, that is 65536 unique IPv6.

In my /32 IPv6 network I can create 120,892,581,961 (120,892 millions) of /112 networks, each network with 65536 of unique IPv6

Helpfull tools to understand IPv6
potato-people.com/blog/2009/02/ipv6-subnet-size-reference-table/
ultratools.com/tools/ipv6CIDRToRange

My full IPv6 range is 2a03:c7c0::/32, this is:

Start Range: 2a03:c7c0:0:0:0:0:0:0
End Range: 2a03:c7c0:ffff:ffff:ffff:ffff:ffff:ffff

Range to provide to my customer 2a03:c7c0::/112, this is:

Start Range: 2a03:c7c0:0:0:0:0:0:0
End Range: 2a03:c7c0:0:0:0:0:0:ffff

Obviously there are not a problem if some customer wants some biggest pool, to provide his the possibility to manage his own IPv6 networks, like a /108 that provides 16 x /112 networks, example of a /108 network

Start Range: 2a03:c7c0:0:0:0:0:0:0
End Range: 2a03:c7c0:0:0:0:0:f:ffff

The IPv6 tool provided in the ADMIN SolusVM can not provide any option to create networks. Is the END-USER tool, by adding unique IPs in ranges of 100 units.

It's very very hard manage a correct subneting with your tool.

I appreciate if you move the current admin tool "to add IPs 100 by 100" to the client area, and provide in the admin area the prossibility to provide IPv6 networks directly to a customer, not to a VPS.
Also consider to dont add unique IPs and force to use allways a CIDR notation to prevent SQL overloads in the SolusVM service when I manage billions of unique IPv6.

Is the customer the decision to route a unique IP of his block to some VPS or other one.
If a customer wants move 7624 unique IPs I can not do this work, because I need contract a person to do only IP movements during a day.

It's crazy to provide unique IPv6 to a customer. I will provide a minium /112 network (65536 of unique IPv6) to each customer.

Thanks.
Hacer clic para expandir...

Y la respuesta fue esta:

Hi,

I totally understand what you are saying and it is something we are putting in place shortly. This has been planned for a while now and will be available shortly. thanks for your explanation all the same.

--
Kind Regards,

Phill Bandelow

Management
SolusLabs Support
Hacer clic para expandir...

Por lo que parece que está en curso de implementación....

Qué opináis sobre el hecho de dar un /112 completo ?

He creado este fichero para comprender la notación Hexadecimal de un /112 completo: ginernet.com/dec-hex.php

Creo que es una unidad que proporciona bastante simplicidad a la hora de gestionar un correcto subneting, especialmente en el lado del administrador de la red...

Salu2!!

Anunciante

ideasmultiples · 18 Ene 2013

No entiendo en absoluto la necesidad de asignarle esa cantidad de IP's a un cliente cuando nunca los va a usar.

Parece que como hay muchos hay que repartirlos rápido...

Datacenter1 · 18 Ene 2013

Yo sugeriría esta forma

Tienes un /32
Lo divides en /48 para tus clientes (hay 65,536 disponibles en tu /32)
Tus clientes pueden subnetear a /64 por dispositivo físico (tendrán 64.536 disponibles)

No asignar menos de /64 por servidor

jmginer · 20 Dic 2013

Datacenter1 dijo: ↑

Yo sugeriría esta forma

Tienes un /32
Lo divides en /48 para tus clientes (hay 65,536 disponibles en tu /32)
Tus clientes pueden subnetear a /64 por dispositivo físico (tendrán 64.536 disponibles)

No asignar menos de /64 por servidor
Hacer clic para expandir...

El tema se mueve, sigo detrás de esto y por fín parece que vemos una luz al final del camino,
efectivamente, la idea es proponer un /64 para cada cliente.
Más info aquí: http://lowendtalk.com/discussion/18582/improve-ipv6-notation-in-solusvm-for-providers

Phill Bandelow - SolusLabs Support dijo:

Hi,

We already have this in the works. How we will do it is this:

You add a block of IPv6 to SolusVM (i.e a /48). You then specify what nodes you can use that block on. When adding IPv6 to a virtual server you have the option to specify a block size and what block you want it from. So you can select maybe a /122 (64 ip's) from the /48 block. SolusVM will then work out the range of IP's and reserve them for that virtual server.

The variable idea is a good idea in fact and we may beable to add that in as an option.

All our plans will become public knowledge straight after Christmas where we plan to maintain a decent roadmap! You should see major progress as we have a nice new office with 4 full time developers local to myself.

Feel free to post any information back from this ticket on the forum.

--
Kind Regards,
Phill Bandelow - SolusLabs Support
Hacer clic para expandir...

Accede o regístrate

Implementando IPv6

jmginer Usuario activo

Anunciante

ideasmultiples Usuario activo

Datacenter1 Usuario activo

jmginer Usuario activo

Accede o regístrate

Implementando IPv6

jmginer Usuario activo

Anunciante

ideasmultiples Usuario activo

Datacenter1 Usuario activo

jmginer Usuario activo

Búsquedas útiles