12 .TH tripe-admin 5 "18 February 2001" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
14 tripe-admin \- administrator commands for TrIPE
16 This manual page describes the administration interface provided by the
22 program can be used either interactively or in scripts to communicate
23 with the server using this interface. Alternatively, simple custom
24 clients can be written in scripting languages such as Perl, Python or
25 Tcl, or more advanced clients such as GUI monitors can be written in C
26 with little difficulty.
28 Administration commands use a textual protocol. Each client command or
29 server response consists of a line of ASCII text terminated by a single
30 linefeed character. No command may be longer than 255 characters.
31 .SS "General structure"
32 Each command or response line consists of a sequence of
33 whitespace-separated words. The number and nature of whitespace
34 characters separating two words in a client command is not significant;
35 the server always uses a single space character. The first word in a
38 identifying the type of command or response contained. Keywords in
39 client commands are not case-sensitive; the server always uses uppercase
42 For simple client command, the server responds with zero or more
44 lines, followed by either an
50 provides information requested in the command. An
52 response contains no further data. A
54 code is followed by a machine-readable explanation of why the command
57 Simple command processing is strictly synchronous: the server reads a
58 command, processes it, and responds, before reading the next command.
59 All commands can be run as simple commands. Long-running commands
64 block the client until they finish, but the rest of the server continues
66 .B "Background commands"
67 to find out how to issue long-running commands without blocking.
68 .SS "Asynchronous broadcasts"
69 There are three types of asynchronous broadcast messages which aren't
70 associated with any particular command. Clients can select which
71 broadcast messages they're interested in using the
77 message contains a machine-readable message warning of an error
78 encountered while processing a command, unexpected or unusual behaviour
79 by a peer, or a possible attack by an adversary. Under normal
80 conditions, the server shouldn't emit any warnings.
84 message contains a human-readable tracing message containing diagnostic
85 information. Trace messages are controlled using the
87 command-line option to the server, or the
89 administration command (see below). Support for tracing can be disabled
90 when the package is being configured, and may not be available in your
95 message is a machine-readable notification about some routine but
96 interesting event such as creation or destruction of peers.
97 .SS "Background commands"
102 take a long time to complete. To prevent these long-running commands
103 from tying up a server connection, they can be run in the background.
104 Not all commands can be run like this: the ones that can provide a
106 option, which must be supplied with a
109 A command may fail before it starts running in the background. In this
110 case, the server emits a
112 response, as usual. To indicate that a command has started running in
113 the background, the server emits a response of the form
114 .BI "BGDETACH " tag \fR,
117 is the value passed to the
119 option. From this point on, the server is ready to process more
120 commands and reply to them.
122 Responses to background commands are indicated by a line beginning with
128 followed by the command tag. These correspond to the
133 responses for simple commands:
135 indicates information from a background command which has not completed
140 indicates that a background command succeeded or failed, respectively.
142 A background command will never issue an
146 response: it will always detach and then issue any
151 .SS "Client-provided services"
152 .\"* 25 Service-related messages
153 An administration client can provide services to other clients.
154 Services are given names and versions. A client can attempt to
156 a particular service by issuing the
158 command. This may fail, for example, if some other client already
159 provides the same or later version of the service.
161 Other clients can issue
162 .I "service commands"
165 command; the service provider is expected to handle these commands and
168 There are three important asynchronous messages which will be sent to
171 .BI "SVCCANCEL " jobid
172 The named job has been cancelled, either because the issuing client has
173 disconnected or explicitly cancelled the job using the
177 .BI "SVCCLAIM " service " " version
178 Another client has claimed a later version of the named
179 .I service. The recipient is no longer the provider of this service.
181 .BI "SVCJOB " jobid " " service " " command " " args \fR...
182 Announces the arrival of a new job. The
184 is a simple token consisting of alphanumeric characters which
186 uses to identify this job.
188 The service provider can reply to the job using the commands
193 The first of these sends an
195 response and leaves the job active; the other two send an
199 response respectively, and mark the job as being complete.
203 is a potentially long-running command, it can be run in the background.
204 This detail is hidden from service providers:
206 will issue the corresponding
208 responses when appropriate.)
209 .SS "Network addresses"
210 A network address is a sequence of words. The first is a token
211 identifying the network address family. The length of an address and
212 the meanings of the subsequent words depend on the address family.
213 Address family tokens are not case-sensitive on input; on output, they
214 are always in upper-case.
216 At present, only one address family is understood.
218 .BI "INET " address " \fR[" port \fR]
219 An Internet socket, naming an IPv4 address and UDP port. On output, the
220 address is always in numeric dotted-quad form, and the port is given as
221 a plain number. On input, DNS hostnames and symbolic port names are
222 permitted; if omitted, the default port 4070 is used. Name resolution
223 does not block the main server, but will block the requesting client,
224 unless the command is run in the background.
226 If, on input, no recognised address family token is found, the following
227 words are assumed to represent an
229 address. Addresses output by the server always have an address family
231 .SS "Key-value output"
236 produce output in the form of
238 pairs, one per word. Neither the
244 Commands which enable or disable kinds of output (e.g.,
248 work in similar ways. They take a single optional argument, which
249 consists of a string of letters selecting message types, optionally
254 to disable, the subsequently listed types.
256 If the argument is omitted, the available message types are displayed,
259 line, in a fixed-column format. Column zero contains the key letter for
260 selecting that message type; column one contains either a space or a
262 sign, if the message type is disabled or enabled respectively; and a
263 textual description of the message type begins at column 3 and continues
264 to the end of the line.
266 Lowercase key letters control individual message types. Uppercase key
267 letters control collections of message types.
268 .SH "COMMAND REFERENCE"
270 The commands provided are:
272 .BI "ADD \fR[" options "\fR] " peer " " address "\fR..."
273 Adds a new peer. The peer is given the name
275 the peer's public key is assumed to be in the file
277 (or whatever alternative file was specified in the
279 option on the command line). The
281 is the network address (see above for the format) at which the peer can
282 be contacted. The following options are recognised.
286 .BI "\-background " tag
287 Run the command in the background, using the given
291 Don't send an immediate challenge to the peer; instead, wait until it
292 sends us something before responding.
294 .BI "\-keepalive " time
295 Send a no-op packet if we've not sent a packet to the peer in the last
297 interval. This is useful for persuading port-translating firewalls to
298 believe that the `connection' is still active. The
300 is expressed as a nonnegative integer followed optionally by
306 for days, hours, minutes, or seconds respectively; if no suffix is
307 given, seconds are assumed.
309 .BI "\-tunnel " tunnel
310 Use the named tunnel driver, rather than the default.
317 line reporting the IP address and port number stored for
321 Cancels the background job with the named
324 .BI "CHECKCHAL " challenge
325 Verifies a challenge as being one earlier issued by
327 and not previously either passed to
329 or in a greeting message.
332 Causes the server to disassociate itself from its terminal and become a
333 background task. This only works once. A warning is issued.
335 .BI "EPING \fR[" options "\fR] " peer
336 Sends an encrypted ping to the peer, and expects an encrypted response.
337 This checks that the peer is running (and not being impersonated), and
338 that it can encrypt and decrypt packets correctly. Options and
339 responses are the same as for the
344 Requests the server to begin a new key exchange with
349 Requests a challenge. The challenge is returned in an
351 line, as a base64-encoded string. See
354 .BI "GREET " peer " " challenge
355 Sends a greeting packet containing the
357 (base-64 encoded) to the named
359 The expectation is that this will cause the peer to recognize us and
360 begin a key-exchange.
363 Causes the server to emit an
365 line for each command it supports. Each line lists the command name,
366 followed by the names of the arguments. This may be helpful as a memory
367 aid for interactive use, or for program clients probing for features.
372 line containing the name of the network interface used to collect IP
373 packets which are to be encrypted and sent to
375 Used by configuration scripts so that they can set up routing tables
376 appropriately after adding new peers.
381 line giving the tag for each outstanding background job.
384 Causes the server to forget all about
386 All keys are destroyed, and no more packets are sent. No notification
387 is sent to the peer: if it's important that the peer be notified, you
388 must think of a way to do that yourself.
391 For each currently-known peer, an
393 line is written containing the peer's name, as given to
396 .BI "NOTIFY " tokens\fR...
399 notification to all interested administration clients.
402 Returns information about a peer, in key-value form. The following keys
407 The tunnel driver used for this peer.
410 The keepalive interval, in seconds, or zero if no keepalives are to be
414 .BI "PING \fR[" options "\fR] " peer
415 Send a transport-level ping to the peer. The ping and its response are
416 not encrypted or authenticated. This command, possibly in conjunction
417 with tracing, is useful for ensuring that UDP packets are actually
418 flowing in both directions. See also the
424 line is printed describing the outcome:
427 .BI "ping-ok " millis
428 A response was received
430 after the ping was sent.
433 No response was received within the time allowed.
436 The peer was killed (probably by another admin connection) before a
437 response was received.
440 Options recognized for this command are:
444 .BI "\-background " tag
445 Run the command in the background, using the given
448 .BI "\-timeout " time
451 seconds before giving up on a response. The default is 5 seconds. The
453 is expressed as a nonnegative integer followed optionally by
459 for days, hours, minutes, or seconds respectively; if no suffix is
460 given, seconds are assumed.
467 line containing just the number of the UDP port used by the
469 server. If you've allowed your server to allocate a port dynamically,
470 this is how to find out which one it chose.
473 Instructs the server to recheck its keyring files. The server checks
474 these periodically anyway but it may be necessary to force a recheck,
475 for example after adding a new peer key.
478 Instructs the server to exit immediately. A warning is sent.
481 Returns information about the server, in the form of key-value pairs.
482 The following keys are used.
486 A keyword naming the implementation of the
488 server. The current implementation is called
492 The server's version number, as reported by
500 if the server has or hasn't (respectively) become a daemon.
503 .BI "SETIFNAME " peer " " new-name
504 Informs the server that the
506 tunnel-interface name has been changed to
508 This is useful if firewalling decisions are made based on interface
509 names: a setup script for a particular peer can change the name, and
510 then update the server's records so that they're accurate.
512 .BI "SVCCLAIM " service " " version
513 Attempts to claim the named
517 The claim is successful if the service is currently unclaimed, or if
518 a version earlier than
520 is provided; otherwise the command fails with the error
521 .BR "service-exists" .
523 .BI "SVCENSURE " service " \fR[" version \fR]
526 is provided, and (if specified) to at least the given
528 An error is reported if these conditions are not met; otherwise the
529 command succeeds silently.
531 .BI "SVCFAIL " jobid " " tokens \fR...
536 response to the service job with the given
540 as the reason for failure. The job is closed.
542 .BI "SVCINFO " jobid " " tokens \fR...
547 response to the service job with the given
551 as the info message. The job remains open.
554 Output a line of the form
561 for each service currently provided.
569 response to the service job with the given
573 .BI "SVCQUERY " service
576 lines in key-value format, describing the named
578 The following keys are used.
585 The service's version string.
588 .BI "SVCRELEASE " service
589 Announce that the client no longer wishes to provide the named
592 .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR...
593 Submit a job to the provider of the given
599 The following options are accepted.
603 .BI "\-background " tag
604 Run the command in the background, using the given
607 .BI "\-version " version
608 Ensure that at least the given
610 of the service is available before submitting the job.
617 lines, each containing one or more statistics in the form
618 .IB name = value \fR.
619 The statistics-gathering is experimental and subject to change.
621 .BR "TRACE " [\fIoptions\fP]
622 Selects trace outputs: see
624 above. Message types provided are:
627 Currently, the following tracing options are supported:
630 Tunnel events: reception of packets to be encrypted, and injection of
631 successfully-decrypted packets.
634 Peer management events: creation and destruction of peer attachments,
635 and arrival of messages.
638 Administration interface: acceptance of new connections, and handling of
639 the backgroud name-resolution required by the
644 Handling of symmetric keysets: creation and expiry of keysets, and
645 encryption and decryption of messages.
648 Key exchange: reception, parsing and emission of key exchange messages.
651 Key management: loading keys and checking for file modifications.
654 Display information about challenge issuing and verification.
657 Display contents of packets sent and received by the tunnel and/or peer
661 Display inputs, outputs and intermediate results of cryptographic
662 operations. This includes plaintext and key material. Use with
674 outputs provide extra detail for other outputs. Specifying
680 isn't useful; neither is specifying
691 For each available tunnel driver, an
693 line is printed giving its name.
696 Causes the server to emit an
698 line stating its software version, as two words: the server name, and
699 its version string. The server name
701 is reserved to the Straylight/Edgeware implementation.
703 .BR "WATCH " [\fIoptions\fP]
704 Enables or disables asynchronous broadcasts
705 .IR "for the current connection only" .
708 above. The default watch state for the connection the server opens
709 automatically on stdin/stdout is to show warnings and trace messages;
710 other connections show no asynchronous broadcast messages. (This is
711 done in order to guarantee that a program reading the server's stdout
712 does not miss any warnings.)
715 Message types provided are:
733 .BI "WARN " tokens\fR...
736 warning to all interested administration clients.
738 .\"* 20 Error messages (FAIL codes)
743 messages are sent to clients as a result of errors during command
751 server is already running as a daemon.
753 .BI "bad-addr-syntax " message
754 (For commands accepting socket addresses.) The address couldn't be
757 .BI "bad-syntax " cmd " " message
758 (For any command.) The command couldn't be understood: e.g., the number
759 of arguments was wrong.
761 .BI "bad-time-spec " word
764 is not a valid time interval specification. Acceptable time
765 specifications are nonnegative integers followed optionally by
771 for days, hours, minutes, or seconds, respectively.
773 .BI "bad-trace-option " char
776 An unknown trace option was requested.
778 .BI "bad-watch-option " char
781 An unknown watch option was requested.
783 .BI "daemon-error " ecode " " message
786 An error occurred during the attempt to become a daemon, as reported by
789 .BI "invalid-port " number
792 The given port number is out of range.
794 .BI "not-service-provider " service
797 The invoking client is not the current provider of the named
799 and is therefore not allowed to release it.
801 .BI "peer-create-fail " peer
806 failed for some reason. A warning should have been emitted explaining
809 .BI "peer-exists " peer
812 There is already a peer named
815 .B "ping-send-failed"
816 The attempt to send a ping packet failed, probably due to lack of
819 .BI "resolve-error " hostname
824 could not be resolved.
826 .BI "resolver-timeout " hostname
831 took too long to resolve.
833 .BI "service-exists " service " " version
836 Another client is already providing the stated
841 .BI "service-too-old " service " " version
850 is available, which does not meet the stated requirements.
852 .BI "tag-exists " tag
853 (For long-running commands.) The named
855 is already the tag of an outstanding job.
857 .BI "unknown-command " token
862 .BI "unknown-peer " name
870 There is no peer called
873 .BI "unknown-port " port
881 .BI "unknown-service " service
890 is not recognized as the name of a client-provided service.
892 .BI "unknown-tag " tag
897 is not the tag for any outstanding background job. It may have just
900 .\"* 30 Notification broadcasts (NOTE codes)
901 The following notifications are sent to clients who request them.
903 .BI "ADD " peer " " ifname " " address \fR...
904 A new peer has been added. The peer's name is
906 its tunnel is network interface
908 and its network address is
912 The server has forked off into the sunset and become a daemon.
914 .BI "GREET " challenge " " address \fR...
915 A valid greeting was received, with the given challenge (exactly as it
928 finished successfully.
933 has begun or restarted. If key exchange keeps failing, this message
934 will be repeated periodically.
936 .BI "NEWIFNAME " peer " " old-name " " new-name
939 tunnel interface name has been changed from
947 .BI "SVCCLAIM " service " " version
950 is now available, at the stated
953 .BI "SVCRELEASE " service
956 is no longer available.
958 .BI "USER " tokens\fR...
959 An administration client issued a notification using the
963 .\"* 40 Warning broadcasts (WARN codes)
965 There are many possible warnings. They are categorized according to
968 Many of these warnings report system errors. These are reported as a
969 pair of tokens, described below as
975 is a string of the form
979 value of the error; the
981 is the `human-readable' form of the message, as reported by
984 These all indicate that the
986 server has become unable to continue. If enabled, the server will dump
987 core in its configuration directory.
989 .BI "ABORT repeated-select-errors"
990 The main event loop is repeatedly failing. If the server doesn't quit,
991 it will probably waste all available CPU doing nothing.
993 These indicate a problem with the administration socket interface.
995 .BI "ADMIN accept-error " ecode " " message
996 There was an error while attempting to accept a connection from a new
999 .BI "ADMIN client-write-error " ecode " " message
1000 There was an error sending data to a client. The connection to the
1001 client has been closed.
1003 These indicate errors in challenges, either in the
1005 command or in greeting packets.
1007 .B "CHAL impossible-challenge"
1008 The server hasn't issued any challenges yet. Quite how anyone else
1009 thought he could make one up is hard to imagine.
1011 .B "CHAL incorrect-tag"
1012 Challenge received contained the wrong authentication data. It might be
1013 very stale, or a forgery.
1015 .B "CHAL invalid-challenge"
1016 Challenge received was the wrong length. We might have changed MAC
1017 algorithms since the challenge was issued, or it might just be rubbish.
1019 .B "CHAL replay duplicated-sequence"
1020 Challenge received was a definite replay of an old challenge. Someone's
1023 .B "CHAL replay old-sequence"
1024 Challenge received was old, but maybe not actually a replay. Try again.
1025 .SS "KEYMGMT warnings"
1026 These indicate a problem with the keyring files, or the keys stored in
1029 .BI "KEYMGMT bad-private-key " message
1030 The private key could not be read, or failed a consistency check. If
1031 there was a problem with the file, usually there will have been
1033 warnings before this.
1035 .BI "KEYMGMT bad-public-keyring " message
1036 The public keyring couldn't be read. Usually, there will have been
1038 warnings before this.
1040 .BI "KEYMGMT key-file-error " file ":" line " " message
1041 Reports a specific error with the named keyring file. This probably
1045 .BI "KEYMGMT public-key " tag " " tokens\fR...
1046 These messages all indicate a problem with the public key named
1049 .BI "KEYMGMT public-key " tag " algorithm-mismatch"
1050 The algorithms specified on the public key don't match the ones for our
1051 private key. All the peers in a network have to use the same
1054 .BI "KEYMGMT public-key " tag " bad " message
1055 The public key couldn't be read, or is invalid.
1057 .BI "KEYMGMT public-key " tag " bad-public-group-element"
1058 The public key is invalid. This may indicate a malicious attempt to
1059 introduce a bogus key.
1061 .BI "KEYMGMT public-key " tag " bad-algorithm-selection"
1062 The algorithms listed on the public key couldn't be understood. The
1063 algorithm selection attributes are probably malformed and need fixing.
1065 .BI "KEYMGMT public-key " tag " incorrect-group"
1066 The public key doesn't use the same group as our private key. All the
1067 peers in a network have to use the same group.
1069 .BI "KEYMGMT public-key " tag " not-found"
1070 The public key for peer
1072 wasn't in the public keyring.
1074 .BI "KEYMGMT public-key " tag " unknown-type"
1075 The type of the public key isn't understood. Maybe you need to upgrade
1078 (Even if you do, you'll have to regenerate your keys.)
1080 These indicate problems during key-exchange. Many indicate either a bug
1081 in the server (either yours or the remote one), or some kind of attack
1082 in progress. All name a
1084 as the second token: this is the peer the packet is apparently from,
1085 though it may have been sent by an attacker instead.
1087 In the descriptions below,
1089 is one of the tokens
1098 .BI "KX " peer " bad-expected-reply-log"
1101 uses in its protocol contain a check value which proves that the
1102 challenge is honest. This message indicates that the check value
1103 supplied is wrong: someone is attempting to use bogus challenges to
1106 server to leak private key information. No chance!
1108 .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok"
1109 A symmetrically-encrypted portion of a key-exchange message failed to
1112 .BI "KX " peer " invalid " msgtoken
1113 A key-exchange message was malformed. This almost certainly indicates a
1116 .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok"
1117 A message didn't contain the right magic data. This may be a replay of
1118 some old exchange, or random packets being sent in an attempt to waste
1121 .BI "KX " peer " public-key-expired"
1122 The peer's public key has expired. It's maintainer should have given
1123 you a replacement before now.
1125 .BI "KX " peer " sending-cookie"
1126 We've received too many bogus pre-challenge messages. Someone is trying
1127 to flood us with key-exchange messages and make us waste CPU on doing
1128 hard asymmetric crypto sums.
1130 .BI "KX " peer " unexpected " msgtoken
1131 The message received wasn't appropriate for this stage of the key
1132 exchange process. This may mean that one of our previous packets got
1135 it may simply mean that the peer has recently restarted.
1137 .BI "KX " peer " unknown-challenge"
1138 The peer is asking for an answer to a challenge which we don't know
1139 about. This may mean that we've been inundated with challenges from
1140 some malicious source
1141 .I who can read our messages
1142 and discarded the valid one.
1144 .BI "KX " peer " unknown-message 0x" nn
1145 An unknown key-exchange message arrived.
1147 These are largely concerned with management of peers and the low-level
1148 details of the network protocol. The second word is usually the name of
1151 if none is relevant.
1153 .BI "PEER " peer " bad-packet no-type"
1154 An empty packet arrived. This is very strange.
1156 .BI "PEER " peer " bad-packet unknown-category 0x" nn
1157 The message category
1159 (in hex) isn't understood. Probably a strange random packet from
1160 somewhere; could be an unlikely bug.
1162 .BI "PEER " peer " bad-packet unknown-type 0x" nn
1165 (in hex) isn't understood. Probably a strange random packet from
1166 somewhere; could be an unlikely bug.
1168 .BI "PEER " peer " corrupt-encrypted-ping"
1169 The peer sent a ping response which matches an outstanding ping, but its
1170 payload is wrong. There's definitely a bug somewhere.
1172 .BI "PEER " peer " corrupt-transport-ping"
1173 The peer (apparently) sent a ping response which matches an outstanding
1174 ping, but its payload is wrong. Either there's a bug, or the bad guys
1175 are playing tricks on you.
1177 .BI "PEER " peer " decrypt-failed"
1178 An encrypted IP packet failed to decrypt. It may have been mangled in
1179 transit, or may be a very old packet from an expired previous session
1180 key. There is usually a considerable overlap in the validity periods of
1181 successive session keys, so this shouldn't occur unless the key exchange
1182 takes ages or fails.
1184 .BI "PEER " peer " malformed-encrypted-ping"
1185 The peer sent a ping response which is hopelessly invalid. There's
1186 definitely a bug somewhere.
1188 .BI "PEER " peer " malformed-transport-ping"
1189 The peer (apparently) sent a ping response which is hopelessly invalid.
1190 Either there's a bug, or the bad guys are playing tricks on you.
1192 .BI "PEER " peer " packet-build-failed"
1193 There wasn't enough space in our buffer to put the packet we wanted to
1194 send. Shouldn't happen.
1196 .BI "PEER \- socket-read-error " ecode " " message
1197 An error occurred trying to read an incoming packet.
1199 .BI "PEER " peer " socket-write-error " ecode " " message
1200 An error occurred attempting to send a network packet. We lost that
1203 .BI "PEER " peer " unexpected-encrypted-ping 0x" id
1204 The peer sent an encrypted ping response whose id doesn't match any
1205 outstanding ping. Maybe it was delayed for longer than the server was
1206 willing to wait, or maybe the peer has gone mad.
1208 .BI "PEER \- unexpected-source " address\fR...
1209 A packet arrived from
1211 (a network address \(en see above), but no peer is known at that
1212 address. This may indicate a misconfiguration, or simply be a result of
1213 one end of a connection being set up before the other.
1215 .BI "PEER " peer " unexpected-transport-ping 0x" id
1216 The peer (apparently) sent a transport ping response whose id doesn't
1217 match any outstanding ping. Maybe it was delayed for longer than the
1218 server was willing to wait, or maybe the peer has gone mad; or maybe
1219 there are bad people trying to confuse you.
1220 .SS "SERVER warnings"
1221 These indicate problems concerning the server process as a whole.
1223 .BI "SERVER ignore signal " name
1224 A signal arrived, but the server ignored it. Currently this happens for
1226 because that's a popular way of telling daemons to re-read their
1227 configuration files. Since
1229 re-reads its keyrings automatically and has no other configuration
1230 files, it's not relevant, but it seemed better to ignore the signal than
1233 .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR]
1234 A signal arrived and
1238 .BI "SERVER quit admin-request"
1239 A client of the administration interface issued a
1243 .BI "SERVER select-error " ecode " " message
1244 An error occurred in the server's main event loop. This is bad: if it
1245 happens too many times, the server will abort.
1247 These are concerned with the symmetric encryption and decryption
1250 .BI "SYMM replay old-sequence"
1251 A packet was received with an old sequence number. It may just have
1252 been delayed or duplicated, or it may have been an attempt at a replay
1255 .BI "SYMM replay duplicated-sequence"
1256 A packet was received with a sequence number we've definitely seen
1257 before. It may be an accidental duplication because the 'net is like
1258 that, or a deliberate attempt at a replay.
1260 These concern the workings of the system-specific tunnel driver. The
1261 second word is the name of the tunnel interface in question, or
1265 .BI "TUN \- bsd no-tunnel-devices"
1266 The driver couldn't find an available tunnel device. Maybe if you
1269 files, it will work.
1271 .BI "TUN \- " tun-name " open-error " device " " ecode " " message
1272 An attempt to open the tunnel device file
1276 .BI "TUN \- linux config-error " ecode " " message
1277 Configuring the Linux TUN/TAP interface failed.
1279 .BI "TUN " ifname " " tun-name " read-error " ecode " " message
1280 Reading from the tunnel device failed.
1282 .BI "TUN " ifname " slip bad-escape"
1283 The SLIP driver encountered a escaped byte it wasn't expecting to see.
1284 The erroneous packet will be ignored.
1286 .BI "TUN " ifname " slip eof"
1287 The SLIP driver encountered end-of-file on its input descriptor.
1288 Pending data is discarded, and no attempt is made to read any more data
1289 from that interface ever.
1291 .BI "TUN " ifname " slip escape-end"
1292 The SLIP driver encountered an escaped `end' marker. This probably
1293 means that someone's been sending it junk. The erroneous packet is
1294 discarded, and we hope that we've rediscovered synchronization.
1296 .BI "TUN \- slip fork-error " ecode " " message
1297 The SLIP driver encountered an error forking a child process while
1298 allocating a new dynamic interface.
1300 .BI "TUN \- slip no-slip-interfaces"
1301 The driver ran out of static SLIP interfaces. Either preallocate more,
1302 or use dynamic SLIP interface allocation.
1304 .BI "TUN " ifname " slip overflow"
1305 The SLIP driver gave up reading a packet because it got too large.
1307 .BI "TUN \- slip pipe-error " ecode " " message
1308 The SLIP driver encountered an error creating pipes while allocating a
1309 new dynamic interface.
1311 .BI "TUN \- slip read-ifname-failed " ecode " " message
1312 The SLIP driver encountered an error reading the name of a dynamically
1313 allocated interface. Maybe the allocation script is broken.
1315 .BI "TUN \- unet config-error " ecode " " message
1316 Configuring the Linux Unet interface failed. Unet is obsolete and
1317 shouldn't be used any more.
1319 .BI "TUN \- unet getinfo-error " ecode " " message
1320 Reading information about the Unet interface failed. Unet is obsolete
1321 and shouldn't be used any more.
1323 These are issued by administration clients using the
1327 .BI "USER " tokens\fR...
1328 An administration client issued a warning.
1331 .SS "Command responses"
1334 .BI "BGFAIL " tag " " tokens \fR...
1335 .BI "BGINFO " tag " " tokens \fR...
1337 .BI "FAIL " tokens \fR...
1338 .BI "INFO " tokens \fR...
1346 .IR "The Trivial IP Encryption Protocol" .
1348 Mark Wooding, <mdw@distorted.org.uk>
~mdw / tripe / blob