Commit | Line | Data |
---|---|---|
d6623498 | 1 | .\" -*-nroff-*- |
fc916a09 MW |
2 | .\". |
3 | .\" Manual for the administration protocol | |
4 | .\" | |
5 | .\" (c) 2008 Straylight/Edgeware | |
060ca767 | 6 | .\" |
13a55605 | 7 | . |
fc916a09 MW |
8 | .\"----- Licensing notice --------------------------------------------------- |
9 | .\" | |
10 | .\" This file is part of Trivial IP Encryption (TrIPE). | |
11 | .\" | |
11ad66c2 MW |
12 | .\" TrIPE is free software: you can redistribute it and/or modify it under |
13 | .\" the terms of the GNU General Public License as published by the Free | |
14 | .\" Software Foundation; either version 3 of the License, or (at your | |
15 | .\" option) any later version. | |
fc916a09 | 16 | .\" |
11ad66c2 MW |
17 | .\" TrIPE is distributed in the hope that it will be useful, but WITHOUT |
18 | .\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or | |
19 | .\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License | |
20 | .\" for more details. | |
fc916a09 MW |
21 | .\" |
22 | .\" You should have received a copy of the GNU General Public License | |
11ad66c2 | 23 | .\" along with TrIPE. If not, see <https://www.gnu.org/licenses/>. |
fc916a09 MW |
24 | . |
25 | .\"-------------------------------------------------------------------------- | |
e99aedcf | 26 | .so ../common/defs.man \" @@@PRE@@@ |
fc916a09 MW |
27 | . |
28 | .\"-------------------------------------------------------------------------- | |
0647ba7c | 29 | .TH tripe-admin 5tripe "18 February 2001" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption" |
fc916a09 MW |
30 | . |
31 | .\"-------------------------------------------------------------------------- | |
32 | .SH "NAME" | |
33 | . | |
d6623498 | 34 | tripe-admin \- administrator commands for TrIPE |
fc916a09 MW |
35 | . |
36 | .\"-------------------------------------------------------------------------- | |
37 | .SH "DESCRIPTION" | |
38 | . | |
d6623498 | 39 | This manual page describes the administration interface provided by the |
40 | .BR tripe (8) | |
41 | daemon. | |
42 | .PP | |
43 | The | |
44 | .BR tripectl (8) | |
45 | program can be used either interactively or in scripts to communicate | |
46 | with the server using this interface. Alternatively, simple custom | |
47 | clients can be written in scripting languages such as Perl, Python or | |
48 | Tcl, or more advanced clients such as GUI monitors can be written in C | |
49 | with little difficulty. | |
50 | .PP | |
37941236 | 51 | Administration commands use a textual protocol. Each client command or |
52 | server response consists of a line of ASCII text terminated by a single | |
53 | linefeed character. No command may be longer than 255 characters. | |
d6623498 | 54 | .SS "General structure" |
55 | Each command or response line consists of a sequence of | |
83487ded MW |
56 | whitespace-separated tokens. The number and nature of whitespace |
57 | characters separating two tokens in a client command is not significant; | |
58 | the server always uses a single space character. The first token in a | |
d6623498 | 59 | line is a |
60 | .I keyword | |
61 | identifying the type of command or response contained. Keywords in | |
62 | client commands are not case-sensitive; the server always uses uppercase | |
63 | for its keywords. | |
83487ded MW |
64 | .PP |
65 | In order to allow tokens to contain internal whitespace, a quoting | |
66 | mechanism is provided. Whitespace within matched pairs of quotes \(en | |
67 | either single | |
68 | .RB ` ' ' | |
69 | or double | |
70 | .RB ` """" ' | |
71 | \(en is considered to be internal. Any character (other than newline) | |
72 | may be escaped by preceding it with a backslash | |
73 | .RB ` \e ': | |
74 | in particular, this can be used to include quote characters. It is | |
75 | impossible for a token to contain a newline character. | |
76 | .PP | |
77 | On output, the server will use double quotes when necessary. | |
de014da6 | 78 | .SS "Simple commands" |
79 | For simple client command, the server responds with zero or more | |
d6623498 | 80 | .B INFO |
81 | lines, followed by either an | |
82 | .B OK | |
83 | line or a | |
84 | .B FAIL | |
85 | line. Each | |
86 | .B INFO | |
87 | provides information requested in the command. An | |
88 | .B OK | |
89 | response contains no further data. A | |
90 | .B FAIL | |
3cdc3f3a | 91 | code is followed by a machine-readable explanation of why the command |
d6623498 | 92 | failed. |
93 | .PP | |
de014da6 | 94 | Simple command processing is strictly synchronous: the server reads a |
95 | command, processes it, and responds, before reading the next command. | |
96 | All commands can be run as simple commands. Long-running commands | |
97 | (e.g., | |
98 | .B ADD | |
99 | and | |
100 | .BR PING ) | |
101 | block the client until they finish, but the rest of the server continues | |
bdc44f5b MW |
102 | running. See |
103 | .B "Background commands" | |
104 | to find out how to issue long-running commands without blocking. | |
105 | .SS "Asynchronous broadcasts" | |
106 | There are three types of asynchronous broadcast messages which aren't | |
107 | associated with any particular command. Clients can select which | |
108 | broadcast messages they're interested in using the | |
109 | .B WATCH | |
110 | command. | |
de014da6 | 111 | .PP |
112 | The | |
d6623498 | 113 | .B WARN |
3cdc3f3a | 114 | message contains a machine-readable message warning of an error |
d6623498 | 115 | encountered while processing a command, unexpected or unusual behaviour |
116 | by a peer, or a possible attack by an adversary. Under normal | |
de014da6 | 117 | conditions, the server shouldn't emit any warnings. |
118 | .PP | |
119 | The | |
d6623498 | 120 | .B TRACE |
3cdc3f3a | 121 | message contains a human-readable tracing message containing diagnostic |
d6623498 | 122 | information. Trace messages are controlled using the |
123 | .B \-T | |
124 | command-line option to the server, or the | |
125 | .B TRACE | |
126 | administration command (see below). Support for tracing can be disabled | |
127 | when the package is being configured, and may not be available in your | |
de014da6 | 128 | version. |
129 | .PP | |
130 | Finally, the | |
3cdc3f3a | 131 | .B NOTE |
132 | message is a machine-readable notification about some routine but | |
133 | interesting event such as creation or destruction of peers. | |
de014da6 | 134 | .SS "Background commands" |
135 | Some commands (e.g., | |
136 | .B ADD | |
137 | and | |
138 | .BR PING ) | |
139 | take a long time to complete. To prevent these long-running commands | |
140 | from tying up a server connection, they can be run in the background. | |
141 | Not all commands can be run like this: the ones that can provide a | |
142 | .B \-background | |
143 | option, which must be supplied with a | |
144 | .IR tag . | |
145 | .PP | |
146 | A command may fail before it starts running in the background. In this | |
147 | case, the server emits a | |
148 | .B FAIL | |
149 | response, as usual. To indicate that a command has started running in | |
150 | the background, the server emits a response of the form | |
151 | .BI "BGDETACH " tag \fR, | |
152 | where | |
153 | .I tag | |
154 | is the value passed to the | |
155 | .B \-background | |
156 | option. From this point on, the server is ready to process more | |
157 | commands and reply to them. | |
158 | .PP | |
159 | Responses to background commands are indicated by a line beginning with | |
e04c2d50 | 160 | one of the tokens |
de014da6 | 161 | .BR BGOK , |
162 | .BR BGFAIL , | |
163 | or | |
164 | .BR BGINFO , | |
e04c2d50 | 165 | followed by the command tag. These correspond to the |
de014da6 | 166 | .BR OK , |
167 | .BR FAIL , | |
168 | and | |
169 | .B INFO | |
170 | responses for simple commands: | |
171 | .B BGINFO | |
172 | indicates information from a background command which has not completed | |
173 | yet; and | |
174 | .B BGOK | |
175 | and | |
176 | .B BGFAIL | |
177 | indicates that a background command succeeded or failed, respectively. | |
178 | .PP | |
179 | A background command will never issue an | |
180 | .B OK | |
060ca767 | 181 | or |
9df937a3 | 182 | .B INFO |
060ca767 | 183 | response: it will always detach and then issue any |
184 | .B BGINFO | |
185 | lines followed by | |
de014da6 | 186 | .B BGOK |
187 | response. | |
bdc44f5b MW |
188 | .SS "Client-provided services" |
189 | .\"* 25 Service-related messages | |
190 | An administration client can provide services to other clients. | |
191 | Services are given names and versions. A client can attempt to | |
192 | .I claim | |
193 | a particular service by issuing the | |
194 | .B SVCCLAIM | |
195 | command. This may fail, for example, if some other client already | |
196 | provides the same or later version of the service. | |
197 | .PP | |
198 | Other clients can issue | |
199 | .I "service commands" | |
200 | using the | |
201 | .B "SVCSUBMIT" | |
202 | command; the service provider is expected to handle these commands and | |
203 | reply to them. | |
204 | .PP | |
205 | There are three important asynchronous messages which will be sent to | |
206 | service providers. | |
207 | .SP | |
208 | .BI "SVCCANCEL " jobid | |
209 | The named job has been cancelled, either because the issuing client has | |
210 | disconnected or explicitly cancelled the job using the | |
211 | .B BGCANCEL | |
212 | command. | |
213 | .SP | |
214 | .BI "SVCCLAIM " service " " version | |
215 | Another client has claimed a later version of the named | |
9df937a3 MW |
216 | .IR service . |
217 | The recipient is no longer the provider of this service. | |
bdc44f5b MW |
218 | .SP |
219 | .BI "SVCJOB " jobid " " service " " command " " args \fR... | |
220 | Announces the arrival of a new job. The | |
221 | .I jobid | |
222 | is a simple token consisting of alphanumeric characters which | |
223 | .B tripe | |
224 | uses to identify this job. | |
225 | .PP | |
226 | The service provider can reply to the job using the commands | |
227 | .BR SVCINFO , | |
228 | .B SVCOK | |
229 | and | |
230 | .BR SVCFAIL . | |
231 | The first of these sends an | |
232 | .B INFO | |
233 | response and leaves the job active; the other two send an | |
234 | .B OK | |
235 | or | |
236 | .B FAIL | |
237 | response respectively, and mark the job as being complete. | |
238 | .PP | |
239 | (Since | |
240 | .B SVCSUBMIT | |
241 | is a potentially long-running command, it can be run in the background. | |
242 | This detail is hidden from service providers: | |
243 | .B tripe | |
244 | will issue the corresponding | |
245 | .BR BG ... | |
246 | responses when appropriate.) | |
3cdc3f3a | 247 | .SS "Network addresses" |
83487ded | 248 | A network address is a sequence of tokens. The first is a token |
3cdc3f3a | 249 | identifying the network address family. The length of an address and |
83487ded | 250 | the meanings of the subsequent tokens depend on the address family. |
3cdc3f3a | 251 | Address family tokens are not case-sensitive on input; on output, they |
252 | are always in upper-case. | |
253 | .PP | |
254 | At present, only one address family is understood. | |
255 | .TP | |
165efde7 | 256 | .BI "INET " address " \fR[" port \fR] |
3cdc3f3a | 257 | An Internet socket, naming an IPv4 address and UDP port. On output, the |
258 | address is always in numeric dotted-quad form, and the port is given as | |
259 | a plain number. On input, DNS hostnames and symbolic port names are | |
165efde7 MW |
260 | permitted; if omitted, the default port 4070 is used. Name resolution |
261 | does not block the main server, but will block the requesting client, | |
262 | unless the command is run in the background. | |
3cdc3f3a | 263 | .PP |
78dcf842 | 264 | If, on input, no recognized address family token is found, the following |
83487ded | 265 | tokens are assumed to represent an |
3cdc3f3a | 266 | .B INET |
2acd7cd6 MW |
267 | address. Addresses output by the server always have an address family |
268 | token. | |
060ca767 | 269 | .SS "Key-value output" |
270 | Some commands (e.g., | |
271 | .B STATS | |
272 | and | |
273 | .BR SERVINFO ) | |
274 | produce output in the form of | |
275 | .IB key = value | |
83487ded | 276 | pairs, one per token. Neither the |
060ca767 | 277 | .I key |
278 | nor the | |
279 | .I value | |
280 | contain spaces. | |
281 | .SS "Trace lists" | |
282 | Commands which enable or disable kinds of output (e.g., | |
283 | .B TRACE | |
284 | and | |
285 | .BR WATCH ) | |
286 | work in similar ways. They take a single optional argument, which | |
287 | consists of a string of letters selecting message types, optionally | |
288 | interspersed with | |
289 | .RB ` + ' | |
290 | to enable, or | |
291 | .RB ` \- ' | |
292 | to disable, the subsequently listed types. | |
293 | .PP | |
294 | If the argument is omitted, the available message types are displayed, | |
295 | one to an | |
296 | .B INFO | |
297 | line, in a fixed-column format. Column zero contains the key letter for | |
298 | selecting that message type; column one contains either a space or a | |
e04c2d50 | 299 | .RB ` + ' |
060ca767 | 300 | sign, if the message type is disabled or enabled respectively; and a |
301 | textual description of the message type begins at column 3 and continues | |
302 | to the end of the line. | |
303 | .PP | |
304 | Lowercase key letters control individual message types. Uppercase key | |
305 | letters control collections of message types. | |
fc916a09 MW |
306 | . |
307 | .\"-------------------------------------------------------------------------- | |
3cdc3f3a | 308 | .SH "COMMAND REFERENCE" |
fc916a09 | 309 | . |
13a55605 | 310 | .\"* 10 Commands |
d6623498 | 311 | The commands provided are: |
13a55605 | 312 | .SP |
9986f0b5 | 313 | .BI "ADD \fR[" options "\fR] " peer " " address "\fR..." |
3cdc3f3a | 314 | Adds a new peer. The peer is given the name |
315 | .IR peer ; | |
316 | the peer's public key is assumed to be in the file | |
317 | .B keyring.pub | |
318 | (or whatever alternative file was specified in the | |
319 | .B \-K | |
320 | option on the command line). The | |
321 | .I address | |
322 | is the network address (see above for the format) at which the peer can | |
78dcf842 | 323 | be contacted. The following options are recognized. |
42da2a58 | 324 | .RS |
13a55605 | 325 | .\"+opts |
42da2a58 | 326 | .TP |
de014da6 | 327 | .BI "\-background " tag |
328 | Run the command in the background, using the given | |
329 | .IR tag . | |
330 | .TP | |
010e6f63 MW |
331 | .B "\-cork" |
332 | Don't send an immediate challenge to the peer; instead, wait until it | |
333 | sends us something before responding. | |
334 | .TP | |
0ba8de86 | 335 | .BI "\-keepalive " time |
336 | Send a no-op packet if we've not sent a packet to the peer in the last | |
337 | .I time | |
338 | interval. This is useful for persuading port-translating firewalls to | |
339 | believe that the `connection' is still active. The | |
340 | .I time | |
341 | is expressed as a nonnegative integer followed optionally by | |
342 | .BR d , | |
343 | .BR h , | |
344 | .BR m , | |
345 | or | |
346 | .BR s | |
347 | for days, hours, minutes, or seconds respectively; if no suffix is | |
348 | given, seconds are assumed. | |
349 | .TP | |
48b84569 MW |
350 | .BI "\-key " tag |
351 | Use the public key | |
352 | .I tag | |
353 | to authenticate the peer. The default is to use the key tagged | |
354 | .IR peer . | |
355 | .TP | |
8362ac1c MW |
356 | .BI "\-knock \fR[" prefix .\fR] tag |
357 | Send the string | |
358 | .RI [ prefix\fB. ] tag | |
359 | in | |
360 | .B token-rq | |
361 | and | |
362 | .B knock | |
363 | messages to the peer during key-exchange. The string as a whole should | |
364 | name the local machine to the peer, and | |
365 | .I tag | |
366 | should name its public key. When such messages are received from a | |
367 | currently unknown peer, | |
368 | .BR tripe (8) | |
369 | emits a | |
370 | .B KNOCK | |
371 | notification stating the peer's (claimed) name and address. The server | |
372 | will already have verified that the sender is using the peer's private | |
373 | key by this point. | |
374 | .TP | |
6411163d MW |
375 | .B "\-mobile" |
376 | The peer is a mobile device, and is likely to change address rapidly. | |
377 | If a packet arrives from an unknown address, the server's usual response | |
378 | is to log a warning and discard it. If the server knows of any mobile | |
379 | peers, however, it will attempt to decrypt the packet using their keys, | |
380 | and if one succeeds, the server will update its idea of the peer's | |
381 | address and emit an | |
382 | .B NEWADDR | |
383 | notification. | |
384 | .TP | |
e1f1a2a0 MW |
385 | .BI "\-priv " tag |
386 | Use the private key | |
387 | .I tag | |
388 | to authenticate to the peer. The default is to use the key named in the | |
389 | .RB ` \-t ' | |
390 | command-line option, or a key with type | |
391 | .B tripe | |
392 | or | |
393 | .BR tripe-dh : | |
394 | see | |
395 | .BR tripe (8) | |
396 | for the details. | |
397 | .TP | |
0ba8de86 | 398 | .BI "\-tunnel " tunnel |
42da2a58 | 399 | Use the named tunnel driver, rather than the default. |
13a55605 | 400 | .\"-opts |
42da2a58 | 401 | .RE |
13a55605 | 402 | .SP |
3cdc3f3a | 403 | .BI "ADDR " peer |
404 | Emits an | |
405 | .B INFO | |
406 | line reporting the IP address and port number stored for | |
407 | .IR peer . | |
13a55605 | 408 | .SP |
35c8b547 | 409 | .BI "ALGS \fR[" peer \fR] |
449991a3 | 410 | Emits information about the cryptographic algorithms in use, in |
35c8b547 MW |
411 | key-value form. If a |
412 | .I peer | |
413 | is given, then describe the algorithms used in the association with that | |
414 | peer; otherwise describe the default algorithms. | |
449991a3 | 415 | .RS |
35c8b547 MW |
416 | .PP |
417 | The keys are as follows. | |
449991a3 MW |
418 | .TP |
419 | .B kx-group | |
420 | Type of key-exchange group in use, currently either | |
421 | .B ec | |
422 | or | |
423 | .BR prime . | |
424 | .TP | |
425 | .B kx-group-order-bits | |
426 | Length of the group order, in bits. This gives an approximate measure | |
427 | of the group strength. | |
428 | .TP | |
429 | .B kx-group-elt-bits | |
430 | Length of a group element, in bits. This may be useful when analyzing | |
431 | protocol traces. | |
432 | .TP | |
433 | .B hash | |
434 | The hash function in use, e.g., | |
435 | .BR sha256 . | |
436 | .TP | |
437 | .B mgf | |
438 | The mask-generating function in use, e.g., | |
439 | .BR whirlpool-mgf . | |
440 | .TP | |
441 | .B hashsz | |
442 | The size of the hash function's output, in octets. | |
443 | .TP | |
a93aacce MW |
444 | .B bulk-transform |
445 | The name of the bulk-crypto transform. | |
446 | .TP | |
447 | .B bulk-overhead | |
448 | The amount of overhead, in bytes, caused by the crypto transform. | |
449 | .TP | |
449991a3 MW |
450 | .B cipher |
451 | The name of the bulk data cipher in use, e.g., | |
452 | .BR blowfish-cbc . | |
453 | .TP | |
454 | .B cipher-keysz | |
455 | The length of key used by the bulk data cipher, in octets. | |
456 | .TP | |
457 | .B cipher-blksz | |
458 | The block size of the bulk data cipher, or zero if it's not based on a | |
459 | block cipher. | |
460 | .TP | |
461 | .B cipher-data-limit | |
462 | The maximum amount of data to be encrypted using a single key. (A new | |
463 | key exchange is instigated well before the limit is reached, in order to | |
464 | allow for a seamless changeover of keys.) | |
465 | .TP | |
466 | .B mac | |
467 | The message authentication algorithm in use, e.g., | |
494a7ac0 | 468 | .BR ripemd160-hmac . |
449991a3 MW |
469 | .TP |
470 | .B mac-keysz | |
471 | The length of the key used by the message authentication algorithm, in | |
472 | octets. | |
473 | .TP | |
474 | .B mac-tagsz | |
475 | The length of the message authentication tag, in octets. | |
b87bffcb MW |
476 | .TP |
477 | .B blkc | |
478 | The block cipher in use, e.g., | |
479 | .BR blowfish . | |
480 | .TP | |
481 | .B blkc-keysz | |
482 | The length of key used by the block cipher, in octets. | |
483 | .TP | |
484 | .B blkc-blksz | |
485 | The block size of the block cipher. | |
449991a3 MW |
486 | .PP |
487 | The various sizes are useful, for example, when computing the MTU for a | |
488 | tunnel interface. If | |
489 | .I MTU | |
490 | is the MTU of the path to the peer, then the tunnel MTU should be | |
491 | .IP | |
492 | .I MTU | |
a93aacce MW |
493 | \- 29 \- |
494 | .I bulk-overhead | |
449991a3 MW |
495 | .PP |
496 | allowing 20 bytes of IP header, 8 bytes of UDP header, a packet type | |
a93aacce MW |
497 | octet, and the bulk-crypto transform overhead (which includes the |
498 | sequence number). | |
449991a3 MW |
499 | .RE |
500 | .SP | |
ff92ffd3 MW |
501 | .BI "BGCANCEL " tag |
502 | Cancels the background job with the named | |
503 | .IR tag . | |
504 | .SP | |
37941236 | 505 | .BI "CHECKCHAL " challenge |
506 | Verifies a challenge as being one earlier issued by | |
507 | .B GETCHAL | |
508 | and not previously either passed to | |
509 | .B CHECKCHAL | |
510 | or in a greeting message. | |
13a55605 | 511 | .SP |
3cdc3f3a | 512 | .B "DAEMON" |
513 | Causes the server to disassociate itself from its terminal and become a | |
c37b77e0 | 514 | background task. This only works once. A notification is issued. |
2acd7cd6 | 515 | .SP |
0ba8de86 | 516 | .BI "EPING \fR[" options "\fR] " peer |
517 | Sends an encrypted ping to the peer, and expects an encrypted response. | |
518 | This checks that the peer is running (and not being impersonated), and | |
519 | that it can encrypt and decrypt packets correctly. Options and | |
520 | responses are the same as for the | |
521 | .B PING | |
522 | command. | |
13a55605 | 523 | .SP |
de014da6 | 524 | .BI "FORCEKX " peer |
525 | Requests the server to begin a new key exchange with | |
526 | .I peer | |
527 | immediately. | |
13a55605 | 528 | .SP |
37941236 | 529 | .B "GETCHAL" |
530 | Requests a challenge. The challenge is returned in an | |
531 | .B INFO | |
532 | line, as a base64-encoded string. See | |
533 | .BR CHECKCHAL . | |
13a55605 | 534 | .SP |
37941236 | 535 | .BI "GREET " peer " " challenge |
536 | Sends a greeting packet containing the | |
537 | .I challenge | |
538 | (base-64 encoded) to the named | |
539 | .IR peer . | |
540 | The expectation is that this will cause the peer to recognize us and | |
541 | begin a key-exchange. | |
13a55605 | 542 | .SP |
d6623498 | 543 | .B "HELP" |
544 | Causes the server to emit an | |
545 | .B INFO | |
546 | line for each command it supports. Each line lists the command name, | |
547 | followed by the names of the arguments. This may be helpful as a memory | |
548 | aid for interactive use, or for program clients probing for features. | |
e04c2d50 | 549 | .SP |
3cdc3f3a | 550 | .BI "IFNAME " peer |
551 | Emits an | |
552 | .B INFO | |
553 | line containing the name of the network interface used to collect IP | |
554 | packets which are to be encrypted and sent to | |
555 | .IR peer . | |
556 | Used by configuration scripts so that they can set up routing tables | |
557 | appropriately after adding new peers. | |
13a55605 | 558 | .SP |
ff92ffd3 MW |
559 | .B "JOBS" |
560 | Emits an | |
561 | .B INFO | |
562 | line giving the tag for each outstanding background job. | |
563 | .SP | |
3cdc3f3a | 564 | .BI "KILL " peer |
565 | Causes the server to forget all about | |
566 | .IR peer . | |
567 | All keys are destroyed, and no more packets are sent. No notification | |
568 | is sent to the peer: if it's important that the peer be notified, you | |
569 | must think of a way to do that yourself. | |
13a55605 | 570 | .SP |
3cdc3f3a | 571 | .B "LIST" |
572 | For each currently-known peer, an | |
573 | .B INFO | |
574 | line is written containing the peer's name, as given to | |
575 | .BR ADD . | |
13a55605 | 576 | .SP |
bd58d532 | 577 | .BI "NOTIFY " tokens\fR... |
e04c2d50 | 578 | Issues a |
bd58d532 | 579 | .B USER |
580 | notification to all interested administration clients. | |
13a55605 | 581 | .SP |
060ca767 | 582 | .BI "PEERINFO " peer |
583 | Returns information about a peer, in key-value form. The following keys | |
584 | are returned. | |
585 | .RS | |
586 | .TP | |
587 | .B tunnel | |
588 | The tunnel driver used for this peer. | |
589 | .TP | |
590 | .B keepalive | |
591 | The keepalive interval, in seconds, or zero if no keepalives are to be | |
592 | sent. | |
48b84569 | 593 | .TP |
8362ac1c MW |
594 | .B knock |
595 | If present, the string sent to the peer to set up the association; see | |
596 | the | |
597 | .B \-knock | |
598 | option to | |
599 | .BR ADD , | |
600 | and the | |
601 | .B KNOCK | |
602 | notification. | |
603 | .TP | |
48b84569 | 604 | .B key |
fe2a5dcf | 605 | The (short) key tag being used for the peer, as passed to the |
48b84569 | 606 | .B ADD |
fe2a5dcf MW |
607 | command. |
608 | .TP | |
609 | .B current-key | |
610 | The full key tag of the peer's public key currently being used. This | |
611 | may change during the life of the association. | |
612 | .TP | |
613 | .B private-key | |
614 | The private key tag being used for the peer, as passed to the | |
615 | .B ADD | |
f3c6d21c MW |
616 | command, or the |
617 | .RB ` \-t ' | |
618 | command-line option. If neither of these was given explicitly, the | |
619 | private key tag is shown as | |
620 | .RB ` (default) ', | |
621 | since there is no fixed tag used under these circumstances. | |
fe2a5dcf MW |
622 | .TP |
623 | .B current-private-key | |
624 | The full key tag of the private key currently being used for this | |
625 | association. This may change during the life of the association. | |
bd322830 MW |
626 | .TP |
627 | .B corked | |
628 | Either | |
629 | .B t | |
630 | or | |
631 | .B nil | |
632 | depending on whether or not (respectively) key-exchange is waiting for | |
633 | the peer to initiate. | |
634 | .TP | |
635 | .B mobile | |
636 | Either | |
637 | .B t | |
638 | or | |
639 | .B nil | |
640 | depending on whether or not (respectively) the peer is expected to | |
641 | change its address unpredictably. | |
060ca767 | 642 | .RE |
13a55605 | 643 | .SP |
0ba8de86 | 644 | .BI "PING \fR[" options "\fR] " peer |
645 | Send a transport-level ping to the peer. The ping and its response are | |
646 | not encrypted or authenticated. This command, possibly in conjunction | |
647 | with tracing, is useful for ensuring that UDP packets are actually | |
648 | flowing in both directions. See also the | |
649 | .B EPING | |
650 | command. | |
651 | .IP | |
652 | An | |
653 | .B INFO | |
654 | line is printed describing the outcome: | |
655 | .RS | |
656 | .TP | |
657 | .BI "ping-ok " millis | |
e04c2d50 | 658 | A response was received |
0ba8de86 | 659 | .I millis |
660 | after the ping was sent. | |
661 | .TP | |
662 | .BI "ping-timeout" | |
663 | No response was received within the time allowed. | |
664 | .TP | |
665 | .BI "ping-peer-died" | |
666 | The peer was killed (probably by another admin connection) before a | |
667 | response was received. | |
668 | .RE | |
669 | .IP | |
670 | Options recognized for this command are: | |
671 | .RS | |
13a55605 | 672 | .\"+opts |
0ba8de86 | 673 | .TP |
de014da6 | 674 | .BI "\-background " tag |
675 | Run the command in the background, using the given | |
676 | .IR tag . | |
677 | .TP | |
0ba8de86 | 678 | .BI "\-timeout " time |
679 | Wait for | |
680 | .I time | |
2acd7cd6 MW |
681 | seconds before giving up on a response. The default is 5 seconds. The |
682 | .I time | |
683 | is expressed as a nonnegative integer followed optionally by | |
684 | .BR d , | |
685 | .BR h , | |
686 | .BR m , | |
687 | or | |
688 | .BR s | |
689 | for days, hours, minutes, or seconds respectively; if no suffix is | |
690 | given, seconds are assumed. | |
13a55605 | 691 | .\"-opts |
0ba8de86 | 692 | .RE |
13a55605 | 693 | .SP |
3cdc3f3a | 694 | .B "PORT" |
695 | Emits an | |
696 | .B INFO | |
697 | line containing just the number of the UDP port used by the | |
698 | .B tripe | |
699 | server. If you've allowed your server to allocate a port dynamically, | |
700 | this is how to find out which one it chose. | |
13a55605 | 701 | .SP |
de014da6 | 702 | .B "RELOAD" |
703 | Instructs the server to recheck its keyring files. The server checks | |
704 | these periodically anyway but it may be necessary to force a recheck, | |
705 | for example after adding a new peer key. | |
13a55605 | 706 | .SP |
3cdc3f3a | 707 | .B "QUIT" |
708 | Instructs the server to exit immediately. A warning is sent. | |
13a55605 | 709 | .SP |
060ca767 | 710 | .B "SERVINFO" |
711 | Returns information about the server, in the form of key-value pairs. | |
712 | The following keys are used. | |
713 | .RS | |
714 | .TP | |
715 | .B implementation | |
716 | A keyword naming the implementation of the | |
717 | .BR tripe (8) | |
718 | server. The current implementation is called | |
719 | .BR edgeware-tripe . | |
720 | .TP | |
721 | .B version | |
722 | The server's version number, as reported by | |
723 | .BR VERSION . | |
724 | .TP | |
725 | .B daemon | |
726 | Either | |
727 | .B t | |
728 | or | |
729 | .BR nil , | |
730 | if the server has or hasn't (respectively) become a daemon. | |
731 | .RE | |
13a55605 | 732 | .SP |
64cf2223 MW |
733 | .BI "SETIFNAME " peer " " new-name |
734 | Informs the server that the | |
735 | .IR peer 's | |
736 | tunnel-interface name has been changed to | |
737 | .IR new-name . | |
738 | This is useful if firewalling decisions are made based on interface | |
739 | names: a setup script for a particular peer can change the name, and | |
740 | then update the server's records so that they're accurate. | |
741 | .SP | |
405fc4da MW |
742 | .BI "STATS " peer |
743 | Emits a number of | |
744 | .B INFO | |
745 | lines, each containing one or more statistics in the form | |
746 | .IB name = value \fR. | |
747 | The statistics-gathering is experimental and subject to change. | |
748 | .SP | |
bdc44f5b MW |
749 | .BI "SVCCLAIM " service " " version |
750 | Attempts to claim the named | |
751 | .IR service , | |
752 | offering the given | |
753 | .IR version . | |
754 | The claim is successful if the service is currently unclaimed, or if | |
755 | a version earlier than | |
756 | .I version | |
757 | is provided; otherwise the command fails with the error | |
758 | .BR "service-exists" . | |
759 | .SP | |
760 | .BI "SVCENSURE " service " \fR[" version \fR] | |
e04c2d50 | 761 | Ensure that |
bdc44f5b MW |
762 | .I service |
763 | is provided, and (if specified) to at least the given | |
764 | .IR version . | |
765 | An error is reported if these conditions are not met; otherwise the | |
766 | command succeeds silently. | |
767 | .SP | |
768 | .BI "SVCFAIL " jobid " " tokens \fR... | |
769 | Send a | |
770 | .B FAIL | |
771 | (or | |
772 | .BR BGFAIL ) | |
773 | response to the service job with the given | |
774 | .IR jobid , | |
e04c2d50 | 775 | passing the |
bdc44f5b MW |
776 | .I tokens |
777 | as the reason for failure. The job is closed. | |
778 | .SP | |
779 | .BI "SVCINFO " jobid " " tokens \fR... | |
780 | Send an | |
781 | .B INFO | |
782 | (or | |
783 | .BR BGINFO ) | |
784 | response to the service job with the given | |
785 | .IR jobid , | |
786 | passing the | |
787 | .I tokens | |
788 | as the info message. The job remains open. | |
789 | .SP | |
790 | .B "SVCLIST" | |
791 | Output a line of the form | |
792 | .RS | |
793 | .IP | |
794 | .B INFO | |
795 | .I service | |
796 | .I version | |
797 | .PP | |
798 | for each service currently provided. | |
799 | .RE | |
800 | .SP | |
801 | .BI "SVCOK " jobid | |
802 | Send an | |
803 | .B OK | |
804 | (or | |
805 | .BR BGINFO ) | |
806 | response to the service job with the given | |
807 | .IR jobid . | |
808 | The job is closed. | |
809 | .SP | |
810 | .BI "SVCQUERY " service | |
811 | Emits a number of | |
812 | .B info | |
813 | lines in key-value format, describing the named | |
814 | .IR service. | |
815 | The following keys are used. | |
816 | .RS | |
817 | .TP | |
818 | .B name | |
819 | The service's name. | |
820 | .TP | |
821 | .B version | |
822 | The service's version string. | |
823 | .RE | |
824 | .SP | |
825 | .BI "SVCRELEASE " service | |
826 | Announce that the client no longer wishes to provide the named | |
827 | .IR service . | |
828 | .SP | |
829 | .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR... | |
830 | Submit a job to the provider of the given | |
831 | .IR service , | |
832 | passing it the named | |
833 | .I command | |
834 | and the given | |
835 | .IR arguments . | |
836 | The following options are accepted. | |
837 | .RS | |
838 | .\"+opts | |
839 | .TP | |
840 | .BI "\-background " tag | |
841 | Run the command in the background, using the given | |
842 | .IR tag . | |
843 | .TP | |
844 | .BI "\-version " version | |
845 | Ensure that at least the given | |
846 | .I version | |
847 | of the service is available before submitting the job. | |
848 | .RE | |
849 | .\"-opts | |
850 | .SP | |
d6623498 | 851 | .BR "TRACE " [\fIoptions\fP] |
060ca767 | 852 | Selects trace outputs: see |
e04c2d50 | 853 | .B "Trace lists" |
060ca767 | 854 | above. Message types provided are: |
d6623498 | 855 | .RS |
2d752320 | 856 | .PP |
d6623498 | 857 | Currently, the following tracing options are supported: |
858 | .TP | |
859 | .B t | |
860 | Tunnel events: reception of packets to be encrypted, and injection of | |
861 | successfully-decrypted packets. | |
862 | .TP | |
863 | .B r | |
864 | Peer management events: creation and destruction of peer attachments, | |
865 | and arrival of messages. | |
866 | .TP | |
867 | .B a | |
868 | Administration interface: acceptance of new connections, and handling of | |
869 | the backgroud name-resolution required by the | |
870 | .B ADD | |
871 | command. | |
872 | .TP | |
d6623498 | 873 | .B s |
874 | Handling of symmetric keysets: creation and expiry of keysets, and | |
875 | encryption and decryption of messages. | |
876 | .TP | |
877 | .B x | |
878 | Key exchange: reception, parsing and emission of key exchange messages. | |
879 | .TP | |
880 | .B m | |
881 | Key management: loading keys and checking for file modifications. | |
37941236 | 882 | .TP |
883 | .B l | |
884 | Display information about challenge issuing and verification. | |
885 | .TP | |
886 | .B p | |
887 | Display contents of packets sent and received by the tunnel and/or peer | |
888 | modules. | |
889 | .TP | |
890 | .B c | |
891 | Display inputs, outputs and intermediate results of cryptographic | |
892 | operations. This includes plaintext and key material. Use with | |
893 | caution. | |
894 | .TP | |
895 | .B A | |
896 | All of the above. | |
d6623498 | 897 | .PP |
898 | Note that the | |
899 | .B p | |
900 | (packet contents) | |
901 | and | |
902 | .B c | |
903 | (crypto details) | |
904 | outputs provide extra detail for other outputs. Specifying | |
905 | .B p | |
906 | without | |
37941236 | 907 | .BR r |
d6623498 | 908 | or |
909 | .B t | |
910 | isn't useful; neither is specifying | |
911 | .B c | |
912 | without one of | |
913 | .BR s , | |
37941236 | 914 | .BR l , |
d6623498 | 915 | .B x |
916 | or | |
917 | .BR m . | |
918 | .RE | |
13a55605 | 919 | .SP |
060ca767 | 920 | .B "TUNNELS" |
921 | For each available tunnel driver, an | |
922 | .B INFO | |
923 | line is printed giving its name. | |
13a55605 | 924 | .SP |
060ca767 | 925 | .B "VERSION" |
926 | Causes the server to emit an | |
927 | .B INFO | |
83487ded | 928 | line stating its software version, as two tokens: the server name, and |
060ca767 | 929 | its version string. The server name |
930 | .B tripe | |
931 | is reserved to the Straylight/Edgeware implementation. | |
13a55605 | 932 | .SP |
3cdc3f3a | 933 | .BR "WATCH " [\fIoptions\fP] |
bdc44f5b | 934 | Enables or disables asynchronous broadcasts |
3cdc3f3a | 935 | .IR "for the current connection only" . |
060ca767 | 936 | See |
e04c2d50 | 937 | .B "Trace lists" |
3cdc3f3a | 938 | above. The default watch state for the connection the server opens |
939 | automatically on stdin/stdout is to show warnings and trace messages; | |
bdc44f5b MW |
940 | other connections show no asynchronous broadcast messages. (This is |
941 | done in order to guarantee that a program reading the server's stdout | |
942 | does not miss any warnings.) | |
3cdc3f3a | 943 | .RS |
944 | .PP | |
060ca767 | 945 | Message types provided are: |
3cdc3f3a | 946 | .TP |
947 | .B t | |
948 | .B TRACE | |
949 | messages. | |
950 | .TP | |
951 | .B n | |
952 | .B NOTE | |
953 | messages. | |
954 | .TP | |
955 | .B w | |
956 | .B WARN | |
957 | messages. | |
958 | .TP | |
37941236 | 959 | .B A |
3cdc3f3a | 960 | All of the above. |
961 | .RE | |
13a55605 | 962 | .SP |
bd58d532 | 963 | .BI "WARN " tokens\fR... |
e04c2d50 | 964 | Issues a |
bd58d532 | 965 | .B USER |
966 | warning to all interested administration clients. | |
fc916a09 MW |
967 | . |
968 | .\"-------------------------------------------------------------------------- | |
3cdc3f3a | 969 | .SH "ERROR MESSAGES" |
fc916a09 | 970 | . |
13a55605 | 971 | .\"* 20 Error messages (FAIL codes) |
3cdc3f3a | 972 | The following |
973 | .B FAIL | |
de014da6 | 974 | (or |
975 | .BR BGFAIL ) | |
3cdc3f3a | 976 | messages are sent to clients as a result of errors during command |
977 | processing. | |
13a55605 | 978 | .SP |
3cdc3f3a | 979 | .BI "already-daemon" |
980 | (For | |
981 | .BR DAEMON .) | |
982 | The | |
983 | .B tripe | |
984 | server is already running as a daemon. | |
13a55605 | 985 | .SP |
f43df819 | 986 | .BI "bad-addr-syntax " message |
37941236 | 987 | (For commands accepting socket addresses.) The address couldn't be |
988 | understood. | |
13a55605 | 989 | .SP |
37d4c59e MW |
990 | .BI "bad-base64 " message |
991 | (For commands accepting Base64-encoded input.) The Base64-encoded | |
992 | string was invalid. | |
993 | .SP | |
f43df819 | 994 | .BI "bad-syntax " cmd " " message |
3cdc3f3a | 995 | (For any command.) The command couldn't be understood: e.g., the number |
996 | of arguments was wrong. | |
13a55605 | 997 | .SP |
83487ded | 998 | .BI "bad-time-spec " token |
0ba8de86 | 999 | The |
83487ded | 1000 | .I token |
0ba8de86 | 1001 | is not a valid time interval specification. Acceptable time |
e04c2d50 | 1002 | specifications are nonnegative integers followed optionally by |
0ba8de86 | 1003 | .BR d , |
1004 | .BR h , | |
1005 | .BR m , | |
1006 | or | |
1007 | .BR s , | |
1008 | for days, hours, minutes, or seconds, respectively. | |
13a55605 | 1009 | .SP |
3cdc3f3a | 1010 | .BI "bad-trace-option " char |
1011 | (For | |
1012 | .BR TRACE .) | |
1013 | An unknown trace option was requested. | |
13a55605 | 1014 | .SP |
3cdc3f3a | 1015 | .BI "bad-watch-option " char |
1016 | (For | |
1017 | .BR WATCH .) | |
1018 | An unknown watch option was requested. | |
13a55605 | 1019 | .SP |
f43df819 | 1020 | .BI "daemon-error " ecode " " message |
3cdc3f3a | 1021 | (For |
1022 | .BR DAEMON .) | |
1023 | An error occurred during the attempt to become a daemon, as reported by | |
1024 | .IR message . | |
13a55605 | 1025 | .SP |
3cdc3f3a | 1026 | .BI "invalid-port " number |
1027 | (For | |
1028 | .BR ADD .) | |
1029 | The given port number is out of range. | |
13a55605 | 1030 | .SP |
bdc44f5b | 1031 | .BI "not-service-provider " service |
e04c2d50 | 1032 | (For |
bdc44f5b MW |
1033 | .BR SVCRELEASE .) |
1034 | The invoking client is not the current provider of the named | |
1035 | .IR service , | |
1036 | and is therefore not allowed to release it. | |
1037 | .SP | |
3cdc3f3a | 1038 | .BI "peer-create-fail " peer |
1039 | (For | |
1040 | .BR ADD .) | |
1041 | Adding | |
1042 | .I peer | |
1043 | failed for some reason. A warning should have been emitted explaining | |
1044 | why. | |
13a55605 | 1045 | .SP |
c8e02c8a MW |
1046 | .BI "peer-addr-exists " address\fR... |
1047 | (For | |
1048 | .BR ADD .) | |
1049 | There is already a peer with the given | |
1050 | .IR address . | |
1051 | .SP | |
3cdc3f3a | 1052 | .BI "peer-exists " peer |
1053 | (For | |
1054 | .BR ADD .) | |
1055 | There is already a peer named | |
d6623498 | 1056 | .IR peer . |
13a55605 | 1057 | .SP |
0ba8de86 | 1058 | .B "ping-send-failed" |
1059 | The attempt to send a ping packet failed, probably due to lack of | |
1060 | encryption keys. | |
13a55605 | 1061 | .SP |
75566d17 MW |
1062 | .B "provider-failed" |
1063 | (For | |
1064 | .BR SVCSUBMIT .) | |
1065 | The service provider disconnected without sending back a final reply to | |
1066 | the job. | |
1067 | .SP | |
1068 | .B "provider-overloaded" | |
1069 | (For | |
1070 | .BR SVCSUBMIT .) | |
1071 | The service provider has too many jobs queued up for it already. | |
1072 | .SP | |
3cdc3f3a | 1073 | .BI "resolve-error " hostname |
1074 | (For | |
1075 | .BR ADD .) | |
1076 | The DNS name | |
1077 | .I hostname | |
1078 | could not be resolved. | |
13a55605 | 1079 | .SP |
3cdc3f3a | 1080 | .BI "resolver-timeout " hostname |
1081 | (For | |
1082 | .BR ADD .) | |
1083 | The DNS name | |
1084 | .I hostname | |
1085 | took too long to resolve. | |
13a55605 | 1086 | .SP |
bdc44f5b MW |
1087 | .BI "service-exists " service " " version |
1088 | (For | |
1089 | .BR SVCCLAIM .) | |
1090 | Another client is already providing the stated | |
1091 | .I version | |
1092 | of the | |
1093 | .IR service . | |
1094 | .SP | |
1095 | .BI "service-too-old " service " " version | |
1096 | (For | |
1097 | .B SVCENSURE | |
1098 | and | |
1099 | .BR SVCSUBMIT .) | |
1100 | Only the given | |
1101 | .I version | |
1102 | of the requested | |
1103 | .I service | |
1104 | is available, which does not meet the stated requirements. | |
1105 | .SP | |
ff92ffd3 MW |
1106 | .BI "tag-exists " tag |
1107 | (For long-running commands.) The named | |
1108 | .I tag | |
1109 | is already the tag of an outstanding job. | |
1110 | .SP | |
3cdc3f3a | 1111 | .BI "unknown-command " token |
1112 | The command | |
9df937a3 | 1113 | .I token |
78dcf842 | 1114 | was not recognized. |
13a55605 | 1115 | .SP |
72482dfa MW |
1116 | .BI "unknown-jobid " jobid |
1117 | (For | |
1118 | .BR SVCOK , | |
1119 | .BR SVCFAIL , | |
1120 | and | |
1121 | .BR SVCINFO .) | |
1122 | The token | |
1123 | .I jobid | |
1124 | is not recognized as identifying an outstanding job. It may have just | |
1125 | been cancelled. | |
1126 | .SP | |
3cdc3f3a | 1127 | .BI "unknown-peer " name |
1128 | (For | |
1129 | .BR ADDR , | |
1130 | .BR IFNAME , | |
1131 | .BR KILL , | |
64cf2223 | 1132 | .BR SETIFNAME , |
3cdc3f3a | 1133 | and |
1134 | .BR STATS .) | |
1135 | There is no peer called | |
1136 | .IR name . | |
13a55605 | 1137 | .SP |
fd68efa9 | 1138 | .BI "unknown-port " port |
3cdc3f3a | 1139 | (For |
1140 | .BR ADD .) | |
fd68efa9 MW |
1141 | The port name |
1142 | .I port | |
e04c2d50 | 1143 | couldn't be found in |
3cdc3f3a | 1144 | .BR /etc/services . |
dad7eebc | 1145 | .SP |
bdc44f5b MW |
1146 | .BI "unknown-service " service |
1147 | (For | |
1148 | .BR SVCENSURE , | |
1149 | .BR SVCQUERY , | |
1150 | .BR SVCRELEASE , | |
1151 | and | |
1152 | .BR SVCSUBMIT .) | |
1153 | The token | |
1154 | .I service | |
1155 | is not recognized as the name of a client-provided service. | |
dad7eebc | 1156 | .SP |
ff92ffd3 MW |
1157 | .BI "unknown-tag " tag |
1158 | (For | |
1159 | .BR BGCANCEL .) | |
1160 | The given | |
1161 | .I tag | |
1162 | is not the tag for any outstanding background job. It may have just | |
1163 | finished. | |
75566d17 MW |
1164 | .SP |
1165 | .BI "unknown-tunnel " tun | |
1166 | (For | |
1167 | .BR ADD .) | |
1168 | The given | |
1169 | .I tun | |
1170 | is not the name of any known tunnel driver. | |
fc916a09 MW |
1171 | . |
1172 | .\"-------------------------------------------------------------------------- | |
3cdc3f3a | 1173 | .SH "NOTIFICATIONS" |
fc916a09 | 1174 | . |
13a55605 | 1175 | .\"* 30 Notification broadcasts (NOTE codes) |
3cdc3f3a | 1176 | The following notifications are sent to clients who request them. |
13a55605 | 1177 | .SP |
42da2a58 | 1178 | .BI "ADD " peer " " ifname " " address \fR... |
3cdc3f3a | 1179 | A new peer has been added. The peer's name is |
42da2a58 | 1180 | .IR peer , |
1181 | its tunnel is network interface | |
1182 | .IR ifname , | |
3cdc3f3a | 1183 | and its network address is |
1184 | .IR address . | |
13a55605 | 1185 | .SP |
3cdc3f3a | 1186 | .BI "DAEMON" |
1187 | The server has forked off into the sunset and become a daemon. | |
13a55605 | 1188 | .SP |
37941236 | 1189 | .BI "GREET " challenge " " address \fR... |
1190 | A valid greeting was received, with the given challenge (exactly as it | |
1191 | was returned by | |
1192 | .B GETCHAL | |
1193 | earlier). | |
13a55605 | 1194 | .SP |
d6623498 | 1195 | .BI "KILL " peer |
3cdc3f3a | 1196 | The peer |
1197 | .I peer | |
1198 | has been killed. | |
13a55605 | 1199 | .SP |
8362ac1c MW |
1200 | .BI "KNOCK " peer " " address |
1201 | The currently unknown | |
1202 | .I peer | |
1203 | is attempting to connect from | |
1204 | .IR address . | |
1205 | .SP | |
3cdc3f3a | 1206 | .BI "KXDONE " peer |
1207 | Key exchange with | |
1208 | .I peer | |
1209 | finished successfully. | |
13a55605 | 1210 | .SP |
3cdc3f3a | 1211 | .BI "KXSTART " peer |
1212 | Key exchange with | |
1213 | .I peer | |
1214 | has begun or restarted. If key exchange keeps failing, this message | |
1215 | will be repeated periodically. | |
13a55605 | 1216 | .SP |
6411163d MW |
1217 | .BI "NEWADDR " peer " " address |
1218 | The given mobile | |
1219 | .IR peer 's | |
1220 | IP address has been changed to | |
1221 | .IR address . | |
1222 | .SP | |
64cf2223 MW |
1223 | .BI "NEWIFNAME " peer " " old-name " " new-name |
1224 | The given | |
1225 | .IR peer 's | |
1226 | tunnel interface name has been changed from | |
1227 | .I old-name | |
1228 | to | |
1229 | .IR new-name , | |
1230 | as a result of a | |
1231 | .B SETIFNAME | |
1232 | command. | |
1233 | .SP | |
bdc44f5b MW |
1234 | .BI "SVCCLAIM " service " " version |
1235 | The named | |
1236 | .I service | |
1237 | is now available, at the stated | |
1238 | .IR version . | |
1239 | .SP | |
1240 | .BI "SVCRELEASE " service | |
1241 | The named | |
1242 | .I service | |
1243 | is no longer available. | |
1244 | .SP | |
bd58d532 | 1245 | .BI "USER " tokens\fR... |
1246 | An administration client issued a notification using the | |
1247 | .B NOTIFY | |
1248 | command. | |
fc916a09 MW |
1249 | . |
1250 | .\"-------------------------------------------------------------------------- | |
3cdc3f3a | 1251 | .SH "WARNINGS" |
fc916a09 | 1252 | . |
13a55605 MW |
1253 | .\"* 40 Warning broadcasts (WARN codes) |
1254 | .\"+sep | |
3cdc3f3a | 1255 | There are many possible warnings. They are categorized according to |
1256 | their first tokens. | |
f43df819 MW |
1257 | .PP |
1258 | Many of these warnings report system errors. These are reported as a | |
1259 | pair of tokens, described below as | |
1260 | .I ecode | |
1261 | and | |
1262 | .IR message . | |
1263 | The | |
1264 | .I ecode | |
1265 | is a string of the form | |
1266 | .BI E number | |
1267 | giving the | |
1268 | .BR errno (3) | |
1269 | value of the error; the | |
1270 | .I message | |
1271 | is the `human-readable' form of the message, as reported by | |
1272 | .BR strerror (3). | |
3cdc3f3a | 1273 | .SS "ABORT warnings" |
1274 | These all indicate that the | |
d6623498 | 1275 | .B tripe |
3cdc3f3a | 1276 | server has become unable to continue. If enabled, the server will dump |
1277 | core in its configuration directory. | |
13a55605 | 1278 | .SP |
3cdc3f3a | 1279 | .BI "ABORT repeated-select-errors" |
1280 | The main event loop is repeatedly failing. If the server doesn't quit, | |
1281 | it will probably waste all available CPU doing nothing. | |
1282 | .SS "ADMIN warnings" | |
1283 | These indicate a problem with the administration socket interface. | |
13a55605 | 1284 | .SP |
f43df819 | 1285 | .BI "ADMIN accept-error " ecode " " message |
3cdc3f3a | 1286 | There was an error while attempting to accept a connection from a new |
1287 | client. | |
13a55605 | 1288 | .SP |
f43df819 | 1289 | .BI "ADMIN client-write-error " ecode " " message |
3cdc3f3a | 1290 | There was an error sending data to a client. The connection to the |
1291 | client has been closed. | |
37941236 | 1292 | .SS "CHAL warnings" |
1293 | These indicate errors in challenges, either in the | |
1294 | .B CHECKCHAL | |
1295 | command or in greeting packets. | |
13a55605 | 1296 | .SP |
37941236 | 1297 | .B "CHAL impossible-challenge" |
1298 | The server hasn't issued any challenges yet. Quite how anyone else | |
1299 | thought he could make one up is hard to imagine. | |
13a55605 | 1300 | .SP |
37941236 | 1301 | .B "CHAL incorrect-tag" |
1302 | Challenge received contained the wrong authentication data. It might be | |
1303 | very stale, or a forgery. | |
13a55605 | 1304 | .SP |
37941236 | 1305 | .B "CHAL invalid-challenge" |
1306 | Challenge received was the wrong length. We might have changed MAC | |
1307 | algorithms since the challenge was issued, or it might just be rubbish. | |
13a55605 | 1308 | .SP |
37941236 | 1309 | .B "CHAL replay duplicated-sequence" |
1310 | Challenge received was a definite replay of an old challenge. Someone's | |
1311 | up to something! | |
13a55605 | 1312 | .SP |
37941236 | 1313 | .B "CHAL replay old-sequence" |
1314 | Challenge received was old, but maybe not actually a replay. Try again. | |
3cdc3f3a | 1315 | .SS "KEYMGMT warnings" |
1316 | These indicate a problem with the keyring files, or the keys stored in | |
4d36660a MW |
1317 | them. The first token is either |
1318 | .B private-keyring | |
1319 | or | |
1320 | .B public-keyring | |
1321 | (notated | |
1322 | .IB which -keyring | |
1323 | in the descriptions below) indicating which keyring file is problematic, | |
1324 | and the second token is the filename of the keyring. Frequently a key | |
1325 | tag may be given next, preceded by the token | |
1326 | .BR key . | |
1327 | .SP | |
f1d5c891 MW |
1328 | .BI "KEYMGMT private-keyring " file " key " tag " incorrect-public-key" |
1329 | The private key doesn't record the correct corresponding public key. | |
1330 | .SP | |
4d36660a MW |
1331 | .BI "KEYMGMT public-keyring " file " key " tag " algorithm-mismatch" |
1332 | A peer's public key doesn't request the same algorithms as our private | |
1333 | key. | |
1334 | .SP | |
1335 | .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length " len | |
1336 | The key attributes specify the length of MAC tag as | |
1337 | .I len | |
1338 | but this is an invalid value \(en either too large or not a multiple of | |
1339 | eight. | |
1340 | .SP | |
1341 | .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length-string " str | |
1342 | The key attributes contain | |
1343 | .I str | |
1344 | where a MAC tag length was expected. The key was generated wrongly. | |
1345 | .SP | |
1346 | .BI "KEYMGMT private-keyring " file " key " tag " changed-group" | |
1347 | The private keyring has been changed, but the new private key can't be | |
1348 | used because it uses a different group for Diffie\(enHellman key | |
1349 | exchange. | |
1350 | .SP | |
1351 | .BI "KEYMGMT " which "-keyring " file " io-error " ecode " " message | |
1352 | A system error occurred while opening or reading the keyring file. | |
1353 | .SP | |
a93aacce MW |
1354 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-bulk-transform " bulk |
1355 | The key specifies the use of an unknown bulk-crypto transform | |
1356 | .IR bulk . | |
1357 | Maybe the key was generated wrongly, or maybe the version of Catacomb | |
1358 | installed is too old. | |
1359 | .SP | |
4d36660a MW |
1360 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-cipher " cipher |
1361 | The key specifies the use of an unknown symmetric encryption algorithm | |
1362 | .IR cipher . | |
1363 | Maybe the key was generated wrongly, or maybe the version of | |
1364 | Catacomb installed is too old. | |
1365 | .SP | |
1366 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-group-type " type | |
1367 | The key specifies the use of a Diffie\(enHellman group of an unknown | |
1368 | .IR type . | |
1369 | Maybe the key was generated wrongly, or maybe the version of | |
1370 | .BR tripe (8) | |
1371 | is too old. | |
1372 | .SP | |
1373 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-hash " hash | |
1374 | The key specifies the use of an unknown hash function | |
1375 | .IR hash . | |
1376 | Maybe the key was generated wrongly, or maybe the version of Catacomb | |
1377 | installed is too old. | |
1378 | .SP | |
1379 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mac " mac | |
1380 | The key specifies the use of an unknown message authentication code | |
1381 | .IR mac . | |
1382 | Maybe the key was generated wrongly, or maybe the version of Catacomb | |
1383 | installed is too old. | |
1384 | .SP | |
1385 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mgf-cipher " mgf | |
1386 | The key specifies the use of an unknown symmetric encryption function | |
1387 | .I mgf | |
1388 | for mask generation. Maybe the key was generated wrongly, or maybe the | |
1389 | version of Catacomb installed is too old. | |
1390 | .SP | |
07bdda1f MW |
1391 | .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-serialization-format " ser |
1392 | The key specifies the use of an unknown serialization format | |
1393 | .I ser | |
1394 | for hashing group elements. Maybe the key was generated wrongly, or | |
1395 | maybe the version of Catacomb installed is too old. | |
1396 | .SP | |
4d36660a MW |
1397 | .BI "KEYMGMT " which "-keyring " file " key " tag " no-hmac-for-hash " hash |
1398 | No message authentication code was given explicitly, and there's no | |
1399 | implementation of HMAC for the selected hash function | |
1400 | .IR hash . | |
1401 | .SP | |
1402 | .BI "KEYMGMT " which "-keyring " file " key " tag " " alg " " name " no-key-size " hashsz | |
1403 | The | |
1404 | .I alg | |
1405 | token is either | |
1406 | .B cipher | |
1407 | or | |
1408 | .BR mac . | |
1409 | The named algorithm requires more key material than the hash function | |
1410 | can provide. You must change either the hash function, or the cipher or | |
1411 | MAC. | |
13a55605 | 1412 | .SP |
4d36660a MW |
1413 | .BI "KEYMGMT " which "-keyring " file " key " tag " mgf " mgf " restrictive-key-schedule" |
1414 | The cipher selected for mask-generation is unsuitable because it can't | |
1415 | accept arbitrary-sized keys. | |
13a55605 | 1416 | .SP |
4d36660a MW |
1417 | .BI "KEYMGMT " which "-keyring " file " key-not-found " tag |
1418 | A key named | |
3cdc3f3a | 1419 | .I tag |
4d36660a | 1420 | couldn't be found in the keyring. |
13a55605 | 1421 | .SP |
fb6a9f13 MW |
1422 | .BI "KEYMGMT " which "-keyring " file " unknown-key-id 0x" keyid |
1423 | A key with the given | |
1424 | .I keyid | |
1425 | (in hex) was requested but not found. | |
1426 | .SP | |
4d36660a MW |
1427 | .BI "KEYMGMT " which "-keyring " file " line " line " " message |
1428 | The contents of the keyring file are invalid. There may well be a bug | |
1429 | in the | |
1430 | .BR key (1) | |
1431 | program. | |
3cdc3f3a | 1432 | .SS "KX warnings" |
1433 | These indicate problems during key-exchange. Many indicate either a bug | |
1434 | in the server (either yours or the remote one), or some kind of attack | |
1435 | in progress. All name a | |
1436 | .I peer | |
1437 | as the second token: this is the peer the packet is apparently from, | |
1438 | though it may have been sent by an attacker instead. | |
1439 | .PP | |
1440 | In the descriptions below, | |
1441 | .I msgtoken | |
1442 | is one of the tokens | |
1443 | .BR pre-challenge , | |
1444 | .BR cookie , | |
1445 | .BR challenge , | |
1446 | .BR reply , | |
1447 | .BR switch-rq , | |
3cdc3f3a | 1448 | .BR switch-ok . |
8362ac1c MW |
1449 | .BR token-rq , |
1450 | .BR token , | |
1451 | or | |
1452 | .BR knock . | |
13a55605 | 1453 | .SP |
35c8b547 MW |
1454 | .BI "KX " peer " algorithms-mismatch local-private-key " privtag " peer-public-key " pubtag |
1455 | The algorithms specified in the peer's public key | |
1456 | .I pubtag | |
1457 | don't match the ones described in the private key | |
1458 | .IR privtag . | |
1459 | .SP | |
3cdc3f3a | 1460 | .BI "KX " peer " bad-expected-reply-log" |
1461 | The challenges | |
1462 | .B tripe | |
1463 | uses in its protocol contain a check value which proves that the | |
1464 | challenge is honest. This message indicates that the check value | |
1465 | supplied is wrong: someone is attempting to use bogus challenges to | |
1466 | persuade your | |
1467 | .B tripe | |
1468 | server to leak private key information. No chance! | |
13a55605 | 1469 | .SP |
bd58d532 | 1470 | .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok" |
3cdc3f3a | 1471 | A symmetrically-encrypted portion of a key-exchange message failed to |
1472 | decrypt. | |
13a55605 | 1473 | .SP |
3cdc3f3a | 1474 | .BI "KX " peer " invalid " msgtoken |
1475 | A key-exchange message was malformed. This almost certainly indicates a | |
1476 | bug somewhere. | |
13a55605 | 1477 | .SP |
bd58d532 | 1478 | .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok" |
3cdc3f3a | 1479 | A message didn't contain the right magic data. This may be a replay of |
1480 | some old exchange, or random packets being sent in an attempt to waste | |
1481 | CPU. | |
13a55605 | 1482 | .SP |
35c8b547 MW |
1483 | .BI "KX " peer " " which "-key-expired" |
1484 | The local private key or the peer's public key (distinguished by | |
1485 | .IR which ) | |
1486 | has expired. Either you or the peer's maintainer should have arranged | |
1487 | for a replacement before now. | |
13a55605 | 1488 | .SP |
3cdc3f3a | 1489 | .BI "KX " peer " sending-cookie" |
1490 | We've received too many bogus pre-challenge messages. Someone is trying | |
1491 | to flood us with key-exchange messages and make us waste CPU on doing | |
1492 | hard asymmetric crypto sums. | |
13a55605 | 1493 | .SP |
3cdc3f3a | 1494 | .BI "KX " peer " unexpected " msgtoken |
1495 | The message received wasn't appropriate for this stage of the key | |
1496 | exchange process. This may mean that one of our previous packets got | |
e04c2d50 | 1497 | lost. For |
3cdc3f3a | 1498 | .BR pre-challenge , |
1499 | it may simply mean that the peer has recently restarted. | |
13a55605 | 1500 | .SP |
3cdc3f3a | 1501 | .BI "KX " peer " unknown-challenge" |
1502 | The peer is asking for an answer to a challenge which we don't know | |
1503 | about. This may mean that we've been inundated with challenges from | |
1504 | some malicious source | |
1505 | .I who can read our messages | |
1506 | and discarded the valid one. | |
13a55605 | 1507 | .SP |
3cdc3f3a | 1508 | .BI "KX " peer " unknown-message 0x" nn |
1509 | An unknown key-exchange message arrived. | |
1510 | .SS "PEER warnings" | |
1511 | These are largely concerned with management of peers and the low-level | |
83487ded | 1512 | details of the network protocol. The second token is usually the name of |
e04c2d50 | 1513 | a peer, or |
3cdc3f3a | 1514 | .RB ` \- ' |
1515 | if none is relevant. | |
13a55605 | 1516 | .SP |
3cdc3f3a | 1517 | .BI "PEER " peer " bad-packet no-type" |
1518 | An empty packet arrived. This is very strange. | |
13a55605 | 1519 | .SP |
3cdc3f3a | 1520 | .BI "PEER " peer " bad-packet unknown-category 0x" nn |
1521 | The message category | |
1522 | .I nn | |
1523 | (in hex) isn't understood. Probably a strange random packet from | |
1524 | somewhere; could be an unlikely bug. | |
13a55605 | 1525 | .SP |
3cdc3f3a | 1526 | .BI "PEER " peer " bad-packet unknown-type 0x" nn |
1527 | The message type | |
1528 | .I nn | |
1529 | (in hex) isn't understood. Probably a strange random packet from | |
1530 | somewhere; could be an unlikely bug. | |
13a55605 | 1531 | .SP |
0ba8de86 | 1532 | .BI "PEER " peer " corrupt-encrypted-ping" |
1533 | The peer sent a ping response which matches an outstanding ping, but its | |
1534 | payload is wrong. There's definitely a bug somewhere. | |
13a55605 | 1535 | .SP |
0ba8de86 | 1536 | .BI "PEER " peer " corrupt-transport-ping" |
1537 | The peer (apparently) sent a ping response which matches an outstanding | |
1538 | ping, but its payload is wrong. Either there's a bug, or the bad guys | |
1539 | are playing tricks on you. | |
13a55605 | 1540 | .SP |
3cdc3f3a | 1541 | .BI "PEER " peer " decrypt-failed" |
1542 | An encrypted IP packet failed to decrypt. It may have been mangled in | |
1543 | transit, or may be a very old packet from an expired previous session | |
1544 | key. There is usually a considerable overlap in the validity periods of | |
1545 | successive session keys, so this shouldn't occur unless the key exchange | |
1546 | takes ages or fails. | |
13a55605 | 1547 | .SP |
0ba8de86 | 1548 | .BI "PEER " peer " malformed-encrypted-ping" |
1549 | The peer sent a ping response which is hopelessly invalid. There's | |
1550 | definitely a bug somewhere. | |
13a55605 | 1551 | .SP |
0ba8de86 | 1552 | .BI "PEER " peer " malformed-transport-ping" |
1553 | The peer (apparently) sent a ping response which is hopelessly invalid. | |
1554 | Either there's a bug, or the bad guys are playing tricks on you. | |
13a55605 | 1555 | .SP |
3cdc3f3a | 1556 | .BI "PEER " peer " packet-build-failed" |
1557 | There wasn't enough space in our buffer to put the packet we wanted to | |
1558 | send. Shouldn't happen. | |
13a55605 | 1559 | .SP |
f43df819 | 1560 | .BI "PEER \- socket-read-error " ecode " " message |
3cdc3f3a | 1561 | An error occurred trying to read an incoming packet. |
13a55605 | 1562 | .SP |
f43df819 | 1563 | .BI "PEER " peer " socket-write-error " ecode " " message |
3cdc3f3a | 1564 | An error occurred attempting to send a network packet. We lost that |
1565 | one. | |
13a55605 | 1566 | .SP |
8362ac1c MW |
1567 | .BI "PEER " address\fR... " socket-write-error " ecode " " message |
1568 | An error occurred attempting to send a network packet. We lost that | |
1569 | one. | |
1570 | .SP | |
0ba8de86 | 1571 | .BI "PEER " peer " unexpected-encrypted-ping 0x" id |
1572 | The peer sent an encrypted ping response whose id doesn't match any | |
1573 | outstanding ping. Maybe it was delayed for longer than the server was | |
1574 | willing to wait, or maybe the peer has gone mad. | |
13a55605 | 1575 | .SP |
0ba8de86 | 1576 | .BI "PEER \- unexpected-source " address\fR... |
1577 | A packet arrived from | |
1578 | .I address | |
1579 | (a network address \(en see above), but no peer is known at that | |
1580 | address. This may indicate a misconfiguration, or simply be a result of | |
1581 | one end of a connection being set up before the other. | |
13a55605 | 1582 | .SP |
0ba8de86 | 1583 | .BI "PEER " peer " unexpected-transport-ping 0x" id |
1584 | The peer (apparently) sent a transport ping response whose id doesn't | |
1585 | match any outstanding ping. Maybe it was delayed for longer than the | |
1586 | server was willing to wait, or maybe the peer has gone mad; or maybe | |
1587 | there are bad people trying to confuse you. | |
e8ea4061 MW |
1588 | .SS "PRIVSEP warnings" |
1589 | These indicate problems with the privilege-separation helper process. | |
1590 | (The server tries to drop its privileges when it starts up, leaving a | |
1591 | privileged helper process behind which will create and hand over tunnel | |
1592 | descriptors on request, but hopefully not do anything else especially | |
1593 | dangerous. Tunnel descriptors are not completely safe, but this is | |
1594 | probably better than nothing.) | |
1595 | .SP | |
1596 | .BI "PRIVSEP child-exited " rc | |
1597 | The helper process exited normally with status | |
1598 | .IR rc . | |
1599 | Status 0 means that it thought the server didn't want it any more; 1 | |
1600 | means that it was invoked incorrectly; 127 means that some system call | |
1601 | failed. | |
1602 | .SP | |
1603 | .BI "PRIVSEP child-killed " sig | |
1604 | The helper process was killed by signal number | |
1605 | .IR sig . | |
1606 | .SP | |
1607 | .BI "PRIVSEP child-died " status | |
1608 | The helper process died in some unexpected way; | |
1609 | .I status is the raw status code returned by | |
1610 | .BR waitpid (2), | |
1611 | because the server didn't understand how to decode it. | |
1612 | .SP | |
1613 | .BI "PRIVSEP helper-died" | |
1614 | A tunnel driver requires a tunnel descriptor from the helper, but the | |
1615 | helper isn't running so this won't work. | |
1616 | .SP | |
1617 | .BI "PRIVSEP helper-read-error " ecode " " message | |
1618 | The server failed to read a response from the helper process. | |
1619 | .SP | |
1620 | .BI "PRIVSEP helper-short-read" | |
1621 | The helper process didn't send back enough data, and has likely crashed. | |
1622 | .SP | |
1623 | .BI "PRIVSEP helper-write-error " ecode " " message | |
1624 | The server failed to send a message to the helper process. | |
1625 | .SP | |
1626 | .BI "PRIVSEP no-fd-from-helper" | |
1627 | The helper process sent back a positive response, but didn't include the | |
1628 | requested tunnel descriptor. | |
1629 | .SP | |
1630 | .BI "PRIVSEP unknown-response-code" | |
1631 | The helper process sent back an incomprehensible reply. It's probably | |
1632 | very confused and may crash. | |
3cdc3f3a | 1633 | .SS "SERVER warnings" |
1634 | These indicate problems concerning the server process as a whole. | |
13a55605 | 1635 | .SP |
3cdc3f3a | 1636 | .BI "SERVER ignore signal " name |
1637 | A signal arrived, but the server ignored it. Currently this happens for | |
1638 | .B SIGHUP | |
1639 | because that's a popular way of telling daemons to re-read their | |
1640 | configuration files. Since | |
1641 | .B tripe | |
1642 | re-reads its keyrings automatically and has no other configuration | |
1643 | files, it's not relevant, but it seemed better to ignore the signal than | |
1644 | let the server die. | |
13a55605 | 1645 | .SP |
3cdc3f3a | 1646 | .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR] |
1647 | A signal arrived and | |
1648 | .B tripe | |
1649 | is going to quit. | |
13a55605 | 1650 | .SP |
3cdc3f3a | 1651 | .BI "SERVER quit admin-request" |
1652 | A client of the administration interface issued a | |
1653 | .B QUIT | |
1654 | command. | |
13a55605 | 1655 | .SP |
46dde080 MW |
1656 | .BI "SERVER quit foreground-eof" |
1657 | The server is running in foreground mode (the | |
1658 | .B \-F | |
1659 | option), and encountered end-of-file on standard input. | |
1660 | .SP | |
f43df819 | 1661 | .BI "SERVER select-error " ecode " " message |
3cdc3f3a | 1662 | An error occurred in the server's main event loop. This is bad: if it |
1663 | happens too many times, the server will abort. | |
e8ea4061 MW |
1664 | .SP |
1665 | .BI "SERVER waitpid-error " ecode " " message | |
1666 | The server was informed that one of its child processes had exited, but | |
1667 | couldn't retrieve the child's status. | |
3cdc3f3a | 1668 | .SS "SYMM warnings" |
1669 | These are concerned with the symmetric encryption and decryption | |
1670 | process. | |
13a55605 | 1671 | .SP |
3cdc3f3a | 1672 | .BI "SYMM replay old-sequence" |
1673 | A packet was received with an old sequence number. It may just have | |
1674 | been delayed or duplicated, or it may have been an attempt at a replay | |
1675 | attack. | |
13a55605 | 1676 | .SP |
3cdc3f3a | 1677 | .BI "SYMM replay duplicated-sequence" |
1678 | A packet was received with a sequence number we've definitely seen | |
1679 | before. It may be an accidental duplication because the 'net is like | |
1680 | that, or a deliberate attempt at a replay. | |
1681 | .SS "TUN warnings" | |
1682 | These concern the workings of the system-specific tunnel driver. The | |
83487ded | 1683 | second token is the name of the tunnel interface in question, or |
3cdc3f3a | 1684 | .RB ` \- ' |
1685 | if none. | |
13a55605 | 1686 | .SP |
3cdc3f3a | 1687 | .BI "TUN \- bsd no-tunnel-devices" |
1688 | The driver couldn't find an available tunnel device. Maybe if you | |
e04c2d50 | 1689 | create some more |
3cdc3f3a | 1690 | .BI /dev/tun nn |
1691 | files, it will work. | |
13a55605 | 1692 | .SP |
72917fe7 | 1693 | .BI "TUN \- " tun-name " open-error " device " " ecode " " message |
3cdc3f3a | 1694 | An attempt to open the tunnel device file |
1695 | .I device | |
1696 | failed. | |
13a55605 | 1697 | .SP |
f43df819 | 1698 | .BI "TUN \- linux config-error " ecode " " message |
3cdc3f3a | 1699 | Configuring the Linux TUN/TAP interface failed. |
13a55605 | 1700 | .SP |
f43df819 | 1701 | .BI "TUN " ifname " " tun-name " read-error " ecode " " message |
42da2a58 | 1702 | Reading from the tunnel device failed. |
13a55605 | 1703 | .SP |
898975ee MW |
1704 | .BI "TUN " ifname " " tun-name " write-error " ecode " " message |
1705 | Writing from the tunnel device failed. | |
1706 | .SP | |
42da2a58 | 1707 | .BI "TUN " ifname " slip bad-escape" |
1708 | The SLIP driver encountered a escaped byte it wasn't expecting to see. | |
1709 | The erroneous packet will be ignored. | |
13a55605 | 1710 | .SP |
b9066fbb | 1711 | .BI "TUN " ifname " slip eof" |
1712 | The SLIP driver encountered end-of-file on its input descriptor. | |
1713 | Pending data is discarded, and no attempt is made to read any more data | |
1714 | from that interface ever. | |
13a55605 | 1715 | .SP |
b9066fbb | 1716 | .BI "TUN " ifname " slip escape-end" |
1717 | The SLIP driver encountered an escaped `end' marker. This probably | |
1718 | means that someone's been sending it junk. The erroneous packet is | |
1719 | discarded, and we hope that we've rediscovered synchronization. | |
13a55605 | 1720 | .SP |
f43df819 | 1721 | .BI "TUN \- slip fork-error " ecode " " message |
42da2a58 | 1722 | The SLIP driver encountered an error forking a child process while |
1723 | allocating a new dynamic interface. | |
13a55605 | 1724 | .SP |
42da2a58 | 1725 | .BI "TUN \- slip no-slip-interfaces" |
1726 | The driver ran out of static SLIP interfaces. Either preallocate more, | |
1727 | or use dynamic SLIP interface allocation. | |
13a55605 | 1728 | .SP |
b9066fbb | 1729 | .BI "TUN " ifname " slip overflow" |
1730 | The SLIP driver gave up reading a packet because it got too large. | |
13a55605 | 1731 | .SP |
f43df819 | 1732 | .BI "TUN \- slip pipe-error " ecode " " message |
42da2a58 | 1733 | The SLIP driver encountered an error creating pipes while allocating a |
1734 | new dynamic interface. | |
13a55605 | 1735 | .SP |
f43df819 | 1736 | .BI "TUN \- slip read-ifname-failed " ecode " " message |
42da2a58 | 1737 | The SLIP driver encountered an error reading the name of a dynamically |
1738 | allocated interface. Maybe the allocation script is broken. | |
13a55605 | 1739 | .SP |
f43df819 | 1740 | .BI "TUN \- unet config-error " ecode " " message |
42da2a58 | 1741 | Configuring the Linux Unet interface failed. Unet is obsolete and |
1742 | shouldn't be used any more. | |
13a55605 | 1743 | .SP |
f43df819 | 1744 | .BI "TUN \- unet getinfo-error " ecode " " message |
42da2a58 | 1745 | Reading information about the Unet interface failed. Unet is obsolete |
1746 | and shouldn't be used any more. | |
bd58d532 | 1747 | .SS "USER warnings" |
1748 | These are issued by administration clients using the | |
1749 | .B WARN | |
1750 | command. | |
13a55605 | 1751 | .SP |
bd58d532 | 1752 | .BI "USER " tokens\fR... |
1753 | An administration client issued a warning. | |
13a55605 | 1754 | .\"-sep |
fc916a09 MW |
1755 | . |
1756 | .\"-------------------------------------------------------------------------- | |
13a55605 | 1757 | .SH "SUMMARY" |
fc916a09 | 1758 | . |
13a55605 MW |
1759 | .SS "Command responses" |
1760 | .nf | |
2acd7cd6 | 1761 | .BI "BGDETACH " tag |
13a55605 MW |
1762 | .BI "BGFAIL " tag " " tokens \fR... |
1763 | .BI "BGINFO " tag " " tokens \fR... | |
1764 | .BI "BGOK " tag | |
1765 | .BI "FAIL " tokens \fR... | |
1766 | .BI "INFO " tokens \fR... | |
1767 | .B OK | |
1768 | .fi | |
1769 | .\"= summary | |
fc916a09 MW |
1770 | . |
1771 | .\"-------------------------------------------------------------------------- | |
d6623498 | 1772 | .SH "SEE ALSO" |
fc916a09 | 1773 | . |
d6623498 | 1774 | .BR tripectl (1), |
1775 | .BR tripe (8). | |
1776 | .PP | |
3cdc3f3a | 1777 | .IR "The Trivial IP Encryption Protocol" . |
fc916a09 MW |
1778 | . |
1779 | .\"-------------------------------------------------------------------------- | |
d6623498 | 1780 | .SH "AUTHOR" |
fc916a09 | 1781 | . |
d36eda2a | 1782 | Mark Wooding, <mdw@distorted.org.uk> |
fc916a09 MW |
1783 | . |
1784 | .\"----- That's all, folks -------------------------------------------------- |