-
Notifications
You must be signed in to change notification settings - Fork 591
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
Labels
Comments
stephenplusplus
added
core
type: question
Request for information or clarification. Not an issue.
labels
May 14, 2016
This issue was moved to grpc/grpc#6623 |
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. |
Thanks @stephenplusplus |
chingor13
pushed a commit
that referenced
this issue
Aug 22, 2022
chingor13
pushed a commit
that referenced
this issue
Aug 22, 2022
chingor13
pushed a commit
that referenced
this issue
Aug 22, 2022
chingor13
pushed a commit
that referenced
this issue
Aug 26, 2022
chingor13
pushed a commit
that referenced
this issue
Sep 12, 2022
chingor13
pushed a commit
that referenced
this issue
Sep 13, 2022
chingor13
pushed a commit
that referenced
this issue
Sep 14, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Sep 15, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Sep 16, 2022
sofisl
pushed a commit
that referenced
this issue
Oct 5, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Oct 5, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Oct 8, 2022
This was referenced Oct 11, 2022
sofisl
pushed a commit
that referenced
this issue
Oct 11, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Nov 16, 2022
sofisl
pushed a commit
that referenced
this issue
Nov 16, 2022
This was referenced Nov 16, 2022
sofisl
pushed a commit
that referenced
this issue
Nov 16, 2022
This was referenced Nov 16, 2022
sofisl
pushed a commit
that referenced
this issue
Nov 16, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Nov 16, 2022
sofisl
pushed a commit
that referenced
this issue
Nov 17, 2022
This was referenced Nov 17, 2022
sofisl
pushed a commit
that referenced
this issue
Nov 18, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Nov 30, 2022
4 tasks
sofisl
pushed a commit
that referenced
this issue
Jan 10, 2023
4 tasks
sofisl
pushed a commit
that referenced
this issue
Jan 17, 2023
sofisl
pushed a commit
that referenced
this issue
Jan 26, 2023
4 tasks
4 tasks
sofisl
pushed a commit
that referenced
this issue
Sep 13, 2023
4 tasks
sofisl
pushed a commit
that referenced
this issue
Sep 14, 2023
4 tasks
This was referenced Jan 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While using gcloud v0.33.0 (thanks for all the grpc improvements so far) I'm still getting some additional output:
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.
The text was updated successfully, but these errors were encountered: