IPv6

[Mathijs]

So we have to type every ipv6 address by hand?
That's quite a shame.

[RatS]

suggestions how to optimize?

[Mathijs]

on page one i suggested:

Quote:Well those are the 2 that should be done indeed, but it is not that simple as adding one ip of course.
I would say, let's give a /80 to a server, and each virtualhost its own /128. Each https can also have it's own ip, no problem there anymore.
So it would be setting a /80 in the setup screen, set own ip's to domains, set AAAA records in DNS. And all that while keeping it compatible with ipv4 in the mean time.

So when you would add a domain, it should get an ipv6 address automatically.
Now we are working with multiple vhosts on one or more ip's because we have a shortage, on ipv6 every domain can get its own ip or even multiple ip's. So i think automating that would be the way to go instead of having to assign every ipv6 address by hand.
Because of ipv6, things will change quite a lot, so implementing ipv6 like ipv4 is working at this moment, doesn't seem the right way to me.
Does this sound reasonable, or is it me being lazy?

[rbtux]

nope your not crazy

its a common misunderstanding of network / systemengineers that ipv6 is the same as ipv4, but somewhat more addresses...

that being said I don't know how a sane ipv6 implementation looks like

atm. we include the number of the virtual user an a site-id in the ip address... all servers in a /64 net...

our servers are all identified by an integer number (CI - ITIL ;-))

so this number goes in the address to... the complete address looks like

2a00:baba:dead:beef:0:4590:7025:3

where dead:beef is the server subnet 00004590 is the CI number of the server 7025 ist the id of the virtualuser and 0003 is the third page of the user on this server...

[Mathijs]

Quote:that being said I don't know how a sane ipv6 implementation looks like

So it seems we need to discuss how to implement it in a sane way, that is exactly the reason why i brought that up on the first page of this thread.

So please everyone, think about this and post your opinion here, so it can be implemented in a way that suits everyone best.

Of course, it doesn't have to be like i proposed it to be in the end, but that is how others told me they did implement it in their environments. Also, to me it seems the right way to do it.

[joximu]

(02-22-2010 08:00 AM)rbtux Wrote:  nope your not crazy

its a common misunderstanding of network / systemengineers that ipv6 is the same as ipv4, but somewhat more addresses...

that being said I don't know how a sane ipv6 implementation looks like

atm. we include the number of the virtual user an a site-id in the ip address... all servers in a /64 net...

our servers are all identified by an integer number (CI - ITIL ;-))

so this number goes in the address to... the complete address looks like

2a00:baba:dead:beef:0:4590:7025:3

where dead:beef is the server subnet 00004590 is the CI number of the server 7025 ist the id of the virtualuser and 0003 is the third page of the user on this server...

so it's not allowed to have more than 65536 pages on a site?
or you mean page not in the meaning of web-page but rather domain/sub-domain/2nd domain/alias etc...

well this should be enough...

/J

[rbtux]

thats 16-bit per virtual user, that should be enough...

But as I said... Thats just what we think is a good idea :-))

---

To be more specific

our concept allows

32-bit (4 billion) Servers per Subnet (well that wont scale, i know ;-))
16-bit (65k) Users per Server
16-bit (65k) Different Websites/Domains/etc per User

[FredNeuberger]

Why don't you keep it as much flexible as possible?
I guess not every service provider will give you a /64.
On my virtual machine I've only six IPv6 addresses.

[FredNeuberger]

Hey there

Is there any progress recently?

[petzsch]

IPv6 is coming slowly but surely

Hetzner.de (huge german ISP) includes a /64 IPv6 subnet with every dedicated server now. Details

vsell.de includes one free IPv6 IP adress with their virtual servers along with the included IPv4 address.

From the implementation in ISPcp I think we should leave as much freedom to the user as possible. In the transition time we surely need virtual hosts on an IPv4 and IPv6 adress.

If many (>200 addresses?) IPv6 adresses are avaible ISPcp should be able to assign one address per domain/alias (subdomain maybe not so we can still use a wildcard entry on external dns servers).

I'll give IPv6 a try for setting up nameservers to listen to ipv4 and ipv6 (PowerDNS with ISPdns managment interface)