4 Except for common @code{-mtu}, @code{-stats}, @code{-egd} options server
5 has the following ones:
10 @ref{Network, network protocol} to use. Can be @emph{udp} (default),
11 @emph{tcp} or @emph{all}.
14 Address (@code{host:port} format) we must bind to.
17 Path to JSON file with the configuration.
20 Start trivial HTTP @ref{Proxy} server on specified @emph{host:port}.
24 Configuration file is JSON file with following example structure:
28 "stargrave": { <-- Peer human readable name
29 "iface": "tap10", <-- OPTIONAL TAP interface name
30 "up": "./stargrave-up.sh", <-- OPTIONAL up-script
31 "down": "./stargrave-down.sh", <-- OPTIONAL down-script
32 "timeout": 60, <-- OPTIONAL overriden timeout
33 "noise": true, <-- OPTIONAL noise enabler
35 "cpr": 64, <-- OPTIONAL constant packet
37 "verifier": "$argon2d..." <-- verifier received from client
43 At least one of either @code{iface} or @code{up} must be specified. If
44 you specify @code{iface}, then it will be forcefully used to determine
45 what TAP interface will be used. If it is not specified, then up-script
46 must output interface's name to stdout (first output line).
48 For example up-script can be just @code{echo tap10}, or more advanced
49 like the following one:
53 $tap=$(ifconfig tap create)
54 ifconfig $tap inet6 fc00::1/96 mtu 1412 up
58 Each minute server rereads and refreshes peers configuration and adds
59 newly appeared identities, deletes an obsolete ones.
61 You can use convenient @code{utils/newclient.sh} script for new client
65 % ./utils/newclient.sh Alice
67 Your client verifier is: $argon2d$m=4096,t=128,p=1$bwR5VjeCYIQaa8SeaI3rqg
69 Place the following JSON configuration entry on the server's side:
72 "up": "/path/to/up.sh",
73 "iface": "or TAP interface name",
74 "verifier": "$argon2d$m=4096,t=128,p=1$bwR5VjeCYIQaa8SeaI3rqg$KCNIqfS4DGsBTtVytamAzcISgrlEWvNxan1UfBrFu10"