Solved Include IPv6 into Cloudron
-
It's almost 2021 and time for Cloudron to step-up to IPv6
see:
https://forum.cloudron.io/topic/3783/firewall-ip-blocking-ipv6-not-possible
https://forum.cloudron.io/topic/2161/is-cloudron-ready-for-ipv6-or-not -
+1 for IPv6. Had a situation come up recently where IPv6 would have (apparently) resolved it when it came to email block lists. Of course the easier workaround for me is to use a mail relay instead of the built-in SMTP server, but IPv6 was a second alternative presented by OVH who is responsible for the IP range mine was included in.
-
Wasn't this supposed to be available on 2020? Even cloudron.io is not accessible from IPv6-only hosts. Tried with NAT64 also and no results. We need IPv6 asap.
-
Agree would be good to add, currently you can already just setup the DNS records with AAAA to point to the Cloudron and that should work fine. I think the automation of that is just what is lacking, next to maybe some mail DNS record related things, but not 100% sure.
Given that ipv4 is supported everywhere and at least I am not aware of a VPS provider who does not give ipv4 addresses, we have handled that as low priority so far.I am curious in which circumstances you have ipv6 only clients? Maybe we are missing a crucial use-case.
-
I don't have any ipv6 only clients, but I really would like to support the sites on my cloudron being accessed over ipv6 seamlessly.
-
@nebulon I’ve setup AAAA records manually for all domains, however AAAA for the mailserver doesn’t work. Check your domain and email at https://en.internet.nl and try to get 100%.
For all domains I get a 100% now because you guys did some tweaking in the latest version. However email is still stuck at 84% because of IPv6 and DANE.
It’s now closer to 2022 and really time to implement IPv6 also in blocklists and firewall.
-
I've run into this recently as well. While setting the records manually would work, automating this (particularly with Cloudflare) would be wonderful.
-
IPv4 is now double the price as 2020, from 20/25 for 1 IP now is 45/50 for 1 IP.
This is really hard to sustain for those who have their own platform, IPv6 will be really appreciated.Matteo. R.
Founder and Tech-Support Manager.
MooCloud MSP
Swiss Managed Service Provider -
I guess we can move gradually to support both better in parallel first, for example we could setup AAAA records automatically if a non manual DNS backend is configured. Also not sure what is required for other things like the mail server to bind to that interface as well. Not sure how things like PTR for mail delivery deal with this and if there is an IPv6 equivalent.
IPv6 only Cloudrons are likely a bit harder to get done, but maybe in the future.
-
A gradual approach is the best, and yes PTR is available for IPv6.
Cloudron can also take advantage of IPv6 "Subnet", and having a dedicated IPv6 for every container. -
Google IPv6 Implementors Conference: State of the IPv6 Internet & Transition Mechanisms and Tools
Youtube Video -
-
@nebulon Since ipv4 addresses are getting more expensive it might be worthwhile to start considering and planning for ipv6.
-
For everyone like myself who still needs to freshen up on IPv6 here a free course by ripe.net
-
Fair enough, I will add this to 7.1 roadmap
I can't promise this gets done though, since we have to investigate what needs to be done. It also depends on services like Lets Encrypt supporting IPv6 nicely (which I think they do by now). -
For those using Hetzner, it seems that they have released IPv6-only versions for some of their dedicated servers. These IPv6-only servers are cheaper since the price of the IPv4 address is deducted from the original price.
More info can be found here https://docs.hetzner.com/robot/dedicated-server/ip/faq-primary-ipv4/.
They are apparently working on IPv6-only cloud servers as well, so it's something to look forward to if Cloudron can support IPv6.
-
@thpuffin yup, working on ipv6 support for 7.1!
