feat: IPv6 support

[M96268004]

Feature Request

Describe the Feature Request

Thanks, the ui are great, will you plan to adding IPv6 support?

[dec0dOS]

Hey, @M96268004!
For now, supporting IPv6 in ZeroUI is the low priority task.

On the ZeroTier VL1 level, all IPv6-enabled devices will work as expected, so you'll do not have any issues with IPv6-only public address devices.
The real thing is just ideological preference for system administrators.

If you have special IPv6-only workflow, I'd like to know. Thank you!

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍.
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[xaverruss]

Hi,
I am writing here so that the Bot doesn't close this feature request.

IPv6 Support would still be a desirable feature, atleast for some.
I, for example, haven't moved over from ztncui because we use IPv6 exclusive throughout multiple sites for internal communication and access to Gitlab / Storage / remote access.
With the support of Tags and Flow Rules on this side I already tried "curling" the Ipv6 support into the controller directly.
But its quite inconvenient and definitely nothing I'd like to do in our production setup.
(yes we use a non official Controller in sort of productive use, but in a association not in a organisation)
Thanks!

[dec0dOS]

Thanks for sharing your usecase. Well, I should reconsider about the IPv6 support in ZeroUI.

[xaverruss]

One thing I'd like to mention is the optimisation of IPv6 in terms of big networks.

With your support of taggs and flow rules and the use of IPv6 6plane in Zerotier Networks,
the whole Site to Site, (from home)Client and Server (including kubernetes / docker / other virtualisation) could use one single big network without having to deal with L3 Routing at all.
Just add it to the Network and set Tags and Rules accordingly.

I haven't digged deeper into the security yet, so I am not sure if this would hold up against possible security consernes, but this is the purpose for the tag and flowrule feature, right ?

This could be done with one bigger IPv4 Network aswell of course, something like 172.30.0.0/16 would satisfy most, if not all networks that consider deploying something like Zerotier I'd assume.

But using v4 one would loose the routable /80 network assigned to each node, which comes in as a big bonus for Server side networking imo.

Adding to that, IPv4 was never really designed to handle such massive networks afaik.

Btw, I currently deploy separate networks and use routing nodes for inter-network communication

Another thing I'd like to add is the use of custom Global Unicast Addresses,
one of our current networks deploys static globally routable IPv6 Addresses,
that we get and route from a vServer at a cloud Hoster. (Hetzner)

And because this is inside Zerotier, every Node in that networks has its own static globally routable IPv6 address
wherever they may be or go.
This also works the other way around, global IPv6 Networking for all nodes, even if they only have IPv4 Network at their site.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍.
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[trobotham]

I have a specific use-case for IPv6 myself, we use it in production and use it in ztncui, it would be awesome to see it.

Awesome work by the way!

👍🏻

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍.
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[bstin]

There are a couple of levels of IPv6 support, I suspect the biggest missing feature is just a checkbox to enable:

• ZT 6plane
• ZT rfc4193

Actually setting up IPv6 assignment pools is a separate issue that could be done at a later phase.

For those of us using 6PLANE having just a checkbox to set the '{"v6AssignMode":{"6plane":true}}' would be a big help (currently now you can set it via curl, however its a bit clunky to do from inside the container.....)

[Semisol]

For those of us using 6PLANE having just a checkbox to set the '{"v6AssignMode":{"6plane":true}}' would be a big help (currently now you can set it via curl, however its a bit clunky to do from inside the container.....)

How do you do this?

I would be interested in this feature too.

[bstin]

How do you do this?

Something like this (this is completely untested but should get you closer).

1. Enter docker container (ie. docker exec -it /bin/bash)
2. Install curl in docker container (if needed)
3. run something like:

curl -X POST --header "X-ZT1-Auth: $(cat /var/lib/zerotierone/authtoken.secret)" -d '{"v6AssignMode":{"6plane":true}}' http://localhost:9993/controller/network/<NETWORKID>