GUARANTEE THAT THERE WILL BE PROTOCOL COMPATIBILITY BETWEEN DIFFERENT
VERSIONS.
-PROTOCOL COMPATIBILITY WAS BROKEN BETWEEN secnet-0.06, secnet-0.07 AND
-secnet-0.08 FOR ENDIANNESS FIXES.
-
-THERE WILL BE ANOTHER CHANGE IN PROTOCOL IN THE secnet-0.1.x SERIES
-
* Preparation
** System software support
-Ensure that you have libgmp2-dev and adns installed (and bison and
+Ensure that you have libgmp3-dev and adns installed (and bison and
flex, and for that matter gcc...).
[On BSD install /usr/ports/devel/bison]
If you're using TUN/TAP on a platform other than Linux-2.4, see
http://vtun.sourceforge.net/tun/
-Note than TUN comes in several flavours. Their names in the
-configuration file are:
- tun: Linux-2.4; only one device file (usually /dev/net/tun)
- tun-old: Linux-2.2, BSD; device files /dev/tun*
- tun-solaris: Solaris (not yet implemented)
-
** System and network configuration
If you intend to start secnet as root, I suggest you create a userid
# cp example.conf /etc/secnet/secnet.conf
# cd /etc/secnet
-# ssh-keygen -f key -N ""
+# ssh-keygen -f key -t rsa1 -N ""
[On BSD use
$ LDFLAGS="-L/usr/local/lib" ./configure
port number on the front-end machine, and does not necessarily have to
match the port number on the machine running secnet. If you want to
use a privileged port number we suggest 410. An appropriate
-unprivileged port number is 51396. (These numbers were picked at
-random.)
+unprivileged port number is 51396.
6. the list of networks accessible at your site over the VPN.