-
Notifications
You must be signed in to change notification settings - Fork 70
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
ipv6 configs #67
Comments
IPv6 broke for me on the last reboot:
Looks like the digitalocean-synchronize service is not getting an IPv6 prefix:
|
I rebooted my droplet and it seems to be working fine. What output do you get when you run |
I get the v6 prefix when I curl this. Perhaps its an intermittent failure? Maybe there should be an exit code check from curl and the request gets retried if it's an error. |
I see. So rebooting it fixes the issue? |
Yes, it does. Intermittent failure.
…On Fri, Sep 21, 2018 at 4:42 PM Gavin Li ***@***.***> wrote:
I see. So rebooting it fixes the issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBd8uRQKM29gnUOqZl-OlQVp_dRPOuvks5udV1MgaJpZM4WCuNd>
.
|
I'm now seeing IPv4 IP setup failures and gateway setup fialures too. Lately, my droplet comes up correctly from a reboot about 50% of the time. I assume it is because of flakiness on the metadata service. Sure would be nice to have some retries with curl. |
Here are some sanitized logs that show how metadata is sometimes missing:
|
How to configurate ipv6 for Droplet with archlinux?
All configs due too wiki are missing and I even don't know how to make server been anable via ipv6
The text was updated successfully, but these errors were encountered: