Panel: IPv6 Support

[adrijanb]

Since the protocol for IPv4 addresses has now reached its limits and the last IPv4 addresses have been distributed, I wanted to ask whether it would be possible to program a future-proof version of Pterodactyl. I am aware that this will be a lot of work, but support for IPv6 should be encouraged, especially in the areas of hosting.

I would be very happy if the support for IPv6 is also added in Pterodactyl!

[TekExplorer]

yes, this is the one thing preventing me from installing it thus far, there are no more IPv4 addresses, but its cheap as all heck (ie. free) to get lots of IPv6 - please tell me this is already implemented or will be soon. i would be incredibly excited to see this implemented

[Wqrld]

I believe docker requires some flags for ipv6 still, but ill try to do some testing to see what's needed

[Wqrld]

see https://docs.docker.com/config/daemon/ipv6/, im going to have a hard time testing though as i don't have ipv6 myself

Edit it would be cool if we could dual-band in some way with one ipv6 address and one ipv4 port for one server but i would have no idea how to do that.

[adrijanb]

It would be awesome, if you could test it.

[Wqrld]

I just got a new laptop that does have ipv6 support (not sure why my pc didnt) so i hope i can get to this soon.

[parkervcp]

You primary issue is that ipv6 still doesn't have wide adoption and 4to6 and 6to4 conversions are still non-standard.

[Wqrld]

You primary issue is that ipv6 still doesn't have wide adoption and 4to6 and 6to4 conversions are still non-standard.

the idea was mainly that you could have minecraft listen on ipv6 AND ipv4 (which is possible through a linux setting which may or mayb not exist in those containers). To also let ipv6 users connect to your server and use v6 where possible

[adrijanb]

@parkervcp is right. There are no standards yet but i think there are going to be some soon.

[LinusTebbe]

Are there any plans to implement this in the foreseeable future?
I just stumbled upon this issue and it's kind of a major problem, as IPv6 connections are actually quicker, at least in Germany, because most IPv4 Adresses are only given via a NAT.
Basically every connection gets atleast a /64 IPv6 subnet.

[matthewpi]

I believe the plan is to get IPv6 support in 1.0, I don't believe we are accepting features/minor fixes to 0.7 (that would include the 0.6 daemon). As https://github.com/pterodactyl/daemon/pull/111 was submitted, CodeCo asked about if the same problem exists in wings (the 1.0 daemon) and I believe it does. While I'm not sure about all the minor implementation details of IPv6, we should try to make 1.0 support it as well as we can without making everything complicated.

[unixfox]

IPv6 support in Docker is kinda wobbly and due to that I use https://github.com/robbertkl/docker-ipv6nat which allows to bind the server to a fixed IPv6 address instead of having a dynamic IPv6 address allocated each time the container gets created.

Maybe that would help for implementing IPv6 support in pterodactyl.

[LinusTebbe]

I got it to work by:

Applying the changes in https://github.com/pterodactyl/daemon/pull/111

Enabling IPv6 support in Docker, disabling the userland proxy by creating the file /etc/docker/daemon.json with the content:

{
  "userland-proxy": false,
  "ipv6": true,
  "fixed-cidr-v6": "fd00::/80"
}

Installing the previously mentioned container: https://github.com/robbertkl/docker-ipv6nat
and rebooting afterwards

Maybe this will help some people having the same problem.

[LinusTebbe]

Is there any update to this?
Now that the 1.0 is out for some time...