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 By default, the server listens for admin connections on the Unix-domain
30 .BR /var/lib/tripe/tripesock .
31 Administration commands use a textual protocol. Each client command or
32 server response consists of a line of ASCII text terminated by a single
33 linefeed character. No command may be longer than 255 characters.
34 .SS "General structure"
35 Each command or response line consists of a sequence of
36 whitespace-separated words. The number and nature of whitespace
37 characters separating two words in a client command is not significant;
38 the server always uses a single space character. The first word in a
41 identifying the type of command or response contained. Keywords in
42 client commands are not case-sensitive; the server always uses uppercase
45 For simple client command, the server responds with zero or more
47 lines, followed by either an
53 provides information requested in the command. An
55 response contains no further data. A
57 code is followed by a machine-readable explanation of why the command
60 Simple command processing is strictly synchronous: the server reads a
61 command, processes it, and responds, before reading the next command.
62 All commands can be run as simple commands. Long-running commands
67 block the client until they finish, but the rest of the server continues
69 .B "Background commands"
70 to find out how to issue long-running commands without blocking.
71 .SS "Asynchronous broadcasts"
72 There are three types of asynchronous broadcast messages which aren't
73 associated with any particular command. Clients can select which
74 broadcast messages they're interested in using the
80 message contains a machine-readable message warning of an error
81 encountered while processing a command, unexpected or unusual behaviour
82 by a peer, or a possible attack by an adversary. Under normal
83 conditions, the server shouldn't emit any warnings.
87 message contains a human-readable tracing message containing diagnostic
88 information. Trace messages are controlled using the
90 command-line option to the server, or the
92 administration command (see below). Support for tracing can be disabled
93 when the package is being configured, and may not be available in your
98 message is a machine-readable notification about some routine but
99 interesting event such as creation or destruction of peers.
100 .SS "Background commands"
105 take a long time to complete. To prevent these long-running commands
106 from tying up a server connection, they can be run in the background.
107 Not all commands can be run like this: the ones that can provide a
109 option, which must be supplied with a
112 A command may fail before it starts running in the background. In this
113 case, the server emits a
115 response, as usual. To indicate that a command has started running in
116 the background, the server emits a response of the form
117 .BI "BGDETACH " tag \fR,
120 is the value passed to the
122 option. From this point on, the server is ready to process more
123 commands and reply to them.
125 Responses to background commands are indicated by a line beginning with
131 followed by the command tag. These correspond to the
136 responses for simple commands:
138 indicates information from a background command which has not completed
143 indicates that a background command succeeded or failed, respectively.
145 A background command will never issue an
149 response: it will always detach and then issue any
154 .SS "Client-provided services"
155 .\"* 25 Service-related messages
156 An administration client can provide services to other clients.
157 Services are given names and versions. A client can attempt to
159 a particular service by issuing the
161 command. This may fail, for example, if some other client already
162 provides the same or later version of the service.
164 Other clients can issue
165 .I "service commands"
168 command; the service provider is expected to handle these commands and
171 There are three important asynchronous messages which will be sent to
174 .BI "SVCCANCEL " jobid
175 The named job has been cancelled, either because the issuing client has
176 disconnected or explicitly cancelled the job using the
180 .BI "SVCCLAIM " service " " version
181 Another client has claimed a later version of the named
182 .I service. The recipient is no longer the provider of this service.
184 .BI "SVCJOB " jobid " " service " " command " " args \fR...
185 Announces the arrival of a new job. The
187 is a simple token consisting of alphanumeric characters which
189 uses to identify this job.
191 The service provider can reply to the job using the commands
196 The first of these sends an
198 response and leaves the job active; the other two send an
202 response respectively, and mark the job as being complete.
206 is a potentially long-running command, it can be run in the background.
207 This detail is hidden from service providers:
209 will issue the corresponding
211 responses when appropriate.)
212 .SS "Network addresses"
213 A network address is a sequence of words. The first is a token
214 identifying the network address family. The length of an address and
215 the meanings of the subsequent words depend on the address family.
216 Address family tokens are not case-sensitive on input; on output, they
217 are always in upper-case.
219 At present, only one address family is understood.
221 .BI "INET " address " " port
222 An Internet socket, naming an IPv4 address and UDP port. On output, the
223 address is always in numeric dotted-quad form, and the port is given as
224 a plain number. On input, DNS hostnames and symbolic port names are
225 permitted. Name resolution does not block the main server, but will
226 block the requesting client, unless the command is run in the background.
228 If, on input, no recognised address family token is found, the following
229 words are assumed to represent an
231 address. Addresses output by the server always have an address family
233 .SS "Key-value output"
238 produce output in the form of
240 pairs, one per word. Neither the
246 Commands which enable or disable kinds of output (e.g.,
250 work in similar ways. They take a single optional argument, which
251 consists of a string of letters selecting message types, optionally
256 to disable, the subsequently listed types.
258 If the argument is omitted, the available message types are displayed,
261 line, in a fixed-column format. Column zero contains the key letter for
262 selecting that message type; column one contains either a space or a
264 sign, if the message type is disabled or enabled respectively; and a
265 textual description of the message type begins at column 3 and continues
266 to the end of the line.
268 Lowercase key letters control individual message types. Uppercase key
269 letters control collections of message types.
270 .SH "COMMAND REFERENCE"
272 The commands provided are:
274 .BI "ADD \fR[" options "\fR] " peer " " address "\fR..."
275 Adds a new peer. The peer is given the name
277 the peer's public key is assumed to be in the file
279 (or whatever alternative file was specified in the
281 option on the command line). The
283 is the network address (see above for the format) at which the peer can
284 be contacted. The following options are recognised.
288 .BI "\-background " tag
289 Run the command in the background, using the given
292 .BI "\-keepalive " time
293 Send a no-op packet if we've not sent a packet to the peer in the last
295 interval. This is useful for persuading port-translating firewalls to
296 believe that the `connection' is still active. The
298 is expressed as a nonnegative integer followed optionally by
304 for days, hours, minutes, or seconds respectively; if no suffix is
305 given, seconds are assumed.
307 .BI "\-tunnel " tunnel
308 Use the named tunnel driver, rather than the default.
315 line reporting the IP address and port number stored for
319 Cancels the background job with the named
322 .BI "CHECKCHAL " challenge
323 Verifies a challenge as being one earlier issued by
325 and not previously either passed to
327 or in a greeting message.
330 Causes the server to disassociate itself from its terminal and become a
331 background task. This only works once. A warning is issued.
333 .BI "EPING \fR[" options "\fR] " peer
334 Sends an encrypted ping to the peer, and expects an encrypted response.
335 This checks that the peer is running (and not being impersonated), and
336 that it can encrypt and decrypt packets correctly. Options and
337 responses are the same as for the
342 Requests the server to begin a new key exchange with
347 Requests a challenge. The challenge is returned in an
349 line, as a base64-encoded string. See
352 .BI "GREET " peer " " challenge
353 Sends a greeting packet containing the
355 (base-64 encoded) to the named
357 The expectation is that this will cause the peer to recognize us and
358 begin a key-exchange.
361 Causes the server to emit an
363 line for each command it supports. Each line lists the command name,
364 followed by the names of the arguments. This may be helpful as a memory
365 aid for interactive use, or for program clients probing for features.
370 line containing the name of the network interface used to collect IP
371 packets which are to be encrypted and sent to
373 Used by configuration scripts so that they can set up routing tables
374 appropriately after adding new peers.
379 line giving the tag for each outstanding background job.
382 Causes the server to forget all about
384 All keys are destroyed, and no more packets are sent. No notification
385 is sent to the peer: if it's important that the peer be notified, you
386 must think of a way to do that yourself.
389 For each currently-known peer, an
391 line is written containing the peer's name, as given to
394 .BI "NOTIFY " tokens\fR...
397 notification to all interested administration clients.
400 Returns information about a peer, in key-value form. The following keys
405 The tunnel driver used for this peer.
408 The keepalive interval, in seconds, or zero if no keepalives are to be
412 .BI "PING \fR[" options "\fR] " peer
413 Send a transport-level ping to the peer. The ping and its response are
414 not encrypted or authenticated. This command, possibly in conjunction
415 with tracing, is useful for ensuring that UDP packets are actually
416 flowing in both directions. See also the
422 line is printed describing the outcome:
425 .BI "ping-ok " millis
426 A response was received
428 after the ping was sent.
431 No response was received within the time allowed.
434 The peer was killed (probably by another admin connection) before a
435 response was received.
438 Options recognized for this command are:
442 .BI "\-background " tag
443 Run the command in the background, using the given
446 .BI "\-timeout " time
449 seconds before giving up on a response. The default is 5 seconds. The
451 is expressed as a nonnegative integer followed optionally by
457 for days, hours, minutes, or seconds respectively; if no suffix is
458 given, seconds are assumed.
465 line containing just the number of the UDP port used by the
467 server. If you've allowed your server to allocate a port dynamically,
468 this is how to find out which one it chose.
471 Instructs the server to recheck its keyring files. The server checks
472 these periodically anyway but it may be necessary to force a recheck,
473 for example after adding a new peer key.
476 Instructs the server to exit immediately. A warning is sent.
479 Returns information about the server, in the form of key-value pairs.
480 The following keys are used.
484 A keyword naming the implementation of the
486 server. The current implementation is called
490 The server's version number, as reported by
498 if the server has or hasn't (respectively) become a daemon.
501 .BI "SETIFNAME " peer " " new-name
502 Informs the server that the
504 tunnel-interface name has been changed to
506 This is useful if firewalling decisions are made based on interface
507 names: a setup script for a particular peer can change the name, and
508 then update the server's records so that they're accurate.
510 .BI "SVCCLAIM " service " " version
511 Attempts to claim the named
515 The claim is successful if the service is currently unclaimed, or if
516 a version earlier than
518 is provided; otherwise the command fails with the error
519 .BR "service-exists" .
521 .BI "SVCENSURE " service " \fR[" version \fR]
524 is provided, and (if specified) to at least the given
526 An error is reported if these conditions are not met; otherwise the
527 command succeeds silently.
529 .BI "SVCFAIL " jobid " " tokens \fR...
534 response to the service job with the given
538 as the reason for failure. The job is closed.
540 .BI "SVCINFO " jobid " " tokens \fR...
545 response to the service job with the given
549 as the info message. The job remains open.
552 Output a line of the form
559 for each service currently provided.
567 response to the service job with the given
571 .BI "SVCQUERY " service
574 lines in key-value format, describing the named
576 The following keys are used.
583 The service's version string.
586 .BI "SVCRELEASE " service
587 Announce that the client no longer wishes to provide the named
590 .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR...
591 Submit a job to the provider of the given
597 The following options are accepted.
601 .BI "\-background " tag
602 Run the command in the background, using the given
605 .BI "\-version " version
606 Ensure that at least the given
608 of the service is available before submitting the job.
615 lines, each containing one or more statistics in the form
616 .IB name = value \fR.
617 The statistics-gathering is experimental and subject to change.
619 .BR "TRACE " [\fIoptions\fP]
620 Selects trace outputs: see
622 above. Message types provided are:
625 Currently, the following tracing options are supported:
628 Tunnel events: reception of packets to be encrypted, and injection of
629 successfully-decrypted packets.
632 Peer management events: creation and destruction of peer attachments,
633 and arrival of messages.
636 Administration interface: acceptance of new connections, and handling of
637 the backgroud name-resolution required by the
642 Handling of symmetric keysets: creation and expiry of keysets, and
643 encryption and decryption of messages.
646 Key exchange: reception, parsing and emission of key exchange messages.
649 Key management: loading keys and checking for file modifications.
652 Display information about challenge issuing and verification.
655 Display contents of packets sent and received by the tunnel and/or peer
659 Display inputs, outputs and intermediate results of cryptographic
660 operations. This includes plaintext and key material. Use with
672 outputs provide extra detail for other outputs. Specifying
678 isn't useful; neither is specifying
689 For each available tunnel driver, an
691 line is printed giving its name.
694 Causes the server to emit an
696 line stating its software version, as two words: the server name, and
697 its version string. The server name
699 is reserved to the Straylight/Edgeware implementation.
701 .BR "WATCH " [\fIoptions\fP]
702 Enables or disables asynchronous broadcasts
703 .IR "for the current connection only" .
706 above. The default watch state for the connection the server opens
707 automatically on stdin/stdout is to show warnings and trace messages;
708 other connections show no asynchronous broadcast messages. (This is
709 done in order to guarantee that a program reading the server's stdout
710 does not miss any warnings.)
713 Message types provided are:
731 .BI "WARN " tokens\fR...
734 warning to all interested administration clients.
736 .\"* 20 Error messages (FAIL codes)
741 messages are sent to clients as a result of errors during command
749 server is already running as a daemon.
751 .BI "bad-addr-syntax " message
752 (For commands accepting socket addresses.) The address couldn't be
755 .BI "bad-syntax " cmd " " message
756 (For any command.) The command couldn't be understood: e.g., the number
757 of arguments was wrong.
759 .BI "bad-time-spec " word
762 is not a valid time interval specification. Acceptable time
763 specifications are nonnegative integers followed optionally by
769 for days, hours, minutes, or seconds, respectively.
771 .BI "bad-trace-option " char
774 An unknown trace option was requested.
776 .BI "bad-watch-option " char
779 An unknown watch option was requested.
781 .BI "daemon-error " ecode " " message
784 An error occurred during the attempt to become a daemon, as reported by
787 .BI "invalid-port " number
790 The given port number is out of range.
792 .BI "not-service-provider " service
795 The invoking client is not the current provider of the named
797 and is therefore not allowed to release it.
799 .BI "peer-create-fail " peer
804 failed for some reason. A warning should have been emitted explaining
807 .BI "peer-exists " peer
810 There is already a peer named
813 .B "ping-send-failed"
814 The attempt to send a ping packet failed, probably due to lack of
817 .BI "resolve-error " hostname
822 could not be resolved.
824 .BI "resolver-timeout " hostname
829 took too long to resolve.
831 .BI "service-exists " service " " version
834 Another client is already providing the stated
839 .BI "service-too-old " service " " version
848 is available, which does not meet the stated requirements.
850 .BI "tag-exists " tag
851 (For long-running commands.) The named
853 is already the tag of an outstanding job.
855 .BI "unknown-command " token
860 .BI "unknown-peer " name
868 There is no peer called
871 .BI "unknown-port " port
879 .BI "unknown-service " service
888 is not recognized as the name of a client-provided service.
890 .BI "unknown-tag " tag
895 is not the tag for any outstanding background job. It may have just
898 .\"* 30 Notification broadcasts (NOTE codes)
899 The following notifications are sent to clients who request them.
901 .BI "ADD " peer " " ifname " " address \fR...
902 A new peer has been added. The peer's name is
904 its tunnel is network interface
906 and its network address is
910 The server has forked off into the sunset and become a daemon.
912 .BI "GREET " challenge " " address \fR...
913 A valid greeting was received, with the given challenge (exactly as it
926 finished successfully.
931 has begun or restarted. If key exchange keeps failing, this message
932 will be repeated periodically.
934 .BI "NEWIFNAME " peer " " old-name " " new-name
937 tunnel interface name has been changed from
945 .BI "SVCCLAIM " service " " version
948 is now available, at the stated
951 .BI "SVCRELEASE " service
954 is no longer available.
956 .BI "USER " tokens\fR...
957 An administration client issued a notification using the
961 .\"* 40 Warning broadcasts (WARN codes)
963 There are many possible warnings. They are categorized according to
966 Many of these warnings report system errors. These are reported as a
967 pair of tokens, described below as
973 is a string of the form
977 value of the error; the
979 is the `human-readable' form of the message, as reported by
982 These all indicate that the
984 server has become unable to continue. If enabled, the server will dump
985 core in its configuration directory.
987 .BI "ABORT repeated-select-errors"
988 The main event loop is repeatedly failing. If the server doesn't quit,
989 it will probably waste all available CPU doing nothing.
991 These indicate a problem with the administration socket interface.
993 .BI "ADMIN accept-error " ecode " " message
994 There was an error while attempting to accept a connection from a new
997 .BI "ADMIN client-write-error " ecode " " message
998 There was an error sending data to a client. The connection to the
999 client has been closed.
1001 These indicate errors in challenges, either in the
1003 command or in greeting packets.
1005 .B "CHAL impossible-challenge"
1006 The server hasn't issued any challenges yet. Quite how anyone else
1007 thought he could make one up is hard to imagine.
1009 .B "CHAL incorrect-tag"
1010 Challenge received contained the wrong authentication data. It might be
1011 very stale, or a forgery.
1013 .B "CHAL invalid-challenge"
1014 Challenge received was the wrong length. We might have changed MAC
1015 algorithms since the challenge was issued, or it might just be rubbish.
1017 .B "CHAL replay duplicated-sequence"
1018 Challenge received was a definite replay of an old challenge. Someone's
1021 .B "CHAL replay old-sequence"
1022 Challenge received was old, but maybe not actually a replay. Try again.
1023 .SS "KEYMGMT warnings"
1024 These indicate a problem with the keyring files, or the keys stored in
1027 .BI "KEYMGMT bad-private-key " message
1028 The private key could not be read, or failed a consistency check. If
1029 there was a problem with the file, usually there will have been
1031 warnings before this.
1033 .BI "KEYMGMT bad-public-keyring " message
1034 The public keyring couldn't be read. Usually, there will have been
1036 warnings before this.
1038 .BI "KEYMGMT key-file-error " file ":" line " " message
1039 Reports a specific error with the named keyring file. This probably
1043 .BI "KEYMGMT public-key " tag " " tokens\fR...
1044 These messages all indicate a problem with the public key named
1047 .BI "KEYMGMT public-key " tag " algorithm-mismatch"
1048 The algorithms specified on the public key don't match the ones for our
1049 private key. All the peers in a network have to use the same
1052 .BI "KEYMGMT public-key " tag " bad " message
1053 The public key couldn't be read, or is invalid.
1055 .BI "KEYMGMT public-key " tag " bad-public-group-element"
1056 The public key is invalid. This may indicate a malicious attempt to
1057 introduce a bogus key.
1059 .BI "KEYMGMT public-key " tag " bad-algorithm-selection"
1060 The algorithms listed on the public key couldn't be understood. The
1061 algorithm selection attributes are probably malformed and need fixing.
1063 .BI "KEYMGMT public-key " tag " incorrect-group"
1064 The public key doesn't use the same group as our private key. All the
1065 peers in a network have to use the same group.
1067 .BI "KEYMGMT public-key " tag " not-found"
1068 The public key for peer
1070 wasn't in the public keyring.
1072 .BI "KEYMGMT public-key " tag " unknown-type"
1073 The type of the public key isn't understood. Maybe you need to upgrade
1076 (Even if you do, you'll have to regenerate your keys.)
1078 These indicate problems during key-exchange. Many indicate either a bug
1079 in the server (either yours or the remote one), or some kind of attack
1080 in progress. All name a
1082 as the second token: this is the peer the packet is apparently from,
1083 though it may have been sent by an attacker instead.
1085 In the descriptions below,
1087 is one of the tokens
1096 .BI "KX " peer " bad-expected-reply-log"
1099 uses in its protocol contain a check value which proves that the
1100 challenge is honest. This message indicates that the check value
1101 supplied is wrong: someone is attempting to use bogus challenges to
1104 server to leak private key information. No chance!
1106 .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok"
1107 A symmetrically-encrypted portion of a key-exchange message failed to
1110 .BI "KX " peer " invalid " msgtoken
1111 A key-exchange message was malformed. This almost certainly indicates a
1114 .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok"
1115 A message didn't contain the right magic data. This may be a replay of
1116 some old exchange, or random packets being sent in an attempt to waste
1119 .BI "KX " peer " public-key-expired"
1120 The peer's public key has expired. It's maintainer should have given
1121 you a replacement before now.
1123 .BI "KX " peer " sending-cookie"
1124 We've received too many bogus pre-challenge messages. Someone is trying
1125 to flood us with key-exchange messages and make us waste CPU on doing
1126 hard asymmetric crypto sums.
1128 .BI "KX " peer " unexpected " msgtoken
1129 The message received wasn't appropriate for this stage of the key
1130 exchange process. This may mean that one of our previous packets got
1133 it may simply mean that the peer has recently restarted.
1135 .BI "KX " peer " unknown-challenge"
1136 The peer is asking for an answer to a challenge which we don't know
1137 about. This may mean that we've been inundated with challenges from
1138 some malicious source
1139 .I who can read our messages
1140 and discarded the valid one.
1142 .BI "KX " peer " unknown-message 0x" nn
1143 An unknown key-exchange message arrived.
1145 These are largely concerned with management of peers and the low-level
1146 details of the network protocol. The second word is usually the name of
1149 if none is relevant.
1151 .BI "PEER " peer " bad-packet no-type"
1152 An empty packet arrived. This is very strange.
1154 .BI "PEER " peer " bad-packet unknown-category 0x" nn
1155 The message category
1157 (in hex) isn't understood. Probably a strange random packet from
1158 somewhere; could be an unlikely bug.
1160 .BI "PEER " peer " bad-packet unknown-type 0x" nn
1163 (in hex) isn't understood. Probably a strange random packet from
1164 somewhere; could be an unlikely bug.
1166 .BI "PEER " peer " corrupt-encrypted-ping"
1167 The peer sent a ping response which matches an outstanding ping, but its
1168 payload is wrong. There's definitely a bug somewhere.
1170 .BI "PEER " peer " corrupt-transport-ping"
1171 The peer (apparently) sent a ping response which matches an outstanding
1172 ping, but its payload is wrong. Either there's a bug, or the bad guys
1173 are playing tricks on you.
1175 .BI "PEER " peer " decrypt-failed"
1176 An encrypted IP packet failed to decrypt. It may have been mangled in
1177 transit, or may be a very old packet from an expired previous session
1178 key. There is usually a considerable overlap in the validity periods of
1179 successive session keys, so this shouldn't occur unless the key exchange
1180 takes ages or fails.
1182 .BI "PEER " peer " malformed-encrypted-ping"
1183 The peer sent a ping response which is hopelessly invalid. There's
1184 definitely a bug somewhere.
1186 .BI "PEER " peer " malformed-transport-ping"
1187 The peer (apparently) sent a ping response which is hopelessly invalid.
1188 Either there's a bug, or the bad guys are playing tricks on you.
1190 .BI "PEER " peer " packet-build-failed"
1191 There wasn't enough space in our buffer to put the packet we wanted to
1192 send. Shouldn't happen.
1194 .BI "PEER \- socket-read-error " ecode " " message
1195 An error occurred trying to read an incoming packet.
1197 .BI "PEER " peer " socket-write-error " ecode " " message
1198 An error occurred attempting to send a network packet. We lost that
1201 .BI "PEER " peer " unexpected-encrypted-ping 0x" id
1202 The peer sent an encrypted ping response whose id doesn't match any
1203 outstanding ping. Maybe it was delayed for longer than the server was
1204 willing to wait, or maybe the peer has gone mad.
1206 .BI "PEER \- unexpected-source " address\fR...
1207 A packet arrived from
1209 (a network address \(en see above), but no peer is known at that
1210 address. This may indicate a misconfiguration, or simply be a result of
1211 one end of a connection being set up before the other.
1213 .BI "PEER " peer " unexpected-transport-ping 0x" id
1214 The peer (apparently) sent a transport ping response whose id doesn't
1215 match any outstanding ping. Maybe it was delayed for longer than the
1216 server was willing to wait, or maybe the peer has gone mad; or maybe
1217 there are bad people trying to confuse you.
1218 .SS "SERVER warnings"
1219 These indicate problems concerning the server process as a whole.
1221 .BI "SERVER ignore signal " name
1222 A signal arrived, but the server ignored it. Currently this happens for
1224 because that's a popular way of telling daemons to re-read their
1225 configuration files. Since
1227 re-reads its keyrings automatically and has no other configuration
1228 files, it's not relevant, but it seemed better to ignore the signal than
1231 .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR]
1232 A signal arrived and
1236 .BI "SERVER quit admin-request"
1237 A client of the administration interface issued a
1241 .BI "SERVER select-error " ecode " " message
1242 An error occurred in the server's main event loop. This is bad: if it
1243 happens too many times, the server will abort.
1245 These are concerned with the symmetric encryption and decryption
1248 .BI "SYMM replay old-sequence"
1249 A packet was received with an old sequence number. It may just have
1250 been delayed or duplicated, or it may have been an attempt at a replay
1253 .BI "SYMM replay duplicated-sequence"
1254 A packet was received with a sequence number we've definitely seen
1255 before. It may be an accidental duplication because the 'net is like
1256 that, or a deliberate attempt at a replay.
1258 These concern the workings of the system-specific tunnel driver. The
1259 second word is the name of the tunnel interface in question, or
1263 .BI "TUN \- bsd no-tunnel-devices"
1264 The driver couldn't find an available tunnel device. Maybe if you
1267 files, it will work.
1269 .BI "TUN - " tun-name " open-error " device " " ecode " " message
1270 An attempt to open the tunnel device file
1274 .BI "TUN \- linux config-error " ecode " " message
1275 Configuring the Linux TUN/TAP interface failed.
1277 .BI "TUN " ifname " " tun-name " read-error " ecode " " message
1278 Reading from the tunnel device failed.
1280 .BI "TUN " ifname " slip bad-escape"
1281 The SLIP driver encountered a escaped byte it wasn't expecting to see.
1282 The erroneous packet will be ignored.
1284 .BI "TUN " ifname " slip eof"
1285 The SLIP driver encountered end-of-file on its input descriptor.
1286 Pending data is discarded, and no attempt is made to read any more data
1287 from that interface ever.
1289 .BI "TUN " ifname " slip escape-end"
1290 The SLIP driver encountered an escaped `end' marker. This probably
1291 means that someone's been sending it junk. The erroneous packet is
1292 discarded, and we hope that we've rediscovered synchronization.
1294 .BI "TUN \- slip fork-error " ecode " " message
1295 The SLIP driver encountered an error forking a child process while
1296 allocating a new dynamic interface.
1298 .BI "TUN \- slip no-slip-interfaces"
1299 The driver ran out of static SLIP interfaces. Either preallocate more,
1300 or use dynamic SLIP interface allocation.
1302 .BI "TUN " ifname " slip overflow"
1303 The SLIP driver gave up reading a packet because it got too large.
1305 .BI "TUN \- slip pipe-error " ecode " " message
1306 The SLIP driver encountered an error creating pipes while allocating a
1307 new dynamic interface.
1309 .BI "TUN \- slip read-ifname-failed " ecode " " message
1310 The SLIP driver encountered an error reading the name of a dynamically
1311 allocated interface. Maybe the allocation script is broken.
1313 .BI "TUN \- unet config-error " ecode " " message
1314 Configuring the Linux Unet interface failed. Unet is obsolete and
1315 shouldn't be used any more.
1317 .BI "TUN \- unet getinfo-error " ecode " " message
1318 Reading information about the Unet interface failed. Unet is obsolete
1319 and shouldn't be used any more.
1321 .BI "TUN \- unet ifname-too-long"
1322 The Unet interface's name overflowed, so we couldn't read it properly.
1323 Unet is obsolete and shouldn't be used any more.
1325 These are issued by administration clients using the
1329 .BI "USER " tokens\fR...
1330 An administration client issued a warning.
1333 .SS "Command responses"
1336 .BI "BGFAIL " tag " " tokens \fR...
1337 .BI "BGINFO " tag " " tokens \fR...
1339 .BI "FAIL " tokens \fR...
1340 .BI "INFO " tokens \fR...
1348 .IR "The Trivial IP Encryption Protocol" .
1350 Mark Wooding, <mdw@distorted.org.uk>
~mdw / tripe / blob