Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Server not bound to IPv6 address #244

Closed
thedufer opened this issue Oct 15, 2015 · 7 comments
Closed

Web Server not bound to IPv6 address #244

thedufer opened this issue Oct 15, 2015 · 7 comments

Comments

@thedufer
Copy link

nodejs.org is advertising both IPv4 and IPv6 addresses:

> dig nodejs.org AAAA
...
nodejs.org.     235 IN  AAAA    2400:cb00:2048:1::6814:162e
nodejs.org.     235 IN  AAAA    2400:cb00:2048:1::6814:172e
> dig nodejs.org A
...
nodejs.org.     203 IN  A   104.20.23.46
nodejs.org.     203 IN  A   104.20.22.46

However, connections to the IPv6 addresses simply hang until the client times out. This means that remote nvm commands, when curl chooses to try v6, take a minimum of 2 minutes. This is true of the newest nvm (0.29.0).

@rvagg
Copy link
Member

rvagg commented Oct 16, 2015

could you try again please @thedufer, they should be good to go now

@thedufer
Copy link
Author

I'm seeing the same issue. After a curl, it just hangs trying to connect:

> curl -vvv -6 http://nodejs.org/dist/
* Adding handle: conn: 0x7fbaca804400
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7fbaca804400) send_pipe: 1, recv_pipe: 0
* About to connect() to nodejs.org port 80 (#0)
*   Trying 2400:cb00:2048:1::6814:162e...

Eventually it just times out.

Both http and https work with the -4 flag and time out with the -6 flag.

@fhemberger
Copy link
Contributor

Fails directly for me (http and https), -4 works fine:

curl -vvv -6 http://nodejs.org/dist/
* Adding handle: conn: 0x7fea32806a00
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7fea32806a00) send_pipe: 1, recv_pipe: 0
* About to connect() to nodejs.org port 80 (#0)
*   Trying 2400:cb00:2048:1::6814:172e...
* Failed to connect to 2400:cb00:2048:1::6814:172e: No route to host
*   Trying 2400:cb00:2048:1::6814:162e...
* Failed to connect to 2400:cb00:2048:1::6814:162e: No route to host
* couldn't connect to host at nodejs.org:80
* Closing connection 0
curl: (7) Failed to connect to 2400:cb00:2048:1::6814:172e: No route to host

curl 7.30.0 (x86_64-apple-darwin13.0) libcurl/7.30.0 SecureTransport zlib/1.2.5

@silverwind
Copy link
Contributor

Works for me

$ curl -vvv -6 http://nodejs.org/dist/
* About to connect() to nodejs.org port 80 (#0)
*   Trying 2400:cb00:2048:1::6814:162e...
* connected
* Connected to nodejs.org (2400:cb00:2048:1::6814:162e) port 80 (#0)
> GET /dist/ HTTP/1.1
> User-Agent: curl/7.26.0
> Host: nodejs.org
> Accept: */*
>
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Date: Fri, 16 Oct 2015 17:45:15 GMT
...

curl 7.26.0 (x86_64-pc-linux-gnu) libcurl/7.26.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3

@fhemberger
Copy link
Contributor

Ah, sorry. Works for me as well, IPv6 was disabled on my local router. 😓

@fhemberger
Copy link
Contributor

@thedufer Can you please check if the problem is fixed for you, so we can close this issue?

@thedufer
Copy link
Author

Sorry for the slow response. Yeah, it looks better now. I think my most recent comment was after running while I was on a VPN that doesn't play nicely with IPv6, so that may have been a false negative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants