[jira] [Updated] (INFRA-11567) IPv6 is not working on 2a01:4f8:130:2192::2 host

["Chris Lambertus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambertus updated INFRA-11567:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

I can't reproduce this. I've tried several validators and proxy services (I don't have native IPv6 connectivity) against 2a10[...]. Hitting http://[2a01:4f8:130:2192::2] seems to properly return the apache.org home page as expected.

Can you please provide a little more information on your setup? Are you using an ipv4->v6 tunnel? What is your IPv6 source address, or v4 if tunneled?


> IPv6 is not working on 2a01:4f8:130:2192::2 host
> ------------------------------------------------
>
>                 Key: INFRA-11567
>                 URL: https://issues.apache.org/jira/browse/INFRA-11567
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: DNS, Website
>            Reporter: Sylvain Rochet
>            Priority: Minor
>
> 2a01:4f8:130:2192::2 is the IPv6 address currently set for, at least, http://httpd.apache.org and http://apr.apache.org.
> $ dig +short -t AAAA httpd.apache.org
> 2a01:4f8:130:2192::2
> $ dig +short -t AAAA apr.apache.org
> 2a01:4f8:130:2192::2
> IPv4 is working fine but IPv6 hang forever:
> $ telnet 88.198.26.2 80
> Trying 88.198.26.2...
> Connected to 88.198.26.2.
> Escape character is '^]'.
> GET / HTTP/1.1
> Host: httpd.apache.org
> HTTP/1.1 200 OK
> Date: Tue, 29 Mar 2016 21:21:00 GMT
> Server: Apache/2.4.7 (Ubuntu)
> Last-Modified: Sat, 20 Feb 2016 10:44:41 GMT
> ETag: "21a9-52c3149824b03"
> Accept-Ranges: bytes
> Content-Length: 8617
> Vary: Accept-Encoding
> Content-Type: text/html
> $ telnet 2a01:4f8:130:2192::2 80
> Trying 2a01:4f8:130:2192::2...
> Connected to 2a01:4f8:130:2192::2.
> Escape character is '^]'.
> GET / HTTP/1.1
> Host: httpd.apache.org
> [HANG HERE]
> That's a problem, because most browsers don't failback to IPv4 if the IPv6 TCP session is properly established but hang forever. Currently, all IPv6 enabled browsers can't access to anything hosted on 2a01:4f8:130:2192::2 at all



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)