Overview of the gnu virtual private ethernet suite.
\s-1GVPE\s0 is a suite designed to provide a virtual private network for multiple nodes over an untrusted network. This document first gives an introduction to VPNs in general and then describes the specific implementation of \s-1GVPE\s0.
\s-1VPN\s0 is an acronym, it stands for:
Virtual means that no physical network is created (of course), but a network is emulated by creating multiple tunnels between the member nodes by encapsulating and sending data over another transport network. Usually the emulated network is a normal \s-1IP\s0 or Ethernet, and the transport network is the Internet. However, using a \s-1VPN\s0 system like \s-1GVPE\s0 to connect nodes over other untrusted networks such as Wireless \s-1LAN\s0 is not uncommon.
Private means that non-participating nodes cannot decode (\*(L"sniff)\*(R" nor inject (\*(L"spoof\*(R") packets. This means that nodes can be connected over untrusted networks such as the public Internet without fear of being eavesdropped while at the same time being able to trust data sent by other nodes. In the case of \s-1GVPE\s0, even participating nodes cannot sniff packets send to other nodes or spoof packets as if sent from other nodes, so communications between any two nodes is private to those two nodes.
Network means that more than two parties can participate in the network, so for instance it's possible to connect multiple branches of a company into a single network. Many so-called \*(L"\s-1VPN\s0\*(R" solutions only create point-to-point tunnels, which in turn can be used to build larger networks. \s-1GVPE\s0 provides a true multi-point network in which any number of nodes (at least a few dozen in practise, the theoretical limit is 4095 nodes) can participate.
Cipher, \s-1HMAC\s0 algorithms and other key parameters must be selected at compile time - this makes it possible to only link in algorithms you actually need. It also makes the crypto part of the source very transparent and easy to inspect, and last not least this makes it possible to hardcode the layout of all packets into the binary. \s-1GVPE\s0 goes a step further and internally reserves blocks of the same length for all packets, which virtually removes all possibilities of buffer overflows, as there is only a single type of buffer and it's always of fixed length.
A few lines of config (the config file is shared unmodified between all hosts) and a single run of \*(C`gvpectrl\*(C' to generate the keys suffices to make it work.
Since every host has it's own private key, other hosts cannot spoof traffic from this host. That makes it possible to filter packet by \s-1MAC\s0 address, e.g. to ensure that packets from a specific \s-1IP\s0 address come, in fact, from a specific host that is associated with that \s-1IP\s0 and not from another host.
Gvpe comes with two programs: one daemon (\*(C`gvpe\*(C') and one control program (\*(C`gvpectrl\*(C').
This program is used to generate the keys, check and give an overview of of the configuration and to control the daemon (restarting etc.).
This is the daemon used to establish and maintain connections to the other network nodes. It should be run on the gateway of each \s-1VPN\s0 subnet.
Please have a look at the \*(C`gvpe.osdep(5)\*(C' manpage for platform-specific information.
Gvpe hardcodes most encryption parameters. While this reduces flexibility, it makes the program much simpler and helps making buffer overflows impossible under most circumstances.
Here are a few recipes for compiling your gvpe, showing the extremes (fast, small, insecure \s-1OR\s0 slow, large, more secure), between which you should choose:
./configure --enable-hmac-length=4 --enable-rand-length=0
Minimize the header overhead of \s-1VPN\s0 packets (the above will result in only 4 bytes of overhead over the raw ethernet frame). This is a insecure configuration because a \s-1HMAC\s0 length of 4 makes collision attacks almost trivial.
./configure --enable-cipher=bf --enable-digest=md4
Use the fastest cipher and digest algorithms currently available in gvpe. \s-1MD4\s0 has been broken and is quite insecure, though, so using another digest algorithm is recommended.
./configure --enable-hmac-length=16 --enable-rand-length=12 --enable-digest=ripemd610
This uses a 16 byte \s-1HMAC\s0 checksum to authenticate packets (I guess 8-12 would also be pretty secure ;) and will additionally prefix each packet with 12 bytes of random data.
In general, remember that \s-1AES-128\s0 seems to be as secure but faster than \s-1AES-192\s0 or \s-1AES-256\s0, more randomness helps against sniffing and a longer \s-1HMAC\s0 helps against spoofing. \s-1MD4\s0 is a fast digest, \s-1SHA1\s0, \s-1RIPEMD160\s0, \s-1SHA256\s0 are consecutively better, and Blowfish is a fast cipher (and also quite secure).
In this section I will describe how to get a simple \s-1VPN\s0 consisting of three hosts up and running.
First you have to create a daemon configuration file and put it into the configuration directory. This is usually \*(C`/etc/gvpe\*(C', depending on how you configured gvpe, and can be overwritten using the \*(C`-c\*(C' command line switch.
Put the following lines into \*(C`/etc/gvpe/gvpe.conf\*(C':
udp-port = 50000 # the external port to listen on (configure your firewall) mtu = 1400 # minimum MTU of all outgoing interfaces on all hosts ifname = vpn0 # the local network device name
node = first # just a nickname hostname = first.example.net # the DNS name or IP address of the host
node = second hostname = 126.96.36.199
node = third hostname = third.example.net
The only other file necessary is the \*(C`if-up\*(C' script that initializes the virtual ethernet interface on the local host. Put the following lines into \*(C`/etc/gvpe/if-up\*(C' and make it executable (\*(C`chmod 755 /etc/gvpe/if-up\*(C'):
#!/bin/sh ip link set $IFNAME address $MAC mtu $MTU up [ $NODENAME = first ] && ip addr add 10.0.1.1 dev $IFNAME [ $NODENAME = second ] && ip addr add 10.0.2.1 dev $IFNAME [ $NODENAME = third ] && ip addr add 10.0.3.1 dev $IFNAME ip route add 10.0.0.0/16 dev $IFNAME
This script will give each node a different \s-1IP\s0 address in the \*(C`10.0/16\*(C' network. The internal network (if gvpe runs on a router) should then be set to a subset of that network, e.g. \*(C`10.0.1.0/24\*(C' on node \*(C`first\*(C', \*(C`10.0.2.0/24\*(C' on node \*(C`second\*(C', and so on.
By enabling routing on the gateway host that runs \*(C`gvpe\*(C' all nodes will be able to reach the other nodes. You can, of course, also use proxy \s-1ARP\s0 or other means of pseudo-bridging, or (best) full routing - the choice is yours.
Run the following command to generate all key pairs for all nodes (that might take a while):
gvpectrl -c /etc/gvpe -g
This command will put the public keys into \*(C`/etc/gvpe/pubkeys/nodename\*(C' and the private keys into \*(C`/etc/gvpe/hostkeys/nodename\*(C'.
Now distribute the config files and private keys to the other nodes. This should be done in two steps, since only the private keys meant for a node should be distributed (so each node has only it's own private key).
The example uses rsync-over-ssh
First all the config files without the hostkeys should be distributed:
rsync -avzessh /etc/gvpe first.example.net:/etc/. --exclude hostkeys rsync -avzessh /etc/gvpe 188.8.131.52:/etc/. --exclude hostkeys rsync -avzessh /etc/gvpe third.example.net:/etc/. --exclude hostkeys
Then the hostkeys should be copied:
rsync -avzessh /etc/gvpe/hostkeys/first first.example.net:/etc/hostkey rsync -avzessh /etc/gvpe/hostkeys/second 184.108.40.206:/etc/hostkey rsync -avzessh /etc/gvpe/hostkeys/third third.example.net:/etc/hostkey
You should now check the configuration by issuing the command \*(C`gvpectrl -c /etc/gvpe -s\*(C' on each node and verify it's output.
You should then start gvpe on each node by issuing a command like:
gvpe -D -l info first # first is the nodename
This will make the gvpe daemon stay in foreground. You should then see \*(L"connection established\*(R" messages. If you don't see them check your firewall and routing (use tcpdump ;).
If this works you should check your networking setup by pinging various endpoints.
To make gvpe run more permanently you can either run it as a daemon (by starting it without the \*(C`-D\*(C' switch), or, much better, from your inittab or equivalent. I use a line like this on all my systems:
t1:2345:respawn:/opt/gvpe/sbin/gvpe -D -L first >/dev/null 2>&1
... and play around. Sending a -HUP (\*(C`gvpectrl -kHUP\*(C') to the daemon will make it try to connect to all other nodes again. If you run it from inittab, as is recommended, \*(C`gvpectrl -k\*(C' (or simply \*(C`killall gvpe\*(C') will kill the daemon, start it again, making it read it's configuration files again.
gvpe.osdep\|(5) for OS-dependent information, gvpe.conf\|(5), gvpectrl\|(8), and for a description of the transports, protocol, and routing algorithm, gvpe.protocol\|(7).
The \s-1GVPE\s0 mailing list, at <http://lists.schmorp.de/>, or \*(C`[email protected]\*(C'.
Marc Lehmann <[email protected]>
\s-1GVPE\s0 itself is distributed under the \s-1GENERAL\s0 \s-1PUBLIC\s0 \s-1LICENSE\s0 (see the file \s-1COPYING\s0 that should be part of your distribution).
In some configurations it uses modified versions of the tinc vpn suite, which is also available under the \s-1GENERAL\s0 \s-1PUBLIC\s0 \s-1LICENSE\s0.