4 Anytun 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.
10 (this includes Debian with FreeBSD Kernel)
15 using ssl crypto library:
18 using nettle crypto library:
23 libboost-serialization-dev
28 if you want clang as compiler
31 if you want to rebuild the manpage:
45 devel/boost (boost-libs on newer versions of the ports tree)
48 if you want to rebuild the manpage:
60 Crosscompiling with MinGW under Debian/Ubuntu:
61 ----------------------------------------------
63 # sudo apt-get install mingw-w64
65 # ./build-boost-mingw-cross.sh
66 # ./build-openssl-mingw-cross.sh
67 # ./build-anytun-mingw-cross.sh
69 The compiled binaries can be found in anytun-w32 and anytun-w64 (32 and 64Bit).
70 You can create a ZIP archive containing all needed files by calling:
72 # ./make-mingw-release.sh
79 http://www.slproweb.com/download/Win32OpenSSL-1_0_1h.exe
82 http://www.slproweb.com/download/Win32OpenSSL_Light-1_0_1h.exe
85 http://sourceforge.net/projects/boost/files/boost-binaries/
87 As it can take some time to install everything from boost here is a
88 complete list of libraries which have to be installed in order to build anytun:
96 Microsoft Visual C++ 2008 Redistributable Package (x86):
97 http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF
105 Getting the source via GIT:
106 ---------------------------
108 git clone https://git.spreadspace.org/anytun/anytun.git
120 using ssl crypto library:
123 # ./configure --use-ssl-crypto
128 - try './configure --help' for further information
129 - if using openssl pre 0.9.8 you have to disable passphrase
130 because openssl had no SHA256 implementation prior to this
132 - on FreeBSD you have to use gmake instead of make
133 - the FreeBSD port has some issues concering daemonizing and signal handling
140 This will install anytun under the --prefix defined with configure.
148 This removes everything except for the config files
152 This also removes the config files
162 The init.d script can be used to start anytun at boot time. It searches for
163 configuration files which reside at $CONFIG_DIR. For each instance of anytun
164 which should be started there must be a directory containing at least a file
165 named config. This file must contain all command line parameter which should
166 be used when starting the daemon. One line for each parameter. Empty lines and
167 lines starting with # are ignored. Besides the config file there may be a script
168 named post-up.sh which will be called when the tun/tap device comes up.
169 Furthermore there may be a directory called conf.d containing config files for
170 anytun-config. The syntax of this files is quite the same as those for anytun.
171 These files are used to configure a multi connection setup using anytun-config
173 This is an example of how the script can be used to start anytun:
175 # /etc/init.d/anytun start client1 p2p-a
177 In this case the script will start 2 instances of anytun using the config files
178 $CONFIG_DIR/client1/config and $CONFIG_DIR/p2p-a/config.
179 If no instance name is specified the script will use the file $CONFIG_DIR/autostart
180 to determine which instances to start or stop. This file must contain a list
181 of instance names which should be used when no names are specified at the command
182 line. One line for each name. Empty lines and lines starting with # are ignored.
188 Using the provided service units, anytun can now be started and managed via Systemd.
189 As with the init.d script, each VPN or anytun instance, identified by it's $vpnname,
190 needs it's own configuration subdirectory. E.g.: ${PREFIX}/etc/anytun/${vpnname}/.
191 For each such CLIENT instance, use the following command to enable it:
193 # systemctl enable anytun@${vpnname}.service
195 Manually start and stop instances by replacing enable with start or stop.
201 Note: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)
202 Cannot open TUN/TAP dev /dev/anytun0: No such file or directory (errno=2)
204 Solution: Enabling tun/tap device
205 ------------------------------------
211 edit /etc/modules and add the line
213 to load the module automatically