Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Information / What lacks for CWP to have complete IPv6 Support
« on: January 30, 2021, 09:32:51 PM »
IPv6 is a reality in many places now a days and CWP as a hosting platform cannot skip it.
As known IPv4 is over and it affects a lot the Hosting industry, so as sooner get customers to be using IPv6 sooner will be less dependent on IPv4. Also there has been a lot of improvement on several countries in the IPv6 deployment for broadband. Some are already over 50% and other over 60%. There are very popular content services like Google (Youtube and Gmail main), Facebook, Netflix, Cloudflare, etc that serve their content 100% in IPv6 already.
Having IPv6 support isn't just a minor optional thing since IPv6 is the actual Internet Protocol and IPv4 and is already considered legacy.
I have reported this to CWP Developers via their BUG Tracker tool last year and never ever got any reply back. The task has not even been assigned to someone to work on.
The main points to get IPv6 to CWP I could gather are:
- An extra menu option that allow you to add all IPv4 and IPv6 addresses that will be used by the several services running inside CWP. CWP Settings, Edit Settings would be this place but it has place for only one address at the moment. Perhaps an additional menu for adding as many IPv4 and IPv6 address as necessary would keep things more organized and in Edit Settings only the Shared/Main IPv4 and IPv6 addresses.
- Automatic generation of all vHosts (Apache/NGINX/Varsnish) for all domains by default with IPv4 and IPv6 configured in the server (or optionally the IPv4 and IPv6 configured specifically for that client). Inside the WebServer Settings, WebServers Domain conf menu.
- Fix the BIND configuration which currently listen on ::1 instead of "any" for IPv6 in order that hosted domains can work properly.
- Fix the DNS Record editor which currently doesn't allow to add AAAA records.
- Make sure a AAAA record is automatically generated for every domain/website hosted where IPv6 is present and configured for that domain.
- Make sure the Mail services also listen on IPv6
- Make sure there is a MX record pointing to an A/AAAA hostname plus de equivalent TXT/SPF record for that domain and rDNS records (if hosted locally)
- Make sure that other services like NGINX, Varnish, SSH, etc also listen on the default IPv6 address by default, at least, or the domain configured address.
Additionally to these above which are basic add also support to CSF and Firewall Manager to be able to manager and view all ip6tables rules
- Make sure that statistics services like Awstats also take in consideration accesses made via IPv6 recorded by the logs.
CoriaWeb Hosting has made some improvements in this topic and posted in the forum. Perhaps they can be useful to help with this necessary improvement - http://forum.centos-webpanel.com/index.php?topic=8000.0
As known IPv4 is over and it affects a lot the Hosting industry, so as sooner get customers to be using IPv6 sooner will be less dependent on IPv4. Also there has been a lot of improvement on several countries in the IPv6 deployment for broadband. Some are already over 50% and other over 60%. There are very popular content services like Google (Youtube and Gmail main), Facebook, Netflix, Cloudflare, etc that serve their content 100% in IPv6 already.
Having IPv6 support isn't just a minor optional thing since IPv6 is the actual Internet Protocol and IPv4 and is already considered legacy.
I have reported this to CWP Developers via their BUG Tracker tool last year and never ever got any reply back. The task has not even been assigned to someone to work on.
The main points to get IPv6 to CWP I could gather are:
- An extra menu option that allow you to add all IPv4 and IPv6 addresses that will be used by the several services running inside CWP. CWP Settings, Edit Settings would be this place but it has place for only one address at the moment. Perhaps an additional menu for adding as many IPv4 and IPv6 address as necessary would keep things more organized and in Edit Settings only the Shared/Main IPv4 and IPv6 addresses.
- Automatic generation of all vHosts (Apache/NGINX/Varsnish) for all domains by default with IPv4 and IPv6 configured in the server (or optionally the IPv4 and IPv6 configured specifically for that client). Inside the WebServer Settings, WebServers Domain conf menu.
- Fix the BIND configuration which currently listen on ::1 instead of "any" for IPv6 in order that hosted domains can work properly.
- Fix the DNS Record editor which currently doesn't allow to add AAAA records.
- Make sure a AAAA record is automatically generated for every domain/website hosted where IPv6 is present and configured for that domain.
- Make sure the Mail services also listen on IPv6
- Make sure there is a MX record pointing to an A/AAAA hostname plus de equivalent TXT/SPF record for that domain and rDNS records (if hosted locally)
- Make sure that other services like NGINX, Varnish, SSH, etc also listen on the default IPv6 address by default, at least, or the domain configured address.
Additionally to these above which are basic add also support to CSF and Firewall Manager to be able to manager and view all ip6tables rules
- Make sure that statistics services like Awstats also take in consideration accesses made via IPv6 recorded by the logs.
CoriaWeb Hosting has made some improvements in this topic and posted in the forum. Perhaps they can be useful to help with this necessary improvement - http://forum.centos-webpanel.com/index.php?topic=8000.0
2
Information / Re: Will we see IPv6 in until 2021?
« on: January 21, 2021, 05:42:07 AM »
Sandeep, why not CWP Developers stop being careless about IPv6 for so long and implement it definitely instead of giving excuses like this to adjust the template.
It is unthinkable that already 2021 there is still NO full IPv6 support for CWP and developers are not barely concerned about it treating it like: "Just edit template manually. We will add when we fell like."
The chap is paying CWP Pro in order to support it. I have paid in the past expecting for it to have IPv6 soon and it seems that probably the developers don't have a vaugue idea of what Ipv6 means in this context always leaving it for later.
Some people from the community already developed something to get this working within CWP and but developers didn't take that work into consideration to use something that has already been done.
What a shame this has been treated like this until now ! Seems we will not see full IPv6 in CWP in 2021 as well.
It is unthinkable that already 2021 there is still NO full IPv6 support for CWP and developers are not barely concerned about it treating it like: "Just edit template manually. We will add when we fell like."
The chap is paying CWP Pro in order to support it. I have paid in the past expecting for it to have IPv6 soon and it seems that probably the developers don't have a vaugue idea of what Ipv6 means in this context always leaving it for later.
Some people from the community already developed something to get this working within CWP and but developers didn't take that work into consideration to use something that has already been done.
What a shame this has been treated like this until now ! Seems we will not see full IPv6 in CWP in 2021 as well.
3
Information / Re: Did CWP support IPV6?
« on: April 10, 2020, 05:29:30 PM »
It doesn't really matter what an specific broadband provider is lacking really.
The reality is that in several countries IPv6 deployment is between 30 to 60% and that IPv4 is already considered legacy.
An old product that doesn't receive updates anymore is understandable not having it but a product that is developed and in already 2020 cannot miss it. The issue about IPv4 exhaustion comes from back in 2011 and a most of the content providers have it 100% ready, including the major ones like Google, Facebook, Netflix, Akamai, Cloudflare - all 100%
The reality is that in several countries IPv6 deployment is between 30 to 60% and that IPv4 is already considered legacy.
An old product that doesn't receive updates anymore is understandable not having it but a product that is developed and in already 2020 cannot miss it. The issue about IPv4 exhaustion comes from back in 2011 and a most of the content providers have it 100% ready, including the major ones like Google, Facebook, Netflix, Akamai, Cloudflare - all 100%
4
Information / Re: Did CWP support IPV6?
« on: April 10, 2020, 03:24:38 PM »
I think you didn't get the critically of this missing. We are not talking about a nice custom thing that would be nice to have like a kind of specially back mode for example.
IPv6 is not something "nice to have when possible" or "optional", but mandatory. A product that lacks it is legacy as it is IPv4.
In 2020 not having it ready and working by default is something that easily puts any product out.
There is the IPv4 exhaustion problem since 2011 which has been increasing and companies are required to use IPv6 everywhere, but CWP in 2020 still didn't take as something important to get everything ready to treat IPv6 as it does with IPv4.
If it hasn't been done yet it is something that should be taken as the highest priority over anything else.
IPv6 is not something "nice to have when possible" or "optional", but mandatory. A product that lacks it is legacy as it is IPv4.
In 2020 not having it ready and working by default is something that easily puts any product out.
There is the IPv4 exhaustion problem since 2011 which has been increasing and companies are required to use IPv6 everywhere, but CWP in 2020 still didn't take as something important to get everything ready to treat IPv6 as it does with IPv4.
If it hasn't been done yet it is something that should be taken as the highest priority over anything else.
5
Information / Re: Did CWP support IPV6?
« on: April 10, 2020, 05:08:29 AM »
Unfortunately it doesn't seem to be that case.
It is worth ask: how is it possible that in 2020 there is still no IPv6 support ?
IPv6 is not a "minor, nice to have thing" to be left to "when there is some time".
Often people complain that there are many contents that don't have IPv6 support but then products that should have it ready don't as well.
It is worth ask: how is it possible that in 2020 there is still no IPv6 support ?
IPv6 is not a "minor, nice to have thing" to be left to "when there is some time".
Often people complain that there are many contents that don't have IPv6 support but then products that should have it ready don't as well.
6
CentOS Configuration / Re: IPv6 support
« on: April 10, 2020, 05:03:20 AM »
How is it possible that in 2020 there is still no IPv6 support ?
IPv6 is not a "minor, nice to have thing" to be left to "when there is some time".
Often people complain that there are many contents that don't have IPv6 support but then products that should have it ready don't as well.
This type of thing should be priority of any other module or feature and even bugs to be fixed. IPv6 is not an optional thing really.
IPv6 is not a "minor, nice to have thing" to be left to "when there is some time".
Often people complain that there are many contents that don't have IPv6 support but then products that should have it ready don't as well.
This type of thing should be priority of any other module or feature and even bugs to be fixed. IPv6 is not an optional thing really.
Pages: [1]
