4 uAnytun can be built by using either libgcrypt, libnettle or the openssl-crypto
5 library. The latter is more performant in most cases but there are some license
6 issues when using this library. It also needs more space when installed.
11 (this includes Debian with FreeBSD Kernel)
18 using ssl crypto library:
23 using nettle crypto library:
28 if you want clang as compiler
32 if you want to rebuild the manpage:
45 using ssl crypto library:
49 if you want to rebuild the manpage:
62 Getting the source via subversion:
63 ----------------------------------
65 svn co https://svn.anytun.org/uanytun/trunk uanytun
78 using ssl crypto library:
81 # ./configure --use-ssl-crypto
85 - try './configure --help' for further information
86 - if using openssl pre 0.9.8 you have to disable passphrase
87 because openssl had no SHA256 implementation prior to this
89 - on OpenBSD/FreeBSD you have to use gmake instead of make
97 This will install anytun under the --prefix defined with configure.
105 This removes everything except for the config files
109 This also removes the config files
119 The init.d script can be used to start uanytun at boot time. It searches for
120 configuration files which reside at $CONFIG_DIR. For each instance of uanytun
121 which should be started there must be a directory containing at least a file
122 named config. This file must contain all command line parameter which should
123 be used when starting the daemon. One line for each parameter. Empty lines and
124 lines starting with # are ignored. Besides the config file there may be a script
125 named post-up.sh which will be called when the tun/tap device comes up.
126 This is an example of how the init.d script can be used to start uanytun:
128 # /etc/init.d/uanytun start client1 p2p-a
130 In this case the script will start 2 instances of uanytun using the config files
131 $CONFIG_DIR/client1/config and $CONFIG_DIR/p2p-a/config.
132 If no instance name is specified the script will use the file $CONFIG_DIR/autostart
133 to determine which instances to start or stop. This file must contain a list
134 of instance names which should be used when no names are specified at the command
135 line. One line for each name. Empty lines and lines starting with # are ignored.