IPv6

The last ipv4 addresses have been handed out to providers. They still won't be provisioned for another few months.

I don't think ipv6 is a tomorrow or 'I'm bailing' issue, but it's definitely a mid-term issue that does need to be functioning sooner rather than later.
 
I don't know of that many ISP that offer IPv6. The major sites are barely offering a service on it.
It's important and it has to happen this year, but it's not that urgent. You can enable it for all services already and make sure you're ready.
 
I don't know of that many ISP that offer IPv6. The major sites are barely offering a service on it.
It's important and it has to happen this year, but it's not that urgent. You can enable it for all services already and make sure you're ready.
It would be nice if it could be ready by June 8th :). All the big players "will offer their content over IPv6 for a 24-hour 'test flight'".
World IPv6 Day
 
Hello,

I've written this guide, which should help clarify things:
http://help.directadmin.com/item.php?id=353

Also, for 1.37.1, DA now listens to both IPv4 and IPv6 on port 2222 (finally)
http://www.directadmin.com/features.php?id=1168

This feature is already in the pre-release section if anyone wants to try it out the new binaries (feedback would good, since it's a total rewrite of the bindings in the sockets class).

Next step is to tackle the licensing system to support IPv6 so that DA boxes are not required to have at least 1 IPv4 IP on them.

;)

John
 
MySQL Access hosts

Hi,

We're testing the whole IPv6 thing and it looks good. At the moment our servers have IPv4 and IPv6 addresses.

But I cannot add a IPv6 address in the MySQL Access Host field (not a valid host). Is this a DirectAdmin thing, or does MySQL lack the support for IPv6?

Thanks,
Michael
 
In the new documentation, it says:
ProFTPd: Apache support IPv6 out of the box. No need for changes.
Apart from the copy and paste error, I don't think it's right unless --enable-ipv6 is now a default flag for proftpd.

Also, I'm confused about that statement about FreeBSD:
What this means is that any service which is using IPv6 to handle both v4 and v6 will only be using v6.

We don't need to enable that flag on FreeBSD 8.x for services to use both IP systems. Is this for Directadmin only?
 
Last edited:
Hello,

Looking over the code, yes it is, however you're going to want to use the expanded form of IPv6 IPs, as I'm not sure it's currently smart enough to figure out a short-form range.

Eg, use this:
Code:
1:2:3:4:5:6:7:8-9
John
 
This makes me very happy to see v6 coming into focus.. time to start inquiring about a v6 range from my provider.

edit: those docs are very helpful. thanks! i'm going to get to work on some v6 soon as my provider forks over a range.
 
Last edited:
I read an article recently... the author made a good argument for the fact that in the short term (years?) it will be most likely that providers (that's us) will be likely using IPv4, while users (especially in newly emerging countries and those using wireless connections) will be likely using IPv6.

Has anyone come up with a reasonable way of doing that? Or are you relying on your upstream for NAT?

Jeff
 
We have integrated IPv6 to our servers and provided it to users.
I went quite smoothly with exception of DA listening to v6.

I would only have one request.
Currently we assign IPv6 address via multiple IP. I would be nice if we could set server IPv4 IP and IPv6 IP that would be automatically assigned to all users.
 
I just need to get Ubersmith to support it properly now and I'm going live with V6..
 
Back
Top