|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #53881 IPv6 broken
Submitted: 2011-01-29 23:58 UTC Modified: 2012-05-15 21:25 UTC
From: tozz at kijkt dot tv Assigned: danbrown (profile)
Status: Wont fix Package: Unknown/Other Function
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: tozz at kijkt dot tv
New email:
PHP Version: OS:


 [2011-01-29 23:58 UTC] tozz at kijkt dot tv
------------ has some AAAA records which are very often broken (currently 2 out of 3 are broken). From what I've read PHP checks its mirrors on regular intervals, but apparently does not check if both IP4 and IP6 work. The lack of this IPv6 check causes the PHP website to load very slow as it waits a few seconds for a timeout on v6 and then falls back to v4.

Perhaps this check can be extended to also check for correct IPv6 function and remove the mirror if its IPv6 connectivity is broken.

Test script:
# date
Sat Jan 29 23:20:16 CET 2011

# telnet -6 80
Trying 2a01:448:1::1036:64:164...
telnet: Unable to connect to remote host: Connection refused

# telnet -6 80 
Trying 2a00:f10:111::1337:1000...
telnet: Unable to connect to remote host: No route to host

Expected result:
I would expect that the PHP mirror check removes mirrors that have broken v6 connectivity.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-01-30 00:04 UTC] tozz at kijkt dot tv
IPv6 traceroute to the SinnerG broken mirror (to indicate its not a routing issue on my side):

# traceroute6 2a00:f10:111::1337:1000
traceroute to 2a00:f10:111::1337:1000 (2a00:f10:111::1337:1000) from 2a01:1b0:7999:402::3, 30 hops max, 24 byte packets
 1  2a01:1b0:7999:402::e (2a01:1b0:7999:402::e)  0.854 ms  0.952 ms  0.99 ms
 2  2a01:1b0:2:6::1 (2a01:1b0:2:6::1)  4.985 ms  4.979 ms  4.991 ms
 3 (2001:7f8:13::a501:2859:2)  5.987 ms  5.968 ms  5.99 ms
 4 (2001:7f8:1::a502:5525:1)  6.987 ms  5.974 ms  5.988 ms
 5  2001:16f8:bb2:197:0:a504:8635:2 (2001:16f8:bb2:197:0:a504:8635:2)  6.989 ms  7.972 ms  6.99 ms
 6  2a00:f10:10a:2::4 (2a00:f10:10a:2::4)  6.987 ms  6.977 ms  6.99 ms
 7  2a00:f10:10a:2::4 (2a00:f10:10a:2::4)  3010.85 ms !H  3010.81 ms !H  3007.83 ms !H
 [2012-05-15 21:04 UTC]
-Status: Open +Status: Wont fix -Assigned To: +Assigned To: danbrown
 [2012-05-15 21:04 UTC]
At this time, we do not require IPv6 capabilities on official mirrors.  
We will begin to phase-in this requirement once the majority of the ISPs and NOCs 
which host the official mirrors have IPv6 support permanently enabled, and expect 
to see an increase in that number on 6 June, 2012 (World IPv6 Day), as is the 
norm each year.

Thank you for submitting this report.
 [2012-05-15 21:11 UTC] tozz at kijkt dot tv
I understand IPv6 is not a requirement. However, some mirrors do have an AAAA-Address but fail to provide working connectivity to that address. The net result is that the PHP website is down for anyone with IPv6 connectivity if he/she is redirected to a mirror with bad IPv6 connectivity.

So either the AAAA records should be removed or should require mirrors to have decent IPv6 connectivity.
 [2012-05-15 21:25 UTC]
While I do appreciate your suggestions, this is still not something we're going 
to fix at this stage.

Also, sometime after you originally submitted this bug, was removed 
from our network.

Finally, for anyone using IPv6 as their exclusive (or even primary) network 
routing, I'm sure there are far greater issues than an occasionally-broken PHP 
mirror.  Again, we will address this at a point, just not this point.

Thanks again.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon Jun 17 22:01:28 2024 UTC