blob: 0c17088bb7b6fe294cd99c079aa290705811fee5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
Running ZeroTier One from a source build:
-- MacOS
By convention, ZeroTier One will keep its state here on mac:
/Library/Application Support/ZeroTier/One
ZeroTier ships with a kernel extension for its own tap device, which it
stores in the above directory. To install this from source, type:
sudo make -f Makefile.mac install-mac-tap
This will create the ZeroTier One home above if it does not exist and install
the kext there. Note that the kext must be owned by root:wheel. The make
rule for install-mac-tap takes care of that.
Next, simply run the binary. It must be run as root to open the tap device.
If run with no options, it will use the default home directory above.
sudo ./zerotier-one &
Type "ifconfig" and look for the new interface, which should be called
"zt0." The strange IPv4 address it has is your "zero4" address. Visit
http://zerotier.net/ to check your connection.
Kill it with something like:
sudo killall zerotier-one
-- Linux
On Linux, the default ZeroTier home is:
/var/lib/zerotier-one
We use the Linux native tap driver, so no special drivers are needed. Just
type:
sudo mkdir /var/lib/zerotier-one
sudo ./zerotier-one &
When run with no options, ZT1 uses its default home path on the current
platform.
Type ifconfig and you should see an interface like "zt0." Then try
http://zerotier.net or ping zerotier.net to check your connection.
-- Windows
To run for manual testing, build the ZeroTierOne VS2012 project and run it
in an administrator-privileged command prompt window.
|
