ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/doc/gvpe.5
(Generate patch)

Comparing gvpe/doc/gvpe.5 (file contents):
Revision 1.3 by pcg, Thu Jan 27 06:58:48 2005 UTC vs.
Revision 1.12 by root, Sat Jul 13 04:10:29 2013 UTC

1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 1.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.20)
2.\" 2.\"
3.\" Standard preamble: 3.\" Standard preamble:
4.\" ======================================================================== 4.\" ========================================================================
5.de Sh \" Subsection heading
6.br
7.if t .Sp
8.ne 5
9.PP
10\fB\\$1\fR
11.PP
12..
13.de Sp \" Vertical space (when we can't use .PP) 5.de Sp \" Vertical space (when we can't use .PP)
14.if t .sp .5v 6.if t .sp .5v
15.if n .sp 7.if n .sp
16.. 8..
17.de Vb \" Begin verbatim text 9.de Vb \" Begin verbatim text
23.ft R 15.ft R
24.fi 16.fi
25.. 17..
26.\" Set up some character translations and predefined strings. \*(-- will 18.\" Set up some character translations and predefined strings. \*(-- will
27.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left 19.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
28.\" double quote, and \*(R" will give a right double quote. | will give a 20.\" double quote, and \*(R" will give a right double quote. \*(C+ will
29.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to 21.\" give a nicer C++. Capital omega is used to do unbreakable dashes and
30.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C' 22.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
31.\" expand to `' in nroff, nothing in troff, for use with C<>. 23.\" nothing in troff, for use with C<>.
32.tr \(*W-|\(bv\*(Tr 24.tr \(*W-
33.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' 25.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
34.ie n \{\ 26.ie n \{\
35. ds -- \(*W- 27. ds -- \(*W-
36. ds PI pi 28. ds PI pi
37. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch 29. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
46. ds PI \(*p 38. ds PI \(*p
47. ds L" `` 39. ds L" ``
48. ds R" '' 40. ds R" ''
49'br\} 41'br\}
50.\" 42.\"
43.\" Escape single quotes in literal strings from groff's Unicode transform.
44.ie \n(.g .ds Aq \(aq
45.el .ds Aq '
46.\"
51.\" If the F register is turned on, we'll generate index entries on stderr for 47.\" If the F register is turned on, we'll generate index entries on stderr for
52.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index 48.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
53.\" entries marked with X<> in POD. Of course, you'll have to process the 49.\" entries marked with X<> in POD. Of course, you'll have to process the
54.\" output yourself in some meaningful fashion. 50.\" output yourself in some meaningful fashion.
55.if \nF \{\ 51.ie \nF \{\
56. de IX 52. de IX
57. tm Index:\\$1\t\\n%\t"\\$2" 53. tm Index:\\$1\t\\n%\t"\\$2"
58.. 54..
59. nr % 0 55. nr % 0
60. rr F 56. rr F
61.\} 57.\}
62.\" 58.el \{\
63.\" For nroff, turn off justification. Always turn off hyphenation; it makes 59. de IX
64.\" way too many mistakes in technical documents. 60..
65.hy 0 61.\}
66.if n .na
67.\" 62.\"
68.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). 63.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
69.\" Fear. Run. Save yourself. No user-serviceable parts. 64.\" Fear. Run. Save yourself. No user-serviceable parts.
70. \" fudge factors for nroff and troff 65. \" fudge factors for nroff and troff
71.if n \{\ 66.if n \{\
127.\} 122.\}
128.rm #[ #] #H #V #F C 123.rm #[ #] #H #V #F C
129.\" ======================================================================== 124.\" ========================================================================
130.\" 125.\"
131.IX Title "GVPE 5" 126.IX Title "GVPE 5"
132.TH GVPE 5 "2005-01-27" "1.7" "GNU Virtual Private Ethernet" 127.TH GVPE 5 "2013-07-10" "2.24" "GNU Virtual Private Ethernet"
128.\" For nroff, turn off justification. Always turn off hyphenation; it makes
129.\" way too many mistakes in technical documents.
130.if n .ad l
131.nh
133.SH "NAME" 132.SH "NAME"
134GNU\-VPE \- Overview of the GNU Virtual Private Ethernet suite. 133GNU\-VPE \- Overview of the GNU Virtual Private Ethernet suite.
135.SH "DESCRIPTION" 134.SH "DESCRIPTION"
136.IX Header "DESCRIPTION" 135.IX Header "DESCRIPTION"
137\&\s-1GVPE\s0 is a suite designed to provide a virtual private network for multiple 136\&\s-1GVPE\s0 is a suite designed to provide a virtual private network for multiple
138nodes over an untrusted network. 137nodes over an untrusted network. This document first gives an introduction
139.IP "\(bu" 4 138to VPNs in general and then describes the specific implementation of \s-1GVPE\s0.
139.SS "\s-1WHAT\s0 \s-1IS\s0 A \s-1VPN\s0?"
140.IX Subsection "WHAT IS A VPN?"
141\&\s-1VPN\s0 is an acronym, it stands for:
142.IP "Virtual" 4
140.IX Xref "Virtual" 143.IX Item "Virtual"
141Virtual means that no physical network is created (of course), but an 144Virtual means that no physical network is created (of course), but a
142ethernet is emulated by creating multiple tunnels between the member 145network is \fIemulated\fR by creating multiple tunnels between the member
146nodes by encapsulating and sending data over another transport network.
147.Sp
148Usually the emulated network is a normal \s-1IP\s0 or Ethernet, and the transport
149network is the Internet. However, using a \s-1VPN\s0 system like \s-1GVPE\s0 to connect
150nodes over other untrusted networks such as Wireless \s-1LAN\s0 is not uncommon.
151.IP "Private" 4
152.IX Item "Private"
153Private means that non-participating nodes cannot decode (\*(L"sniff)\*(R" nor
154inject (\*(L"spoof\*(R") packets. This means that nodes can be connected over
155untrusted networks such as the public Internet without fear of being
156eavesdropped while at the same time being able to trust data sent by other
143nodes. 157nodes.
144.IP "\(bu" 4
145.IX Xref "Private"
146Private means that non-participating nodes cannot decode (\*(L"sniff)\*(R" nor
147inject (\*(L"spoof\*(R") packets.
148.Sp 158.Sp
149In the case of gvpe, even participating nodes cannot sniff packets send to 159In the case of \s-1GVPE\s0, even participating nodes cannot sniff packets
150other nodes or spoof packets as if sent from other nodes. 160send to other nodes or spoof packets as if sent from other nodes, so
151.IP "\(bu" 4 161communications between any two nodes is private to those two nodes.
162.IP "Network" 4
152.IX Xref "Network" 163.IX Item "Network"
153Network means that more than two parties can participate in the network, 164Network means that more than two parties can participate in the network,
154so for instance it's possible to connect multiple branches of a company 165so for instance it's possible to connect multiple branches of a company
155into a single network. Many so-called \*(L"vpn\*(R" solutions only create 166into a single network. Many so-called \*(L"\s-1VPN\s0\*(R" solutions only create
156point-to-point tunnels. 167point-to-point tunnels, which in turn can be used to build larger
168networks.
169.Sp
170\&\s-1GVPE\s0 provides a true multi-point network in which any number of nodes (at
171least a few dozen in practise, the theoretical limit is 4095 nodes) can
172participate.
157.Sh "\s-1DESIGN\s0 \s-1GOALS\s0" 173.SS "\s-1GVPE\s0 \s-1DESIGN\s0 \s-1GOALS\s0"
158.IX Subsection "DESIGN GOALS" 174.IX Subsection "GVPE DESIGN GOALS"
159.IP "\s-1SIMPLE\s0 \s-1DESIGN\s0" 4 175.IP "\s-1SIMPLE\s0 \s-1DESIGN\s0" 4
160.IX Item "SIMPLE DESIGN" 176.IX Item "SIMPLE DESIGN"
161Cipher, \s-1HMAC\s0 algorithms and other key parameters must be selected 177Cipher, \s-1HMAC\s0 algorithms and other key parameters must be selected
162at compile time \- this makes it possible to only link in algorithms 178at compile time \- this makes it possible to only link in algorithms
163you actually need. It also makes the crypto part of the source very 179you actually need. It also makes the crypto part of the source very
164transparent and easy to inspect. 180transparent and easy to inspect, and last not least this makes it possible
181to hardcode the layout of all packets into the binary. \s-1GVPE\s0 goes a step
182further and internally reserves blocks of the same length for all packets,
183which virtually removes all possibilities of buffer overflows, as there is
184only a single type of buffer and it's always of fixed length.
165.IP "\s-1EASY\s0 \s-1TO\s0 \s-1SETUP\s0" 4 185.IP "\s-1EASY\s0 \s-1TO\s0 \s-1SETUP\s0" 4
166.IX Item "EASY TO SETUP" 186.IX Item "EASY TO SETUP"
167A few lines of config (the config file is shared unmodified between all 187A few lines of config (the config file is shared unmodified between all
168hosts) and a single run of \f(CW\*(C`gvpectrl\*(C'\fR to generate the keys suffices to 188hosts) and a single run of \f(CW\*(C`gvpectrl\*(C'\fR to generate the keys suffices to
169make it work. 189make it work.
174address, e.g. to ensure that packets from a specific \s-1IP\s0 address come, in 194address, e.g. to ensure that packets from a specific \s-1IP\s0 address come, in
175fact, from a specific host that is associated with that \s-1IP\s0 and not from 195fact, from a specific host that is associated with that \s-1IP\s0 and not from
176another host. 196another host.
177.SH "PROGRAMS" 197.SH "PROGRAMS"
178.IX Header "PROGRAMS" 198.IX Header "PROGRAMS"
179Vpe comes with two programs: one daemon (\f(CW\*(C`gvpe\*(C'\fR) and one control program 199Gvpe comes with two programs: one daemon (\f(CW\*(C`gvpe\*(C'\fR) and one control program
180(\f(CW\*(C`gvpectrl\*(C'\fR). 200(\f(CW\*(C`gvpectrl\*(C'\fR).
181.IP "gvpectrl" 4 201.IP "gvpectrl" 4
182.IX Item "gvpectrl" 202.IX Item "gvpectrl"
183Is used to generate the keys, check and give an overview of of the 203This program is used to generate the keys, check and give an overview of of the
184configuration and contorl the daemon (restarting etc.). 204configuration and to control the daemon (restarting etc.).
185.IP "gvpe" 4 205.IP "gvpe" 4
186.IX Item "gvpe" 206.IX Item "gvpe"
187Is the daemon used to establish and maintain connections to the other 207This is the daemon used to establish and maintain connections to the other
188network members. It should be run on the gateway machine. 208network nodes. It should be run on the gateway of each \s-1VPN\s0 subnet.
189.SH "COMPILETIME CONFIGURATION" 209.SH "COMPILETIME CONFIGURATION"
190.IX Header "COMPILETIME CONFIGURATION" 210.IX Header "COMPILETIME CONFIGURATION"
191Please have a look at the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for platform-specific 211Please have a look at the \f(CW\*(C`gvpe.osdep(5)\*(C'\fR manpage for platform-specific
192information. 212information.
193.PP 213.PP
214Gvpe hardcodes most encryption parameters. While this reduces flexibility,
215it makes the program much simpler and helps making buffer overflows
216impossible under most circumstances.
217.PP
194Here are a few recipes for compiling your gvpe: 218Here are a few recipes for compiling your gvpe, showing the extremes
219(fast, small, insecure \s-1OR\s0 slow, large, more secure), between which you
220should choose:
195.Sh "\s-1AS\s0 \s-1LOW\s0 \s-1PACKET\s0 \s-1OVERHEAD\s0 \s-1AS\s0 \s-1POSSIBLE\s0" 221.SS "\s-1AS\s0 \s-1LOW\s0 \s-1PACKET\s0 \s-1OVERHEAD\s0 \s-1AS\s0 \s-1POSSIBLE\s0"
196.IX Subsection "AS LOW PACKET OVERHEAD AS POSSIBLE" 222.IX Subsection "AS LOW PACKET OVERHEAD AS POSSIBLE"
197.Vb 1 223.Vb 1
198\& ./configure --enable-hmac-length=4 --enable-rand-length=0 224\& ./configure \-\-enable\-hmac\-length=4 \-\-enable\-rand\-length=0
199.Ve 225.Ve
200.PP 226.PP
201Minimize the header overhead of \s-1VPN\s0 packets (the above will result in only 227Minimize the header overhead of \s-1VPN\s0 packets (the above will result in
2024 bytes of overhead over the raw ethernet frame). 228only 4 bytes of overhead over the raw ethernet frame). This is a insecure
229configuration because a \s-1HMAC\s0 length of 4 makes collision attacks almost
230trivial.
203.Sh "\s-1MINIMIZE\s0 \s-1CPU\s0 \s-1TIME\s0 \s-1REQUIRED\s0" 231.SS "\s-1MINIMIZE\s0 \s-1CPU\s0 \s-1TIME\s0 \s-1REQUIRED\s0"
204.IX Subsection "MINIMIZE CPU TIME REQUIRED" 232.IX Subsection "MINIMIZE CPU TIME REQUIRED"
205.Vb 1 233.Vb 1
206\& ./configure --enable-cipher=bf --enable-digest=md4 234\& ./configure \-\-enable\-cipher=bf \-\-enable\-digest=md4
207.Ve 235.Ve
208.PP 236.PP
209Use the fastest cipher and digest algorithms currently available in gvpe. 237Use the fastest cipher and digest algorithms currently available in
238gvpe. \s-1MD4\s0 has been broken and is quite insecure, though, so using another
239digest algorithm is recommended.
210.Sh "\s-1MAXIMIZE\s0 \s-1SECURITY\s0" 240.SS "\s-1MAXIMIZE\s0 \s-1SECURITY\s0"
211.IX Subsection "MAXIMIZE SECURITY" 241.IX Subsection "MAXIMIZE SECURITY"
212.Vb 1 242.Vb 1
213\& ./configure --enable-hmac-length=16 --enable-rand-length=8 --enable-digest=sha1 243\& ./configure \-\-enable\-hmac\-length=16 \-\-enable\-rand\-length=12 \-\-enable\-digest=ripemd610
214.Ve 244.Ve
215.PP 245.PP
216This uses a 16 byte \s-1HMAC\s0 checksum to authenticate packets (I guess 8\-12 246This uses a 16 byte \s-1HMAC\s0 checksum to authenticate packets (I guess 8\-12
217would also be pretty secure ;) and will additionally prefix each packet 247would also be pretty secure ;) and will additionally prefix each packet
218with 8 bytes of random data. In the long run, people should move to 248with 12 bytes of random data.
219\&\s-1SHA\-224\s0 and beyond, but support in openssl is missing as of writing this
220document.
221.PP 249.PP
222In general, remember that \s-1AES\-128\s0 seems to be more secure and faster than 250In general, remember that \s-1AES\-128\s0 seems to be as secure but faster than
223\&\s-1AES\-192\s0 or \s-1AES\-256\s0, more randomness helps against sniffing and a longer 251\&\s-1AES\-192\s0 or \s-1AES\-256\s0, more randomness helps against sniffing and a longer
224\&\s-1HMAC\s0 helps against spoofing. \s-1MD4\s0 is a fast digest, \s-1SHA1\s0 or \s-1RIPEMD160\s0 are 252\&\s-1HMAC\s0 helps against spoofing. \s-1MD4\s0 is a fast digest, \s-1SHA1\s0, \s-1RIPEMD160\s0, \s-1SHA256\s0
225better, and Blowfish is a fast cipher (and also quite secure). 253are consecutively better, and Blowfish is a fast cipher (and also quite
254secure).
226.SH "HOW TO SET UP A SIMPLE VPN" 255.SH "HOW TO SET UP A SIMPLE VPN"
227.IX Header "HOW TO SET UP A SIMPLE VPN" 256.IX Header "HOW TO SET UP A SIMPLE VPN"
228In this section I will describe how to get a simple \s-1VPN\s0 consisting of 257In this section I will describe how to get a simple \s-1VPN\s0 consisting of
229three hosts up and running. 258three hosts up and running.
230.Sh "\s-1STEP\s0 1: configuration" 259.SS "\s-1STEP\s0 1: configuration"
231.IX Subsection "STEP 1: configuration" 260.IX Subsection "STEP 1: configuration"
232First you have to create a daemon configuation file and put it into the 261First you have to create a daemon configuration file and put it into the
233configuration directory. This is usually \f(CW\*(C`/etc/gvpe\*(C'\fR, depending on how you 262configuration directory. This is usually \f(CW\*(C`/etc/gvpe\*(C'\fR, depending on how you
234configured gvpe, and can be overwritten using the \f(CW\*(C`\-c\*(C'\fR commandline switch. 263configured gvpe, and can be overwritten using the \f(CW\*(C`\-c\*(C'\fR command line switch.
235.PP 264.PP
236Put the following lines into \f(CW\*(C`/etc/gvpe/gvpe.conf\*(C'\fR: 265Put the following lines into \f(CW\*(C`/etc/gvpe/gvpe.conf\*(C'\fR:
237.PP 266.PP
238.Vb 3 267.Vb 3
239\& udp-port = 50000 # the external port to listen on (configure your firewall) 268\& udp\-port = 50000 # the external port to listen on (configure your firewall)
240\& mtu = 1400 # minimum MTU of all outgoing interfaces on all hosts 269\& mtu = 1400 # minimum MTU of all outgoing interfaces on all hosts
241\& ifname = vpn0 # the local network device name 270\& ifname = vpn0 # the local network device name
242.Ve 271\&
243.PP
244.Vb 2
245\& node = first # just a nickname 272\& node = first # just a nickname
246\& hostname = first.example.net # the DNS name or IP address of the host 273\& hostname = first.example.net # the DNS name or IP address of the host
247.Ve 274\&
248.PP
249.Vb 2
250\& node = second 275\& node = second
251\& hostname = 133.55.82.9 276\& hostname = 133.55.82.9
252.Ve 277\&
253.PP
254.Vb 2
255\& node = third 278\& node = third
256\& hostname = third.example.net 279\& hostname = third.example.net
257.Ve 280.Ve
258.PP 281.PP
259The only other file neccessary if the \f(CW\*(C`if\-up\*(C'\fR script that initializes the 282The only other file necessary is the \f(CW\*(C`if\-up\*(C'\fR script that initializes the
260local ethernet interface. Put the following lines into \f(CW\*(C`/etc/gvpe/if\-up\*(C'\fR 283virtual ethernet interface on the local host. Put the following lines into
261and make it execute (\f(CW\*(C`chmod 755 /etc/gvpe/if\-up\*(C'\fR): 284\&\f(CW\*(C`/etc/gvpe/if\-up\*(C'\fR and make it executable (\f(CW\*(C`chmod 755 /etc/gvpe/if\-up\*(C'\fR):
262.PP 285.PP
263.Vb 6 286.Vb 6
264\& #!/bin/sh 287\& #!/bin/sh
265\& ip link set $IFNAME address $MAC mtu $MTU up 288\& ip link set $IFNAME address $MAC mtu $MTU up
266\& [ $NODENAME = first ] && ip addr add 10.0.1.1 dev $IFNAME 289\& [ $NODENAME = first ] && ip addr add 10.0.1.1 dev $IFNAME
268\& [ $NODENAME = third ] && ip addr add 10.0.3.1 dev $IFNAME 291\& [ $NODENAME = third ] && ip addr add 10.0.3.1 dev $IFNAME
269\& ip route add 10.0.0.0/16 dev $IFNAME 292\& ip route add 10.0.0.0/16 dev $IFNAME
270.Ve 293.Ve
271.PP 294.PP
272This script will give each node a different \s-1IP\s0 address in the \f(CW\*(C`10.0/16\*(C'\fR 295This script will give each node a different \s-1IP\s0 address in the \f(CW\*(C`10.0/16\*(C'\fR
273network. The internal network (e.g. the \f(CW\*(C`eth0\*(C'\fR interface) should then be 296network. The internal network (if gvpe runs on a router) should then be
274set to a subset of that network, e.g. \f(CW\*(C`10.0.1.0/24\*(C'\fR on node \f(CW\*(C`first\*(C'\fR, 297set to a subset of that network, e.g. \f(CW\*(C`10.0.1.0/24\*(C'\fR on node \f(CW\*(C`first\*(C'\fR,
275\&\f(CW\*(C`10.0.2.0/24\*(C'\fR on node \f(CW\*(C`second\*(C'\fR, and so on. 298\&\f(CW\*(C`10.0.2.0/24\*(C'\fR on node \f(CW\*(C`second\*(C'\fR, and so on.
276.PP 299.PP
277By enabling routing on the gateway host that runs \f(CW\*(C`gvpe\*(C'\fR all nodes will 300By enabling routing on the gateway host that runs \f(CW\*(C`gvpe\*(C'\fR all nodes will
278be able to reach the other nodes. You can, of course, also use proxy arp 301be able to reach the other nodes. You can, of course, also use proxy \s-1ARP\s0
279or other means of pseudo-bridging (or even real briding), or (best) full 302or other means of pseudo-bridging, or (best) full routing \- the choice is
280routing \- the choice is yours. 303yours.
281.Sh "\s-1STEP\s0 2: create the \s-1RSA\s0 key pairs for all hosts" 304.SS "\s-1STEP\s0 2: create the \s-1RSA\s0 key pairs for all hosts"
282.IX Subsection "STEP 2: create the RSA key pairs for all hosts" 305.IX Subsection "STEP 2: create the RSA key pairs for all hosts"
283Run the following command to generate all key pairs (that might take a 306Run the following command to generate all key pairs for all nodes (that
284while): 307might take a while):
285.PP 308.PP
286.Vb 1 309.Vb 1
287\& gvpectrl -c /etc/gvpe -g 310\& gvpectrl \-c /etc/gvpe \-g
288.Ve 311.Ve
289.PP 312.PP
290This command will put the public keys into \f(CW\*(C`/etc/gvpe/pubkeys/\f(CInodename\f(CW\*(C'\fR and the private keys into \f(CW\*(C`/etc/gvpe/hostkeys/\f(CInodename\f(CW\*(C'\fR. 313This command will put the public keys into \f(CW\*(C`/etc/gvpe/pubkeys/\f(CInodename\f(CW\*(C'\fR and the private keys into \f(CW\*(C`/etc/gvpe/hostkeys/\f(CInodename\f(CW\*(C'\fR.
291.Sh "\s-1STEP\s0 3: distribute the config files to all nodes" 314.SS "\s-1STEP\s0 3: distribute the config files to all nodes"
292.IX Subsection "STEP 3: distribute the config files to all nodes" 315.IX Subsection "STEP 3: distribute the config files to all nodes"
293Now distribute the config files to the other nodes. This should be done in two steps, since the 316Now distribute the config files and private keys to the other nodes. This
294private keys should not be distributed. The example uses rsync-over-ssh 317should be done in two steps, since only the private keys meant for a node
318should be distributed (so each node has only it's own private key).
319.PP
320The example uses rsync-over-ssh
295.PP 321.PP
296First all the config files without the hostkeys should be distributed: 322First all the config files without the hostkeys should be distributed:
297.PP 323.PP
298.Vb 3 324.Vb 3
299\& rsync -avzessh /etc/gvpe first.example.net:/etc/. --exclude hostkeys 325\& rsync \-avzessh /etc/gvpe first.example.net:/etc/. \-\-exclude hostkeys
300\& rsync -avzessh /etc/gvpe 133.55.82.9:/etc/. --exclude hostkeys 326\& rsync \-avzessh /etc/gvpe 133.55.82.9:/etc/. \-\-exclude hostkeys
301\& rsync -avzessh /etc/gvpe third.example.net:/etc/. --exclude hostkeys 327\& rsync \-avzessh /etc/gvpe third.example.net:/etc/. \-\-exclude hostkeys
302.Ve 328.Ve
303.PP 329.PP
304Then the hostkeys should be copied: 330Then the hostkeys should be copied:
305.PP 331.PP
306.Vb 3 332.Vb 3
307\& rsync -avzessh /etc/gvpe/hostkeys/first first.example.net:/etc/hostkey 333\& rsync \-avzessh /etc/gvpe/hostkeys/first first.example.net:/etc/hostkey
308\& rsync -avzessh /etc/gvpe/hostkeys/second 133.55.82.9:/etc/hostkey 334\& rsync \-avzessh /etc/gvpe/hostkeys/second 133.55.82.9:/etc/hostkey
309\& rsync -avzessh /etc/gvpe/hostkeys/third third.example.net:/etc/hostkey 335\& rsync \-avzessh /etc/gvpe/hostkeys/third third.example.net:/etc/hostkey
310.Ve 336.Ve
311.PP 337.PP
312You should now check the configration by issuing the command \f(CW\*(C`gvpectrl \-c 338You should now check the configuration by issuing the command \f(CW\*(C`gvpectrl \-c
313/etc/gvpe \-s\*(C'\fR on each node and verify it's output. 339/etc/gvpe \-s\*(C'\fR on each node and verify it's output.
314.Sh "\s-1STEP\s0 4: starting gvpe" 340.SS "\s-1STEP\s0 4: starting gvpe"
315.IX Subsection "STEP 4: starting gvpe" 341.IX Subsection "STEP 4: starting gvpe"
316You should then start gvpe on each node by issuing a command like: 342You should then start gvpe on each node by issuing a command like:
317.PP 343.PP
318.Vb 1 344.Vb 1
319\& gvpe -D -linfo first # first is the nodename 345\& gvpe \-D \-l info first # first is the nodename
320.Ve 346.Ve
321.PP 347.PP
322This will make the gvpe stay in foreground. You should then see 348This will make the gvpe daemon stay in foreground. You should then see
323\&\*(L"connection established\*(R" messages. If you don't see them check your 349\&\*(L"connection established\*(R" messages. If you don't see them check your
324firewall and routing (use tcpdump ;). 350firewall and routing (use tcpdump ;).
325.PP 351.PP
326If this works you should check your networking setup by pinging various 352If this works you should check your networking setup by pinging various
327endpoints. 353endpoints.
328.PP 354.PP
329To make gvpe run more permanently you can either run it as a daemon 355To make gvpe run more permanently you can either run it as a daemon (by
330(by starting it without the \f(CW\*(C`\-D\*(C'\fR switch), or, much better, from your 356starting it without the \f(CW\*(C`\-D\*(C'\fR switch), or, much better, from your inittab
331inittab. I use a line like this on my systems: 357or equivalent. I use a line like this on all my systems:
332.PP 358.PP
333.Vb 1 359.Vb 1
334\& t1:2345:respawn:/opt/gvpe/sbin/gvpe -D -L first >/dev/null 2>&1 360\& t1:2345:respawn:/opt/gvpe/sbin/gvpe \-D \-L first >/dev/null 2>&1
335.Ve 361.Ve
336.Sh "\s-1STEP\s0 5: enjoy" 362.SS "\s-1STEP\s0 5: enjoy"
337.IX Subsection "STEP 5: enjoy" 363.IX Subsection "STEP 5: enjoy"
338\&... and play around. Sending a \-HUP (\f(CW\*(C`gvpectrl \-kHUP\*(C'\fR) to the daemon 364\&... and play around. Sending a \-HUP (\f(CW\*(C`gvpectrl \-kHUP\*(C'\fR) to the daemon
339will make it try to connect to all other nodes again. If you run it from 365will make it try to connect to all other nodes again. If you run it from
340inittab, as is recommended, \f(CW\*(C`gvpectrl \-k\*(C'\fR (or simply \f(CW\*(C`killall gvpe\*(C'\fR) will 366inittab, as is recommended, \f(CW\*(C`gvpectrl \-k\*(C'\fR (or simply \f(CW\*(C`killall gvpe\*(C'\fR) will
341kill the daemon, start it again, making it read it's configuration files 367kill the daemon, start it again, making it read it's configuration files
342again. 368again.
343.SH "SEE ALSO" 369.SH "SEE ALSO"
344.IX Header "SEE ALSO" 370.IX Header "SEE ALSO"
345\&\fIgvpe.osdep\fR\|(5) for OS-depedendent information, \fIgvpe.conf\fR\|(5), \fIgvpectrl\fR\|(8), and 371\&\fIgvpe.osdep\fR\|(5) for OS-dependent information, \fIgvpe.conf\fR\|(5), \fIgvpectrl\fR\|(8),
346for a description of the protocol and routing algorithms, \fIgvpe.protocol\fR\|(7). 372and for a description of the transports, protocol, and routing algorithm,
373\&\fIgvpe.protocol\fR\|(7).
374.PP
375The \s-1GVPE\s0 mailing list, at <http://lists.schmorp.de/>, or
376\&\f(CW\*(C`gvpe@lists.schmorp.de\*(C'\fR.
347.SH "AUTHOR" 377.SH "AUTHOR"
348.IX Header "AUTHOR" 378.IX Header "AUTHOR"
349Marc Lehmann <gvpe@plan9.de> 379Marc Lehmann <gvpe@schmorp.de>
350.SH "COPYRIGHTS AND LICENSES" 380.SH "COPYRIGHTS AND LICENSES"
351.IX Header "COPYRIGHTS AND LICENSES" 381.IX Header "COPYRIGHTS AND LICENSES"
352\&\s-1GVPE\s0 itself is distributed under the \s-1GENERAL\s0 \s-1PUBLIC\s0 \s-1LICENSE\s0 (see the file 382\&\s-1GVPE\s0 itself is distributed under the \s-1GENERAL\s0 \s-1PUBLIC\s0 \s-1LICENSE\s0 (see the file
353\&\s-1COPYING\s0 that should be part of your distribution). 383\&\s-1COPYING\s0 that should be part of your distribution).
354.PP 384.PP

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines