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

errors with no ipv6 connectivity #1314

Closed
chrishiestand opened this issue May 13, 2016 · 4 comments
Closed

errors with no ipv6 connectivity #1314

chrishiestand opened this issue May 13, 2016 · 4 comments
Assignees
Labels
core type: question Request for information or clarification. Not an issue.

Comments

@chrishiestand
Copy link
Contributor

chrishiestand commented May 13, 2016

While using gcloud v0.33.0 (thanks for all the grpc improvements so far) I'm still getting some additional output:

E0513 15:32:42.397461000 123145307668480 tcp_client_posix.c:191] failed to connect to 'ipv6:[2607:f8b0:400e:c00::ef]:443': timeout occurred
E0513 15:32:45.284575000 123145306595328 tcp_client_posix.c:191] failed to connect to 'ipv6:[2607:f8b0:400e:c00::ef]:443': timeout occurred

I don't have ipv6 WAN connectivity at the moment. This is not fatal since ipv4 is used successfully instead.

Is there anyway to disable ipv6 in gcloud-node/grpc to avoid these error messages (and possible additional latency?)?

You could argue this is an OS issue and that if a public ipv6 address is available it should be okay to assume it can be used. I do seem to be getting public 2602:: addresses even though I'm not using them WAN-wise (I am on a LAN where I don't control the router, and maybe this network is misconfigured). If my context is rare it's fine to simply close this issue.

If I disable ipv6 entirely in the OS the errors do disappear.

@stephenplusplus
Copy link
Contributor

Cc @murgatroid99 @ctiller

@stephenplusplus stephenplusplus added core type: question Request for information or clarification. Not an issue. labels May 14, 2016
@stephenplusplus
Copy link
Contributor

This issue was moved to grpc/grpc#6623

@stephenplusplus
Copy link
Contributor

Hey @chrishiestand, I moved this over to gRPC so the right eyes can take a look. I'll keep an eye on it as well, in case there is anything we can do in gcloud-node.

@chrishiestand
Copy link
Contributor Author

Thanks @stephenplusplus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants