… | |
… | |
8 | [B<--kill>[B<=>I<SIGNAL>]] [B<--mlock>] [B<--help>] [B<--version>] |
8 | [B<--kill>[B<=>I<SIGNAL>]] [B<--mlock>] [B<--help>] [B<--version>] |
9 | I<NODENAME> [I<option...>] |
9 | I<NODENAME> [I<option...>] |
10 | |
10 | |
11 | =head1 DESCRIPTION |
11 | =head1 DESCRIPTION |
12 | |
12 | |
13 | See the gvpe(5) manpage for an introduction to the gvpe suite. |
13 | See the gvpe(5) man page for an introduction to the gvpe suite. |
14 | |
14 | |
15 | This is the manual page for gvpe, the virtual private ethernet daemon. |
15 | This is the manual page for gvpe, the virtual private ethernet daemon. |
16 | When started, C<gvpe> will read it's configuration file to determine the |
16 | When started, C<gvpe> will read it's configuration file to determine the |
17 | network topology, and other configuration information, assuming the role |
17 | network topology, and other configuration information, assuming the role |
18 | of node I<NODENAME>. It will then connect to the tun/tap device and set |
18 | of node I<NODENAME> |
|
|
19 | |
|
|
20 | It will then create/connect to the tun/tap device and set up a socket for |
19 | up a socket for incoming connections. Then a script will be executed to |
21 | incoming connections. Then a C<if-up> script will be executed to further |
20 | further configure the virtual device. If that succeeds, it will detach |
22 | configure the virtual network device. If that succeeds, it will detach |
21 | from the controlling terminal and continue in the background, accepting |
23 | from the controlling terminal and continue in the background, accepting |
22 | and setting up connections to other gvpe daemons that are part of the |
24 | and setting up connections to other gvpe daemons that are part of the |
23 | virtual private ethernet. |
25 | same virtual private ethernet. |
24 | |
26 | |
25 | The optional arguments after the node name have to be of the form: |
27 | The optional arguments after the node name have to be of the form: |
26 | |
28 | |
27 | [I<nodename>.]var=value |
29 | [I<nodename>.]var=value |
28 | |
30 | |
29 | If the argument has a prefix of C<nodename.> |
31 | If the argument has a prefix of C<nodename.> |
30 | (i.e. C<laptop.enable-dns=yes>) then it will be parsed after all the |
32 | (i.e. C<laptop.enable-dns=yes>) then it will be parsed after all the |
31 | config directives for that node, if not, it is parsed befroe the first |
33 | config directives for that node, if not, it is parsed before the first |
32 | node directive in the config file, and can be used to set global options |
34 | node directive in the config file, and can be used to set global options |
33 | or default variables. |
35 | or default variables. |
34 | |
36 | |
35 | For example, to start C<gvpe> in the foreground, with log-level C<info> on |
37 | For example, to start C<gvpe> in the foreground, with log-level C<info> on |
36 | the node C<laptop>, with TCP enabled and HTTP-Proxy host and Port set, use |
38 | the node C<laptop>, with TCP enabled and HTTP-Proxy host and Port set, use |
… | |
… | |
62 | Don't fork and detach but stay in foreground and log messages to stderr in |
64 | Don't fork and detach but stay in foreground and log messages to stderr in |
63 | addition to syslog. |
65 | addition to syslog. |
64 | |
66 | |
65 | =item B<-L>, B<--mlock> |
67 | =item B<-L>, B<--mlock> |
66 | |
68 | |
67 | Lock C<gvpe> into main memory. This will prevent sensitive data like |
69 | Lock C<gvpe> into main memory. This will prevent sensitive data like |
68 | shared private keys to be written to the system swap files/partitions. |
70 | shared private keys to be written to the system swap files/partitions. |
69 | |
71 | |
70 | =item B<--version> |
72 | =item B<--version> |
71 | |
73 | |
72 | Output version information and exit. |
74 | Output version information and exit. |
… | |
… | |
131 | =head1 BUGS |
133 | =head1 BUGS |
132 | |
134 | |
133 | The cryptography in gvpe has not been thoroughly checked by many people |
135 | The cryptography in gvpe has not been thoroughly checked by many people |
134 | yet. Use it at your own risk! |
136 | yet. Use it at your own risk! |
135 | |
137 | |
136 | If you find any bugs, report them to C<gvpe@plan9.de>. |
138 | If you find any bugs, report them to C<gvpe@schmorp.de>. |
137 | |
139 | |
138 | =head1 SEE ALSO |
140 | =head1 SEE ALSO |
139 | |
141 | |
140 | gvpe(5) for an introduction, gvpe.conf(5), gvpectrl(8). |
142 | gvpe(5) for an introduction, gvpe.conf(5), gvpectrl(8). |
141 | |
143 | |
142 | The GVPE mailing list, at L<http://lists.schmorp.de/> or |
144 | The GVPE mailing list, at L<http://lists.schmorp.de/> or |
143 | C<gvpe@lists.schmorp.de>. |
145 | C<gvpe@lists.schmorp.de>. |
144 | |
146 | |
145 | gvpe comes with ABSOLUTELY NO WARRANTY. This is free software, and you are |
147 | GVPE comes with ABSOLUTELY NO WARRANTY. This is free software, and you are |
146 | welcome to redistribute it under certain conditions; see the file COPYING |
148 | welcome to redistribute it under certain conditions; see the file COPYING |
147 | for details. |
149 | for details. |
148 | |
150 | |
149 | =head1 AUTHOR |
151 | =head1 AUTHOR |
150 | |
152 | |
151 | Marc Lehmann C<< <gvpe@plan9.de> >>. |
153 | Marc Lehmann C<< <gvpe@schmorp.de> >>. |
152 | |
154 | |
153 | And thanks to many others for their contributions to gvpe, especially the |
155 | And thanks to many others for their contributions to gvpe, especially the |
154 | tincd authors, who inspired me to write this program (after scavenging |
156 | tincd authors, who inspired me to write this program (after scavenging |
155 | their sourcecode ;). |
157 | their source code ;). |
156 | |
158 | |