Using without an account
you can run your own controller and dont have to have an account
I needed to run sudo to use the zerotier-cli, I suspect I could change the permissions of the authentication token files but either way this was a blocker until I figured this out.
I'd like to work out the best way to handle permissions for this issue and include it in the wiki if that suits whoever is maintaining this page.
- I was able to achieve a pretty seamless permission experience (i.e. no use of
sudo) by copying the auth token into my home directory, like so:
sudo cat /var/lib/zerotier-one/authtoken.secret > ~/.zeroTierOneAuthToken
- Bjeanes (talk) 02:56, 28 September 2020 (UTC)
Zero Tier interface did not appear until reboot
When setting up the zerotier-cli for the first time, I couldn't ping my friend's computer. Although the zerotierone daemon status showed no errors there was no interface under ifconfig.
After reboot, the problem was resolved. It'd be good to have this as a check to avoid others running into the frustration of having a correctly configured network but left unable to ping because of this simple oversight!
DHCP not necessary
Under configuration there is a sentence which states, "You may need to run dhcpcd to acquire the new IP address locally." However, the zerotier-one daemon will issue IP addresses and if you enable dhcp on the virutal interface it will remove the IP applied by the daemon. There may be circumstances which require DHCP and that is probably why the line says it may be necessary, but this is misleading since it does not describe when or why. DraconianSoul (talk) 17:16, 24 September 2019 (UTC)