Replies: 2 comments
-
As a side note, I did see this about getting Docker itself to work with IPv6: https://docs.docker.com/config/daemon/ipv6/ After setting that up and adding all but the postgres service to that ipv6 network I got API error keys from ZTnet, so more work to do. |
Beta Was this translation helpful? Give feedback.
-
It looks like it was fairly simple. After I configured the cloud VPS instances to have dual-stack network adapters and assigned an IPv6 block to them, and to the VPS, I then made the changes mentioned in my last comment to enable IPv6 for Docker, and created the ip6net network. I think that only the ZeroTier container/service really needed to be in that network. I am now able to see some nodes connecting showing an IPv6 address which matches what I was seeing under the zerotier controller. I also had set it up using that Caddy image to provide an SSL proxy, so I put that in that ip6net network as well and it allows management over IPv6. |
Beta Was this translation helpful? Give feedback.
-
Looking to play around with IPv6, has anyone toyed with getting that working in this stack?
I am talking about the controller running on IPv6 so clients can connect to it that way, but I suppose it would also be interesting to see about the zerotier network being IPv6, but that may be a whole different discussion.
Beta Was this translation helpful? Give feedback.
All reactions