4 Anytun can be built by using either libgcrypt or the openssl-crypto library.
5 The latter is more performant in most cases but there are some license
6 issues when using this library.
10 (this includes Debian with FreeBSD Kernel)
20 libboost-serialization1.35-dev
21 libboost-thread1.35-dev
22 libboost-system1.35-dev
23 libboost-regex1.35-dev
25 if you want to rebuild the manpage:
39 devel/boost (boost-libs on newer versions of the ports tree)
42 if you want to rebuild the manpage:
55 http://www.slproweb.com/download/Win32OpenSSL-0_9_8j.exe
58 http://www.slproweb.com/download/Win32OpenSSL_Light-0_9_8j.exe
61 http://www.boostpro.com/download/boost_1_35_0_setup.exe
63 As it can take some time to install everything from boost here is a
64 complete list of libraries which have to be installed in order to build anytun:
72 Microsoft Visual C++ 2008 Redistributable Package (x86):
73 http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF
80 Getting the source via subversion:
81 ----------------------------------
82 svn co http://svn.anytun.org/anytun/trunk anytun
94 using ssl crypto library:
97 # ./configure --use-ssl-crypto
102 - try './configure --help' for further information
103 - if using openssl pre 0.9.8 you have to disable passphrase
104 because openssl had no SHA256 implementation prior to this
106 - on FreeBSD you have to use gmake instead of make
107 - the FreeBSD port has some issues concering daemonizing and signal handling
114 This will install anytun under the --prefix defined with configure.
121 This removes everything except for the config files
125 This also removes the config files
135 The init.d script can be used to start anytun at boot time. It searches for
136 configuration files which reside at $CONFIG_DIR. For each instance of anytun
137 which should be started there must be a directory containing at least a file
138 named config. This file must contain all command line parameter which should
139 be used when starting the daemon. One line for each parameter. Empty lines and
140 lines starting with # are ignored. Besides the config file there may be a script
141 named post-up.sh which will be called when the tun/tap device comes up.
142 Furthermore there may be a directory called conf.d containing config files for
143 anytun-config. The syntax of this files is quite the same as those for anytun.
144 These files are used to configure a multi connection setup using anytun-config
146 This is an example of how the script can be used to start anytun:
148 # /etc/init.d/anytun start client1 p2p-a
150 In this case the script will start 2 instances of anytun using the config files
151 $CONFIG_DIR/client1/config and $CONFIG_DIR/p2p-a/config.
152 If no instance name is specified the script will use the file $CONFIG_DIR/autostart
153 to determine which instances to start or stop. This file must contain a list
154 of instance names which should be used when no names are specified at the command
155 line. One line for each name. Empty lines and lines starting with # are ignored.
162 Note: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)
163 Cannot open TUN/TAP dev /dev/anytun0: No such file or directory (errno=2)
165 Solution: Enabling tun/tap device
166 ------------------------------------
172 edit /etc/modules and add the line
174 to load the module automatically