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

ipv6 configs #67

Open
AlexDeltax opened this issue Aug 18, 2018 · 7 comments
Open

ipv6 configs #67

AlexDeltax opened this issue Aug 18, 2018 · 7 comments

Comments

@AlexDeltax
Copy link

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

@chrissnell
Copy link

chrissnell commented Sep 21, 2018

IPv6 broke for me on the last reboot:

Sep 21 20:54:21 jarvis systemd[1]: Starting Network Service...
Sep 21 20:54:21 jarvis systemd-networkd[353]: /run/systemd/network/dosync-eth0.network:8: Prefix len
gth is invalid, ignoring assignment: 
Sep 21 20:54:21 jarvis systemd-networkd[353]: eth0: Gained IPv6LL
Sep 21 20:54:21 jarvis systemd-networkd[353]: Enumeration completed
Sep 21 20:54:21 jarvis systemd[1]: Started Network Service.
Sep 21 20:54:21 jarvis systemd-networkd[353]: request_name_destroy_callback n_ref=1
Sep 21 20:54:21 jarvis systemd-networkd[353]: lo: Link is not managed by us
Sep 21 20:54:21 jarvis systemd-networkd[353]: eth0: Could not set route: No route to host
Sep 21 20:54:33 jarvis systemd-networkd[353]: eth0: Configured
Sep 21 21:02:03 jarvis systemd[1]: Stopping Network Service...
Sep 21 21:02:03 jarvis systemd[1]: Stopped Network Service.
Sep 21 21:02:03 jarvis systemd[1]: Starting Network Service...
Sep 21 21:02:03 jarvis systemd-networkd[567]: /run/systemd/network/dosync-eth0.network:8: Prefix len
gth is invalid, ignoring assignment: 
Sep 21 21:02:03 jarvis systemd-networkd[567]: eth0: Gained IPv6LL
Sep 21 21:02:03 jarvis systemd-networkd[567]: Enumeration completed
Sep 21 21:02:03 jarvis systemd[1]: Started Network Service.
Sep 21 21:02:03 jarvis systemd-networkd[567]: lo: Link is not managed by us
Sep 21 21:02:03 jarvis systemd-networkd[567]: request_name_destroy_callback n_ref=1
Sep 21 21:02:03 jarvis systemd-networkd[567]: eth0: Could not set route: No route to host
Sep 21 21:02:15 jarvis systemd-networkd[567]: eth0: Configured

Looks like the digitalocean-synchronize service is not getting an IPv6 prefix:

Sep 21 20:54:21 jarvis digitalocean-synchronize[351]: Added IPv6 address 2604:A880:0002:00D0:0000:0000:07FD:8001/ on eth0.

@gh2o
Copy link
Owner

gh2o commented Sep 21, 2018

I rebooted my droplet and it seems to be working fine.

What output do you get when you run curl http://169.254.169.254/metadata/v1/interfaces/public/0/ipv6/cidr and curl http://169.254.169.254/metadata/v1/interfaces/public/0/ipv6/?

@chrissnell
Copy link

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.

@gh2o
Copy link
Owner

gh2o commented Sep 21, 2018

I see. So rebooting it fixes the issue?

@chrissnell
Copy link

chrissnell commented Sep 21, 2018 via email

@chrissnell
Copy link

chrissnell commented Mar 2, 2019

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.

@chrissnell
Copy link

Here are some sanitized logs that show how metadata is sometimes missing:

Dec 01 20:31:01 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 01 20:31:01 jarvis digitalocean-synchronize[267]: Attempting to connect to metadata service ...
Dec 01 20:31:02 jarvis digitalocean-synchronize[301]: Added IPv4 address 138.xxx.xx.xxx/20 on eth0.
Dec 01 20:31:02 jarvis digitalocean-synchronize[306]: Added Anchor IPv4 address 10.x.xx.x/16 on eth0.
Dec 01 20:31:02 jarvis systemd[1]: Started DigitalOcean Synchronization.
-- Reboot --
Dec 05 21:01:03 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 05 21:01:04 jarvis systemd[1]: Started DigitalOcean Synchronization.
-- Reboot --
Dec 08 00:41:19 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 08 00:41:20 jarvis digitalocean-synchronize[335]: Added Anchor IPv4 address 10.x.xx.x/16 on eth0.
Dec 08 00:41:20 jarvis systemd[1]: Started DigitalOcean Synchronization.
-- Reboot --
Dec 13 03:41:46 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 13 03:41:46 jarvis digitalocean-synchronize[321]: Added IPv4 address 138.xxx.xx.xxx/20 on eth0.
Dec 13 03:41:46 jarvis digitalocean-synchronize[329]: Added Anchor IPv4 address 10.x.xx.x/16 on eth0.
Dec 13 03:41:47 jarvis systemd[1]: Started DigitalOcean Synchronization.
-- Reboot --
Dec 20 03:16:28 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 20 03:16:28 jarvis digitalocean-synchronize[252]: Attempting to connect to metadata service ...
Dec 20 03:16:29 jarvis systemd[1]: Started DigitalOcean Synchronization.
-- Reboot --
Dec 21 18:43:44 jarvis systemd[1]: Starting DigitalOcean Synchronization...
Dec 21 18:43:45 jarvis digitalocean-synchronize[333]: Added IPv4 address 138.xxx.xx.xxx/20 on eth0.
Dec 21 18:43:45 jarvis digitalocean-synchronize[342]: Added Anchor IPv4 address 10.x.xx.x/16 on eth0.
Dec 21 18:43:45 jarvis digitalocean-synchronize[360]: Added IPv6 address 2604:A880:0000:00D0:0000:0000:0000:8001/64 on eth0.

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

No branches or pull requests

3 participants