3 .\" Manual for the administration protocol
5 .\" (c) 2008 Straylight/Edgeware
8 .\"----- Licensing notice ---------------------------------------------------
10 .\" This file is part of Trivial IP Encryption (TrIPE).
12 .\" TrIPE is free software; you can redistribute it and/or modify
13 .\" it under the terms of the GNU General Public License as published by
14 .\" the Free Software Foundation; either version 2 of the License, or
15 .\" (at your option) any later version.
17 .\" TrIPE is distributed in the hope that it will be useful,
18 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
19 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 .\" GNU General Public License for more details.
22 .\" You should have received a copy of the GNU General Public License
23 .\" along with TrIPE; if not, write to the Free Software Foundation,
24 .\" Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
26 .\"--------------------------------------------------------------------------
27 .so ../common/defs.man \" @@@PRE@@@
29 .\"--------------------------------------------------------------------------
30 .TH tripe-admin 5 "18 February 2001" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
32 .\"--------------------------------------------------------------------------
35 tripe-admin \- administrator commands for TrIPE
37 .\"--------------------------------------------------------------------------
40 This manual page describes the administration interface provided by the
46 program can be used either interactively or in scripts to communicate
47 with the server using this interface. Alternatively, simple custom
48 clients can be written in scripting languages such as Perl, Python or
49 Tcl, or more advanced clients such as GUI monitors can be written in C
50 with little difficulty.
52 Administration commands use a textual protocol. Each client command or
53 server response consists of a line of ASCII text terminated by a single
54 linefeed character. No command may be longer than 255 characters.
55 .SS "General structure"
56 Each command or response line consists of a sequence of
57 whitespace-separated tokens. The number and nature of whitespace
58 characters separating two tokens in a client command is not significant;
59 the server always uses a single space character. The first token in a
62 identifying the type of command or response contained. Keywords in
63 client commands are not case-sensitive; the server always uses uppercase
66 In order to allow tokens to contain internal whitespace, a quoting
67 mechanism is provided. Whitespace within matched pairs of quotes \(en
72 \(en is considered to be internal. Any character (other than newline)
73 may be escaped by preceding it with a backslash
75 in particular, this can be used to include quote characters. It is
76 impossible for a token to contain a newline character.
78 On output, the server will use double quotes when necessary.
80 For simple client command, the server responds with zero or more
82 lines, followed by either an
88 provides information requested in the command. An
90 response contains no further data. A
92 code is followed by a machine-readable explanation of why the command
95 Simple command processing is strictly synchronous: the server reads a
96 command, processes it, and responds, before reading the next command.
97 All commands can be run as simple commands. Long-running commands
102 block the client until they finish, but the rest of the server continues
104 .B "Background commands"
105 to find out how to issue long-running commands without blocking.
106 .SS "Asynchronous broadcasts"
107 There are three types of asynchronous broadcast messages which aren't
108 associated with any particular command. Clients can select which
109 broadcast messages they're interested in using the
115 message contains a machine-readable message warning of an error
116 encountered while processing a command, unexpected or unusual behaviour
117 by a peer, or a possible attack by an adversary. Under normal
118 conditions, the server shouldn't emit any warnings.
122 message contains a human-readable tracing message containing diagnostic
123 information. Trace messages are controlled using the
125 command-line option to the server, or the
127 administration command (see below). Support for tracing can be disabled
128 when the package is being configured, and may not be available in your
133 message is a machine-readable notification about some routine but
134 interesting event such as creation or destruction of peers.
135 .SS "Background commands"
140 take a long time to complete. To prevent these long-running commands
141 from tying up a server connection, they can be run in the background.
142 Not all commands can be run like this: the ones that can provide a
144 option, which must be supplied with a
147 A command may fail before it starts running in the background. In this
148 case, the server emits a
150 response, as usual. To indicate that a command has started running in
151 the background, the server emits a response of the form
152 .BI "BGDETACH " tag \fR,
155 is the value passed to the
157 option. From this point on, the server is ready to process more
158 commands and reply to them.
160 Responses to background commands are indicated by a line beginning with
166 followed by the command tag. These correspond to the
171 responses for simple commands:
173 indicates information from a background command which has not completed
178 indicates that a background command succeeded or failed, respectively.
180 A background command will never issue an
184 response: it will always detach and then issue any
189 .SS "Client-provided services"
190 .\"* 25 Service-related messages
191 An administration client can provide services to other clients.
192 Services are given names and versions. A client can attempt to
194 a particular service by issuing the
196 command. This may fail, for example, if some other client already
197 provides the same or later version of the service.
199 Other clients can issue
200 .I "service commands"
203 command; the service provider is expected to handle these commands and
206 There are three important asynchronous messages which will be sent to
209 .BI "SVCCANCEL " jobid
210 The named job has been cancelled, either because the issuing client has
211 disconnected or explicitly cancelled the job using the
215 .BI "SVCCLAIM " service " " version
216 Another client has claimed a later version of the named
218 The recipient is no longer the provider of this service.
220 .BI "SVCJOB " jobid " " service " " command " " args \fR...
221 Announces the arrival of a new job. The
223 is a simple token consisting of alphanumeric characters which
225 uses to identify this job.
227 The service provider can reply to the job using the commands
232 The first of these sends an
234 response and leaves the job active; the other two send an
238 response respectively, and mark the job as being complete.
242 is a potentially long-running command, it can be run in the background.
243 This detail is hidden from service providers:
245 will issue the corresponding
247 responses when appropriate.)
248 .SS "Network addresses"
249 A network address is a sequence of tokens. The first is a token
250 identifying the network address family. The length of an address and
251 the meanings of the subsequent tokens depend on the address family.
252 Address family tokens are not case-sensitive on input; on output, they
253 are always in upper-case.
255 At present, only one address family is understood.
257 .BI "INET " address " \fR[" port \fR]
258 An Internet socket, naming an IPv4 address and UDP port. On output, the
259 address is always in numeric dotted-quad form, and the port is given as
260 a plain number. On input, DNS hostnames and symbolic port names are
261 permitted; if omitted, the default port 4070 is used. Name resolution
262 does not block the main server, but will block the requesting client,
263 unless the command is run in the background.
265 If, on input, no recognized address family token is found, the following
266 tokens are assumed to represent an
268 address. Addresses output by the server always have an address family
270 .SS "Key-value output"
275 produce output in the form of
277 pairs, one per token. Neither the
283 Commands which enable or disable kinds of output (e.g.,
287 work in similar ways. They take a single optional argument, which
288 consists of a string of letters selecting message types, optionally
293 to disable, the subsequently listed types.
295 If the argument is omitted, the available message types are displayed,
298 line, in a fixed-column format. Column zero contains the key letter for
299 selecting that message type; column one contains either a space or a
301 sign, if the message type is disabled or enabled respectively; and a
302 textual description of the message type begins at column 3 and continues
303 to the end of the line.
305 Lowercase key letters control individual message types. Uppercase key
306 letters control collections of message types.
308 .\"--------------------------------------------------------------------------
309 .SH "COMMAND REFERENCE"
312 The commands provided are:
314 .BI "ADD \fR[" options "\fR] " peer " " address "\fR..."
315 Adds a new peer. The peer is given the name
317 the peer's public key is assumed to be in the file
319 (or whatever alternative file was specified in the
321 option on the command line). The
323 is the network address (see above for the format) at which the peer can
324 be contacted. The following options are recognized.
328 .BI "\-background " tag
329 Run the command in the background, using the given
333 Don't send an immediate challenge to the peer; instead, wait until it
334 sends us something before responding.
336 .BI "\-keepalive " time
337 Send a no-op packet if we've not sent a packet to the peer in the last
339 interval. This is useful for persuading port-translating firewalls to
340 believe that the `connection' is still active. The
342 is expressed as a nonnegative integer followed optionally by
348 for days, hours, minutes, or seconds respectively; if no suffix is
349 given, seconds are assumed.
354 to authenticate the peer. The default is to use the key tagged
358 The peer is a mobile device, and is likely to change address rapidly.
359 If a packet arrives from an unknown address, the server's usual response
360 is to log a warning and discard it. If the server knows of any mobile
361 peers, however, it will attempt to decrypt the packet using their keys,
362 and if one succeeds, the server will update its idea of the peer's
367 .BI "\-tunnel " tunnel
368 Use the named tunnel driver, rather than the default.
375 line reporting the IP address and port number stored for
379 Emits information about the cryptographic algorithms in use, in
380 key-value form. The keys are as follows.
384 Type of key-exchange group in use, currently either
389 .B kx-group-order-bits
390 Length of the group order, in bits. This gives an approximate measure
391 of the group strength.
394 Length of a group element, in bits. This may be useful when analyzing
398 The hash function in use, e.g.,
402 The mask-generating function in use, e.g.,
406 The size of the hash function's output, in octets.
409 The name of the bulk data cipher in use, e.g.,
413 The length of key used by the bulk data cipher, in octets.
416 The block size of the bulk data cipher, or zero if it's not based on a
420 The maximum amount of data to be encrypted using a single key. (A new
421 key exchange is instigated well before the limit is reached, in order to
422 allow for a seamless changeover of keys.)
425 The message authentication algorithm in use, e.g.,
426 .BR ripemd160-hmac ..
429 The length of the key used by the message authentication algorithm, in
433 The length of the message authentication tag, in octets.
435 The various sizes are useful, for example, when computing the MTU for a
438 is the MTU of the path to the peer, then the tunnel MTU should be
446 allowing 20 bytes of IP header, 8 bytes of UDP header, a packet type
447 octet, a four-octet sequence number, an IV, and a MAC tag.
451 Cancels the background job with the named
454 .BI "CHECKCHAL " challenge
455 Verifies a challenge as being one earlier issued by
457 and not previously either passed to
459 or in a greeting message.
462 Causes the server to disassociate itself from its terminal and become a
463 background task. This only works once. A warning is issued.
465 .BI "EPING \fR[" options "\fR] " peer
466 Sends an encrypted ping to the peer, and expects an encrypted response.
467 This checks that the peer is running (and not being impersonated), and
468 that it can encrypt and decrypt packets correctly. Options and
469 responses are the same as for the
474 Requests the server to begin a new key exchange with
479 Requests a challenge. The challenge is returned in an
481 line, as a base64-encoded string. See
484 .BI "GREET " peer " " challenge
485 Sends a greeting packet containing the
487 (base-64 encoded) to the named
489 The expectation is that this will cause the peer to recognize us and
490 begin a key-exchange.
493 Causes the server to emit an
495 line for each command it supports. Each line lists the command name,
496 followed by the names of the arguments. This may be helpful as a memory
497 aid for interactive use, or for program clients probing for features.
502 line containing the name of the network interface used to collect IP
503 packets which are to be encrypted and sent to
505 Used by configuration scripts so that they can set up routing tables
506 appropriately after adding new peers.
511 line giving the tag for each outstanding background job.
514 Causes the server to forget all about
516 All keys are destroyed, and no more packets are sent. No notification
517 is sent to the peer: if it's important that the peer be notified, you
518 must think of a way to do that yourself.
521 For each currently-known peer, an
523 line is written containing the peer's name, as given to
526 .BI "NOTIFY " tokens\fR...
529 notification to all interested administration clients.
532 Returns information about a peer, in key-value form. The following keys
537 The tunnel driver used for this peer.
540 The keepalive interval, in seconds, or zero if no keepalives are to be
544 The key tag being used for the peer, as passed to the
546 command. (You don't get a full key-id, since that might change while
547 the daemon's running.)
550 .BI "PING \fR[" options "\fR] " peer
551 Send a transport-level ping to the peer. The ping and its response are
552 not encrypted or authenticated. This command, possibly in conjunction
553 with tracing, is useful for ensuring that UDP packets are actually
554 flowing in both directions. See also the
560 line is printed describing the outcome:
563 .BI "ping-ok " millis
564 A response was received
566 after the ping was sent.
569 No response was received within the time allowed.
572 The peer was killed (probably by another admin connection) before a
573 response was received.
576 Options recognized for this command are:
580 .BI "\-background " tag
581 Run the command in the background, using the given
584 .BI "\-timeout " time
587 seconds before giving up on a response. The default is 5 seconds. The
589 is expressed as a nonnegative integer followed optionally by
595 for days, hours, minutes, or seconds respectively; if no suffix is
596 given, seconds are assumed.
603 line containing just the number of the UDP port used by the
605 server. If you've allowed your server to allocate a port dynamically,
606 this is how to find out which one it chose.
609 Instructs the server to recheck its keyring files. The server checks
610 these periodically anyway but it may be necessary to force a recheck,
611 for example after adding a new peer key.
614 Instructs the server to exit immediately. A warning is sent.
617 Returns information about the server, in the form of key-value pairs.
618 The following keys are used.
622 A keyword naming the implementation of the
624 server. The current implementation is called
628 The server's version number, as reported by
636 if the server has or hasn't (respectively) become a daemon.
639 .BI "SETIFNAME " peer " " new-name
640 Informs the server that the
642 tunnel-interface name has been changed to
644 This is useful if firewalling decisions are made based on interface
645 names: a setup script for a particular peer can change the name, and
646 then update the server's records so that they're accurate.
648 .BI "SVCCLAIM " service " " version
649 Attempts to claim the named
653 The claim is successful if the service is currently unclaimed, or if
654 a version earlier than
656 is provided; otherwise the command fails with the error
657 .BR "service-exists" .
659 .BI "SVCENSURE " service " \fR[" version \fR]
662 is provided, and (if specified) to at least the given
664 An error is reported if these conditions are not met; otherwise the
665 command succeeds silently.
667 .BI "SVCFAIL " jobid " " tokens \fR...
672 response to the service job with the given
676 as the reason for failure. The job is closed.
678 .BI "SVCINFO " jobid " " tokens \fR...
683 response to the service job with the given
687 as the info message. The job remains open.
690 Output a line of the form
697 for each service currently provided.
705 response to the service job with the given
709 .BI "SVCQUERY " service
712 lines in key-value format, describing the named
714 The following keys are used.
721 The service's version string.
724 .BI "SVCRELEASE " service
725 Announce that the client no longer wishes to provide the named
728 .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR...
729 Submit a job to the provider of the given
735 The following options are accepted.
739 .BI "\-background " tag
740 Run the command in the background, using the given
743 .BI "\-version " version
744 Ensure that at least the given
746 of the service is available before submitting the job.
753 lines, each containing one or more statistics in the form
754 .IB name = value \fR.
755 The statistics-gathering is experimental and subject to change.
757 .BR "TRACE " [\fIoptions\fP]
758 Selects trace outputs: see
760 above. Message types provided are:
763 Currently, the following tracing options are supported:
766 Tunnel events: reception of packets to be encrypted, and injection of
767 successfully-decrypted packets.
770 Peer management events: creation and destruction of peer attachments,
771 and arrival of messages.
774 Administration interface: acceptance of new connections, and handling of
775 the backgroud name-resolution required by the
780 Handling of symmetric keysets: creation and expiry of keysets, and
781 encryption and decryption of messages.
784 Key exchange: reception, parsing and emission of key exchange messages.
787 Key management: loading keys and checking for file modifications.
790 Display information about challenge issuing and verification.
793 Display contents of packets sent and received by the tunnel and/or peer
797 Display inputs, outputs and intermediate results of cryptographic
798 operations. This includes plaintext and key material. Use with
810 outputs provide extra detail for other outputs. Specifying
816 isn't useful; neither is specifying
827 For each available tunnel driver, an
829 line is printed giving its name.
832 Causes the server to emit an
834 line stating its software version, as two tokens: the server name, and
835 its version string. The server name
837 is reserved to the Straylight/Edgeware implementation.
839 .BR "WATCH " [\fIoptions\fP]
840 Enables or disables asynchronous broadcasts
841 .IR "for the current connection only" .
844 above. The default watch state for the connection the server opens
845 automatically on stdin/stdout is to show warnings and trace messages;
846 other connections show no asynchronous broadcast messages. (This is
847 done in order to guarantee that a program reading the server's stdout
848 does not miss any warnings.)
851 Message types provided are:
869 .BI "WARN " tokens\fR...
872 warning to all interested administration clients.
874 .\"--------------------------------------------------------------------------
877 .\"* 20 Error messages (FAIL codes)
882 messages are sent to clients as a result of errors during command
890 server is already running as a daemon.
892 .BI "bad-addr-syntax " message
893 (For commands accepting socket addresses.) The address couldn't be
896 .BI "bad-syntax " cmd " " message
897 (For any command.) The command couldn't be understood: e.g., the number
898 of arguments was wrong.
900 .BI "bad-time-spec " token
903 is not a valid time interval specification. Acceptable time
904 specifications are nonnegative integers followed optionally by
910 for days, hours, minutes, or seconds, respectively.
912 .BI "bad-trace-option " char
915 An unknown trace option was requested.
917 .BI "bad-watch-option " char
920 An unknown watch option was requested.
922 .BI "daemon-error " ecode " " message
925 An error occurred during the attempt to become a daemon, as reported by
928 .BI "invalid-port " number
931 The given port number is out of range.
933 .BI "not-service-provider " service
936 The invoking client is not the current provider of the named
938 and is therefore not allowed to release it.
940 .BI "peer-create-fail " peer
945 failed for some reason. A warning should have been emitted explaining
948 .BI "peer-addr-exists " address\fR...
951 There is already a peer with the given
954 .BI "peer-exists " peer
957 There is already a peer named
960 .B "ping-send-failed"
961 The attempt to send a ping packet failed, probably due to lack of
964 .BI "resolve-error " hostname
969 could not be resolved.
971 .BI "resolver-timeout " hostname
976 took too long to resolve.
978 .BI "service-exists " service " " version
981 Another client is already providing the stated
986 .BI "service-too-old " service " " version
995 is available, which does not meet the stated requirements.
997 .BI "tag-exists " tag
998 (For long-running commands.) The named
1000 is already the tag of an outstanding job.
1002 .BI "unknown-command " token
1007 .BI "unknown-jobid " jobid
1015 is not recognized as identifying an outstanding job. It may have just
1018 .BI "unknown-peer " name
1026 There is no peer called
1029 .BI "unknown-port " port
1034 couldn't be found in
1037 .BI "unknown-service " service
1046 is not recognized as the name of a client-provided service.
1048 .BI "unknown-tag " tag
1053 is not the tag for any outstanding background job. It may have just
1056 .\"--------------------------------------------------------------------------
1059 .\"* 30 Notification broadcasts (NOTE codes)
1060 The following notifications are sent to clients who request them.
1062 .BI "ADD " peer " " ifname " " address \fR...
1063 A new peer has been added. The peer's name is
1065 its tunnel is network interface
1067 and its network address is
1071 The server has forked off into the sunset and become a daemon.
1073 .BI "GREET " challenge " " address \fR...
1074 A valid greeting was received, with the given challenge (exactly as it
1087 finished successfully.
1092 has begun or restarted. If key exchange keeps failing, this message
1093 will be repeated periodically.
1095 .BI "NEWADDR " peer " " address
1098 IP address has been changed to
1101 .BI "NEWIFNAME " peer " " old-name " " new-name
1104 tunnel interface name has been changed from
1112 .BI "SVCCLAIM " service " " version
1115 is now available, at the stated
1118 .BI "SVCRELEASE " service
1121 is no longer available.
1123 .BI "USER " tokens\fR...
1124 An administration client issued a notification using the
1128 .\"--------------------------------------------------------------------------
1131 .\"* 40 Warning broadcasts (WARN codes)
1133 There are many possible warnings. They are categorized according to
1136 Many of these warnings report system errors. These are reported as a
1137 pair of tokens, described below as
1143 is a string of the form
1147 value of the error; the
1149 is the `human-readable' form of the message, as reported by
1151 .SS "ABORT warnings"
1152 These all indicate that the
1154 server has become unable to continue. If enabled, the server will dump
1155 core in its configuration directory.
1157 .BI "ABORT repeated-select-errors"
1158 The main event loop is repeatedly failing. If the server doesn't quit,
1159 it will probably waste all available CPU doing nothing.
1160 .SS "ADMIN warnings"
1161 These indicate a problem with the administration socket interface.
1163 .BI "ADMIN accept-error " ecode " " message
1164 There was an error while attempting to accept a connection from a new
1167 .BI "ADMIN client-write-error " ecode " " message
1168 There was an error sending data to a client. The connection to the
1169 client has been closed.
1171 These indicate errors in challenges, either in the
1173 command or in greeting packets.
1175 .B "CHAL impossible-challenge"
1176 The server hasn't issued any challenges yet. Quite how anyone else
1177 thought he could make one up is hard to imagine.
1179 .B "CHAL incorrect-tag"
1180 Challenge received contained the wrong authentication data. It might be
1181 very stale, or a forgery.
1183 .B "CHAL invalid-challenge"
1184 Challenge received was the wrong length. We might have changed MAC
1185 algorithms since the challenge was issued, or it might just be rubbish.
1187 .B "CHAL replay duplicated-sequence"
1188 Challenge received was a definite replay of an old challenge. Someone's
1191 .B "CHAL replay old-sequence"
1192 Challenge received was old, but maybe not actually a replay. Try again.
1193 .SS "KEYMGMT warnings"
1194 These indicate a problem with the keyring files, or the keys stored in
1197 .BI "KEYMGMT bad-private-key " message
1198 The private key could not be read, or failed a consistency check. If
1199 there was a problem with the file, usually there will have been
1201 warnings before this.
1203 .BI "KEYMGMT bad-public-keyring " message
1204 The public keyring couldn't be read. Usually, there will have been
1206 warnings before this.
1208 .BI "KEYMGMT key-file-error " file ":" line " " message
1209 Reports a specific error with the named keyring file. This probably
1213 .BI "KEYMGMT public-key " tag " " tokens\fR...
1214 These messages all indicate a problem with the public key named
1217 .BI "KEYMGMT public-key " tag " algorithm-mismatch"
1218 The algorithms specified on the public key don't match the ones for our
1219 private key. All the peers in a network have to use the same
1222 .BI "KEYMGMT public-key " tag " bad " message
1223 The public key couldn't be read, or is invalid.
1225 .BI "KEYMGMT public-key " tag " bad-public-group-element"
1226 The public key is invalid. This may indicate a malicious attempt to
1227 introduce a bogus key.
1229 .BI "KEYMGMT public-key " tag " bad-algorithm-selection"
1230 The algorithms listed on the public key couldn't be understood. The
1231 algorithm selection attributes are probably malformed and need fixing.
1233 .BI "KEYMGMT public-key " tag " incorrect-group"
1234 The public key doesn't use the same group as our private key. All the
1235 peers in a network have to use the same group.
1237 .BI "KEYMGMT public-key " tag " not-found"
1238 The public key for peer
1240 wasn't in the public keyring.
1242 .BI "KEYMGMT public-key " tag " unknown-type"
1243 The type of the public key isn't understood. Maybe you need to upgrade
1246 (Even if you do, you'll have to regenerate your keys.)
1248 These indicate problems during key-exchange. Many indicate either a bug
1249 in the server (either yours or the remote one), or some kind of attack
1250 in progress. All name a
1252 as the second token: this is the peer the packet is apparently from,
1253 though it may have been sent by an attacker instead.
1255 In the descriptions below,
1257 is one of the tokens
1266 .BI "KX " peer " bad-expected-reply-log"
1269 uses in its protocol contain a check value which proves that the
1270 challenge is honest. This message indicates that the check value
1271 supplied is wrong: someone is attempting to use bogus challenges to
1274 server to leak private key information. No chance!
1276 .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok"
1277 A symmetrically-encrypted portion of a key-exchange message failed to
1280 .BI "KX " peer " invalid " msgtoken
1281 A key-exchange message was malformed. This almost certainly indicates a
1284 .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok"
1285 A message didn't contain the right magic data. This may be a replay of
1286 some old exchange, or random packets being sent in an attempt to waste
1289 .BI "KX " peer " public-key-expired"
1290 The peer's public key has expired. It's maintainer should have given
1291 you a replacement before now.
1293 .BI "KX " peer " sending-cookie"
1294 We've received too many bogus pre-challenge messages. Someone is trying
1295 to flood us with key-exchange messages and make us waste CPU on doing
1296 hard asymmetric crypto sums.
1298 .BI "KX " peer " unexpected " msgtoken
1299 The message received wasn't appropriate for this stage of the key
1300 exchange process. This may mean that one of our previous packets got
1303 it may simply mean that the peer has recently restarted.
1305 .BI "KX " peer " unknown-challenge"
1306 The peer is asking for an answer to a challenge which we don't know
1307 about. This may mean that we've been inundated with challenges from
1308 some malicious source
1309 .I who can read our messages
1310 and discarded the valid one.
1312 .BI "KX " peer " unknown-message 0x" nn
1313 An unknown key-exchange message arrived.
1315 These are largely concerned with management of peers and the low-level
1316 details of the network protocol. The second token is usually the name of
1319 if none is relevant.
1321 .BI "PEER " peer " bad-packet no-type"
1322 An empty packet arrived. This is very strange.
1324 .BI "PEER " peer " bad-packet unknown-category 0x" nn
1325 The message category
1327 (in hex) isn't understood. Probably a strange random packet from
1328 somewhere; could be an unlikely bug.
1330 .BI "PEER " peer " bad-packet unknown-type 0x" nn
1333 (in hex) isn't understood. Probably a strange random packet from
1334 somewhere; could be an unlikely bug.
1336 .BI "PEER " peer " corrupt-encrypted-ping"
1337 The peer sent a ping response which matches an outstanding ping, but its
1338 payload is wrong. There's definitely a bug somewhere.
1340 .BI "PEER " peer " corrupt-transport-ping"
1341 The peer (apparently) sent a ping response which matches an outstanding
1342 ping, but its payload is wrong. Either there's a bug, or the bad guys
1343 are playing tricks on you.
1345 .BI "PEER " peer " decrypt-failed"
1346 An encrypted IP packet failed to decrypt. It may have been mangled in
1347 transit, or may be a very old packet from an expired previous session
1348 key. There is usually a considerable overlap in the validity periods of
1349 successive session keys, so this shouldn't occur unless the key exchange
1350 takes ages or fails.
1352 .BI "PEER " peer " malformed-encrypted-ping"
1353 The peer sent a ping response which is hopelessly invalid. There's
1354 definitely a bug somewhere.
1356 .BI "PEER " peer " malformed-transport-ping"
1357 The peer (apparently) sent a ping response which is hopelessly invalid.
1358 Either there's a bug, or the bad guys are playing tricks on you.
1360 .BI "PEER " peer " packet-build-failed"
1361 There wasn't enough space in our buffer to put the packet we wanted to
1362 send. Shouldn't happen.
1364 .BI "PEER \- socket-read-error " ecode " " message
1365 An error occurred trying to read an incoming packet.
1367 .BI "PEER " peer " socket-write-error " ecode " " message
1368 An error occurred attempting to send a network packet. We lost that
1371 .BI "PEER " peer " unexpected-encrypted-ping 0x" id
1372 The peer sent an encrypted ping response whose id doesn't match any
1373 outstanding ping. Maybe it was delayed for longer than the server was
1374 willing to wait, or maybe the peer has gone mad.
1376 .BI "PEER \- unexpected-source " address\fR...
1377 A packet arrived from
1379 (a network address \(en see above), but no peer is known at that
1380 address. This may indicate a misconfiguration, or simply be a result of
1381 one end of a connection being set up before the other.
1383 .BI "PEER " peer " unexpected-transport-ping 0x" id
1384 The peer (apparently) sent a transport ping response whose id doesn't
1385 match any outstanding ping. Maybe it was delayed for longer than the
1386 server was willing to wait, or maybe the peer has gone mad; or maybe
1387 there are bad people trying to confuse you.
1388 .SS "SERVER warnings"
1389 These indicate problems concerning the server process as a whole.
1391 .BI "SERVER ignore signal " name
1392 A signal arrived, but the server ignored it. Currently this happens for
1394 because that's a popular way of telling daemons to re-read their
1395 configuration files. Since
1397 re-reads its keyrings automatically and has no other configuration
1398 files, it's not relevant, but it seemed better to ignore the signal than
1401 .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR]
1402 A signal arrived and
1406 .BI "SERVER quit admin-request"
1407 A client of the administration interface issued a
1411 .BI "SERVER quit foreground-eof"
1412 The server is running in foreground mode (the
1414 option), and encountered end-of-file on standard input.
1416 .BI "SERVER select-error " ecode " " message
1417 An error occurred in the server's main event loop. This is bad: if it
1418 happens too many times, the server will abort.
1420 These are concerned with the symmetric encryption and decryption
1423 .BI "SYMM replay old-sequence"
1424 A packet was received with an old sequence number. It may just have
1425 been delayed or duplicated, or it may have been an attempt at a replay
1428 .BI "SYMM replay duplicated-sequence"
1429 A packet was received with a sequence number we've definitely seen
1430 before. It may be an accidental duplication because the 'net is like
1431 that, or a deliberate attempt at a replay.
1433 These concern the workings of the system-specific tunnel driver. The
1434 second token is the name of the tunnel interface in question, or
1438 .BI "TUN \- bsd no-tunnel-devices"
1439 The driver couldn't find an available tunnel device. Maybe if you
1442 files, it will work.
1444 .BI "TUN \- " tun-name " open-error " device " " ecode " " message
1445 An attempt to open the tunnel device file
1449 .BI "TUN \- linux config-error " ecode " " message
1450 Configuring the Linux TUN/TAP interface failed.
1452 .BI "TUN " ifname " " tun-name " read-error " ecode " " message
1453 Reading from the tunnel device failed.
1455 .BI "TUN " ifname " " tun-name " write-error " ecode " " message
1456 Writing from the tunnel device failed.
1458 .BI "TUN " ifname " slip bad-escape"
1459 The SLIP driver encountered a escaped byte it wasn't expecting to see.
1460 The erroneous packet will be ignored.
1462 .BI "TUN " ifname " slip eof"
1463 The SLIP driver encountered end-of-file on its input descriptor.
1464 Pending data is discarded, and no attempt is made to read any more data
1465 from that interface ever.
1467 .BI "TUN " ifname " slip escape-end"
1468 The SLIP driver encountered an escaped `end' marker. This probably
1469 means that someone's been sending it junk. The erroneous packet is
1470 discarded, and we hope that we've rediscovered synchronization.
1472 .BI "TUN \- slip fork-error " ecode " " message
1473 The SLIP driver encountered an error forking a child process while
1474 allocating a new dynamic interface.
1476 .BI "TUN \- slip no-slip-interfaces"
1477 The driver ran out of static SLIP interfaces. Either preallocate more,
1478 or use dynamic SLIP interface allocation.
1480 .BI "TUN " ifname " slip overflow"
1481 The SLIP driver gave up reading a packet because it got too large.
1483 .BI "TUN \- slip pipe-error " ecode " " message
1484 The SLIP driver encountered an error creating pipes while allocating a
1485 new dynamic interface.
1487 .BI "TUN \- slip read-ifname-failed " ecode " " message
1488 The SLIP driver encountered an error reading the name of a dynamically
1489 allocated interface. Maybe the allocation script is broken.
1491 .BI "TUN \- unet config-error " ecode " " message
1492 Configuring the Linux Unet interface failed. Unet is obsolete and
1493 shouldn't be used any more.
1495 .BI "TUN \- unet getinfo-error " ecode " " message
1496 Reading information about the Unet interface failed. Unet is obsolete
1497 and shouldn't be used any more.
1499 These are issued by administration clients using the
1503 .BI "USER " tokens\fR...
1504 An administration client issued a warning.
1507 .\"--------------------------------------------------------------------------
1510 .SS "Command responses"
1513 .BI "BGFAIL " tag " " tokens \fR...
1514 .BI "BGINFO " tag " " tokens \fR...
1516 .BI "FAIL " tokens \fR...
1517 .BI "INFO " tokens \fR...
1522 .\"--------------------------------------------------------------------------
1528 .IR "The Trivial IP Encryption Protocol" .
1530 .\"--------------------------------------------------------------------------
1533 Mark Wooding, <mdw@distorted.org.uk>
1535 .\"----- That's all, folks --------------------------------------------------
~mdw / tripe / blob