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.10 by pcg, Mon Sep 1 05:31:28 2008 UTC

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

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines