Author Topic: Offical ipv6 Support?  (Read 3014 times)

0 Members and 1 Guest are viewing this topic.

Offline
***
Re: Offical ipv6 Support?
« Reply #15 on: July 27, 2023, 12:20:10 AM »
If you are still using DSL, I feel sorry for that company.

We use AT&T Fiber, and by default AT&T gives IPv4 & IPv6.
I also know Spectrum & Xfinity (Comcast) cable modems do as well.

Most VPS providers offer IPv6 now a days, even Vultr has a IPv6 Only VPS.

An A RECORD search for both amazon and facebook show only IP4.   What say ye now?
Listen to everything Pixelpadre says.

Offline
****
Re: Offical ipv6 Support?
« Reply #16 on: July 27, 2023, 02:46:12 AM »
If you are still using DSL, I feel sorry for that company.

We use AT&T Fiber, and by default AT&T gives IPv4 & IPv6.
I also know Spectrum & Xfinity (Comcast) cable modems do as well.

Most VPS providers offer IPv6 now a days, even Vultr has a IPv6 Only VPS.

I live in rural Florida, we are lucky that they have an interest in giving us DSL.  I get dual bonded speed of 79 down and 10 up.  More than that I don't need.  But when they get around to it, we will eventually get fiber from them.  And it will be synchronous 200/200.  When that happens I could run my server from home, and most likely will.

I call BS on vultr only using IPv6.   That would kill their business as most webservers are running LAMP.  And setting LAMP up for IPv6 with a GUI just isnt ready for prime time.

A quick google challenge reveals:
Do you need both IPv4 and IPv6?

When possible, it is better to keep both IPv4 and IPv6 addresses enabled. For example, using only IPv6 can cause some accessibility issues, as only about one third of the internet supports IPv6 addresses.

Be careful, who you call BS on when clearly you don't know the Facts...
Re-read what I posted, and below is the link & screen capture to backup my statement.

https://www.vultr.com/pricing/#cloud-compute/


When you've been doing Tech & IT work for 34 years, let me know...
But when you mentioned GUI, tells me you probably are a newbie. Which is fine, we all started somewhere.
« Last Edit: July 27, 2023, 03:00:39 AM by Starburst »

Offline
****
Re: Offical ipv6 Support?
« Reply #17 on: July 27, 2023, 02:55:06 AM »
If you are still using DSL, I feel sorry for that company.

We use AT&T Fiber, and by default AT&T gives IPv4 & IPv6.
I also know Spectrum & Xfinity (Comcast) cable modems do as well.

Most VPS providers offer IPv6 now a days, even Vultr has a IPv6 Only VPS.

An A RECORD search for both amazon and facebook show only IP4.   What say ye now?

1. IPv6 is NOT a 'A RECORD'.
Might want to Google DNS Record Types or watch some YouTube videos on Networking.

2. I looked up Amazon, and True they do not have an AAAA Record Entry.
Which is interesting.

3. Looked up Facebook, and they DO have an AAAA Record Entry:

Offline
****
Re: Offical ipv6 Support?
« Reply #18 on: July 27, 2023, 01:59:53 PM »
A ≠ AAAA
(4 | 6)

Offline
****
Re: Offical ipv6 Support?
« Reply #19 on: July 27, 2023, 04:12:43 PM »
To AAAA, or not to AAAA...
That is the question...

Hahaha

Offline
***
Re: Offical ipv6 Support?
« Reply #20 on: July 27, 2023, 08:16:08 PM »
If you are still using DSL, I feel sorry for that company.

We use AT&T Fiber, and by default AT&T gives IPv4 & IPv6.
I also know Spectrum & Xfinity (Comcast) cable modems do as well.

Most VPS providers offer IPv6 now a days, even Vultr has a IPv6 Only VPS.

I live in rural Florida, we are lucky that they have an interest in giving us DSL.  I get dual bonded speed of 79 down and 10 up.  More than that I don't need.  But when they get around to it, we will eventually get fiber from them.  And it will be synchronous 200/200.  When that happens I could run my server from home, and most likely will.

I call BS on vultr only using IPv6.   That would kill their business as most webservers are running LAMP.  And setting LAMP up for IPv6 with a GUI just isnt ready for prime time.

A quick google challenge reveals:
Do you need both IPv4 and IPv6?

When possible, it is better to keep both IPv4 and IPv6 addresses enabled. For example, using only IPv6 can cause some accessibility issues, as only about one third of the internet supports IPv6 addresses.

Be careful, who you call BS on when clearly you don't know the Facts...
Re-read what I posted, and below is the link & screen capture to backup my statement.

https://www.vultr.com/pricing/#cloud-compute/


When you've been doing Tech & IT work for 34 years, let me know...
But when you mentioned GUI, tells me you probably are a newbie. Which is fine, we all started somewhere.

Newbie since 1996 when I purchased 200+ TLDs during the Network Solutions Land Grab.
Listen to everything Pixelpadre says.

Offline
***
Re: Offical ipv6 Support?
« Reply #21 on: July 27, 2023, 08:21:52 PM »
And a simple g search will reveal that your definition of "widespread ipv6 use" amounts to somewhere between 21 and 30%.  That would sure be widespread if it was the black plague, but for webservers.......not even close..  I think Microsoft webservers are at the same percentages.  Does that mean it's widespread?  I don't think so....but the folks in Seattle might.
Listen to everything Pixelpadre says.

Offline
****
Re: Offical ipv6 Support?
« Reply #22 on: July 27, 2023, 08:30:30 PM »
And a simple g search will reveal that your definition of "widespread ipv6 use" amounts to somewhere between 21 and 30%.  That would sure be widespread if it was the black plague, but for webservers.......not even close..  I think Microsoft webservers are at the same percentages.  Does that mean it's widespread?  I don't think so....but the folks in Seattle might.

Give it up newbie.

All your arguments keep being disproven.

https://www.networkworld.com/article/3254575/what-is-ipv6-and-why-aren-t-we-there-yet.html#:~:text=Who%20is%20deploying%20IPv6%3F,mobile%20networks%20leading%20the%20charge.

"As of March 2022, according to Google, the IPv6 adoption rate globally is around 34%, but in the U.S. itís at about 46%.

Carrier networks and ISPs have been the first group to start deploying IPv6 on their networks, with mobile networks leading the charge.
For example, T-Mobile USA has more than 90% of its traffic going over IPv6 as of March 2002, with Verizon Wireless close behind at 82.63%. Comcast and AT&T have their networks at 70% and 73%, respectively"

I would call 70%-90% a 'widespread' use of IPv6.

Offline
****

Offline
****
Re: Offical ipv6 Support?
« Reply #24 on: July 27, 2023, 08:36:59 PM »
If you are still using DSL, I feel sorry for that company.

We use AT&T Fiber, and by default AT&T gives IPv4 & IPv6.
I also know Spectrum & Xfinity (Comcast) cable modems do as well.

Most VPS providers offer IPv6 now a days, even Vultr has a IPv6 Only VPS.

I live in rural Florida, we are lucky that they have an interest in giving us DSL.  I get dual bonded speed of 79 down and 10 up.  More than that I don't need.  But when they get around to it, we will eventually get fiber from them.  And it will be synchronous 200/200.  When that happens I could run my server from home, and most likely will.

I call BS on vultr only using IPv6.   That would kill their business as most webservers are running LAMP.  And setting LAMP up for IPv6 with a GUI just isnt ready for prime time.

A quick google challenge reveals:
Do you need both IPv4 and IPv6?

When possible, it is better to keep both IPv4 and IPv6 addresses enabled. For example, using only IPv6 can cause some accessibility issues, as only about one third of the internet supports IPv6 addresses.

Be careful, who you call BS on when clearly you don't know the Facts...
Re-read what I posted, and below is the link & screen capture to backup my statement.

https://www.vultr.com/pricing/#cloud-compute/


When you've been doing Tech & IT work for 34 years, let me know...
But when you mentioned GUI, tells me you probably are a newbie. Which is fine, we all started somewhere.

Newbie since 1996 when I purchased 200+ TLDs during the Network Solutions Land Grab.

Ah, so your a self admitted domain squatter...

That doesn't make you a Sys Admin.

Offline
***
Re: Offical ipv6 Support?
« Reply #25 on: July 27, 2023, 09:47:12 PM »
No not a system administrator.   But I have been maintaining all of those websites every since trying to keep them at critical mass.  Been thru hundreds of hosts over the years and experienced every possible issue imaginable and having to find solutions with a company of one employee.  It's been a very long 27 years.  I can write an encyclopedia with the knowledge I have about the internets evolution and the companies that haven risen only to crash and burn in a spectacular display of chaos and confusion.

Bill Gates wasnt/isnt a network administrator either.  Lots of people going around calling themselves network administrators these days.  Some even have certifications and still no clue what they are doing.

People like me have an small amount of information about everything, while others have a tremendous amount of information about just one thing.  To each his own.  I dont need to reinvent the wheel, I just need to drive the wagon.
Listen to everything Pixelpadre says.

Offline
***
Re: Offical ipv6 Support?
« Reply #26 on: July 27, 2023, 09:56:10 PM »
And a simple g search will reveal that your definition of "widespread ipv6 use" amounts to somewhere between 21 and 30%.  That would sure be widespread if it was the black plague, but for webservers.......not even close..  I think Microsoft webservers are at the same percentages.  Does that mean it's widespread?  I don't think so....but the folks in Seattle might.

Give it up newbie.

All your arguments keep being disproven.

https://www.networkworld.com/article/3254575/what-is-ipv6-and-why-aren-t-we-there-yet.html#:~:text=Who%20is%20deploying%20IPv6%3F,mobile%20networks%20leading%20the%20charge.

"As of March 2022, according to Google, the IPv6 adoption rate globally is around 34%, but in the U.S. itís at about 46%.

Carrier networks and ISPs have been the first group to start deploying IPv6 on their networks, with mobile networks leading the charge.
For example, T-Mobile USA has more than 90% of its traffic going over IPv6 as of March 2002, with Verizon Wireless close behind at 82.63%. Comcast and AT&T have their networks at 70% and 73%, respectively"

I would call 70%-90% a 'widespread' use of IPv6.
And yet their modems come with default ip4 enabled and ipv6 disabled.  Why are they still using ip4 if ipv6 is widespread.  The answer is quite simple. 

Quote
However, the transition to IPv6-only operation brings specific challenges, one of which is that some DNS zones are only served by IPv4-only authoritative servers. This can cause problems for IPv6-only iterative resolvers as they do not have access to an IPv4 network and may be unable to resolve these DNS zones.Feb 9, 2023
Listen to everything Pixelpadre says.

Offline
****
Re: Offical ipv6 Support?
« Reply #27 on: July 27, 2023, 10:34:15 PM »
Can't help if your small network DNS servers are setup for IPv4 only.
That's your choice.

--

The ICANN Root servers have supported IPv6 since 2008-02-04

https://www.icann.org/en/announcements/details/ipv6-address-added-for-root-servers-in-the-root-zone--addition-enhances-end-to-end-connectivity-for-ipv6-networks-4-2-2008-en

https://www.iana.org/reports/2008/root-aaaa-announcement.html

--

FYI The Major broadband providers like AT&T, T-Mobile, Verizon, Xfinity (Comcast), Windstream, Spectrum/Charter, plus many others have their modem/routers ALL come with IPv4 AND IPv6 Enabled.

You have railroaded this thread for some personal reason away to what it was originally for.

Asking when CWP would be Officially supporting IPv6.

Offline
*
Re: Offical ipv6 Support?
« Reply #28 on: August 18, 2023, 08:39:02 PM »
you can make your own custom template, but we're working on full ip manager and ip assigning feature which are very complicated with ipv6

Yes, I did that too, but as soon as you update CWP, then all the settings are gone.... This frustrates me right now I have made so much effort to customize all the templates from vhosts now they are all botched.

I do the whole thing via vhost templates without customizing individual domains, but now I have the problem that for some reason I can not understand, the php-fpm no longer wants to participate...

Code: [Select]
[Fri Aug 18 21:38:07.522669 2023] [proxy:error] [pid 29938:tid 139680637339392] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /opt/alt/php-fpm82/usr/var/sockets/admin.sock (*:80) failed
[Fri Aug 18 21:38:07.522758 2023] [proxy_fcgi:error] [pid 29938:tid 139680637339392] [client 88.153.177.227:61213] AH01079: failed to make connection to backend: httpd-UDS
[Fri Aug 18 21:38:07.613322 2023] [proxy:error] [pid 29938:tid 139680620553984] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /opt/alt/php-fpm82/usr/var/sockets/admin.sock (*:80) failed
[Fri Aug 18 21:38:07.613349 2023] [proxy_fcgi:error] [pid 29938:tid 139680620553984] [client 88.153.177.227:61214] AH01079: failed to make connection to backend: httpd-UDS, referer: https://domain.tld/

It currently works, only when I choose "Apache default vhost template type: default" and using php-fpm doesn't work anymore....

I'm just tired of it and I'm thinking of switching to Plesk or cPanel, even if they cost a lot more money. Unless admins post a good tutorial that you can use without having to customize annoying individual domains...

I'm curious how long this goes on or how long I have to experiment there for hours until it really works again.

It's 2023 and for me IPv6 is now a must-have.... Whether it is a good idea for someone or not does not interest me.
It is needed and must also be possible.

Offline
****
Re: Offical ipv6 Support?
« Reply #29 on: August 18, 2023, 08:44:39 PM »
@dbmtr

I understand your frustration, the cure for now that we use is to lock the .conf files.
The updates also mess up the setting we need for the mirror servers we run.

Here is what we do:

cd /usr/local/apache/conf/
chattr +i *.conf
cd /usr/local/apache/conf.d/vhosts/
chattr +i *.conf

or you can do chattr +i /usr/local/apache/conf.d/vhosts/*.conf

I always like to make sure I'm in the right folder.

But if you have to do a change, you have to run the opposite chattr -i, make the changes, then relock.