RUNNING.txt 1.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. First build it -- see BUILDING.txt -- then...
  2. -- MacOS --
  3. By convention, ZeroTier One will keep its state here on mac:
  4. /Library/Application Support/ZeroTier/One
  5. ZeroTier ships with a kernel extension for its own tap device, which it
  6. stores in the above directory. To install this from source, type:
  7. sudo make -f Makefile.mac install-mac-tap
  8. This will create the ZeroTier One home above if it does not exist and install
  9. the kext there. Note that the kext must be owned by root:wheel. The make
  10. rule for install-mac-tap takes care of that.
  11. Next, simply run the binary. It must be run as root to open the tap device.
  12. If run with no options, it will use the default home directory above.
  13. sudo ./zerotier-one &
  14. Finally, join the Earth network (the big public LAN and the only net for now):
  15. sudo zerotier-cli join bc8f9a8ee3000001
  16. Try pinging earth.zerotier.net and going to http://earth.zerotier.net/ in a
  17. browser to see if you're online.
  18. -- Linux
  19. On Linux, the default ZeroTier home is:
  20. /var/lib/zerotier-one
  21. Just type:
  22. sudo mkdir /var/lib/zerotier-one
  23. sudo ./zerotier-one &
  24. When run with no options, ZT1 uses its default home path on the current
  25. platform. Note that ZT1 requires the Linux tap driver, so it must be
  26. available in the kernel or as a module. In most Linux distributions it's
  27. included out of the box and should just work.
  28. Finally, join the Earth network (the big public LAN and the only net for now):
  29. sudo zerotier-cli join bc8f9a8ee3000001
  30. Try pinging earth.zerotier.net and going to http://earth.zerotier.net/ in a
  31. browser to see if you're online.
  32. -- Windows
  33. Port in progress, and it's going to pretty much always be more painful to
  34. build than *nix systems. Just wait for the binary release unless you're
  35. brave, in which case you can load the VS2012 solution and play around.