3 .\" Manual for the peer configuration file
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 it under
13 .\" the terms of the GNU General Public License as published by the Free
14 .\" Software Foundation; either version 3 of the License, or (at your
15 .\" option) any later version.
17 .\" TrIPE is distributed in the hope that it will be useful, but WITHOUT
18 .\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
19 .\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
22 .\" You should have received a copy of the GNU General Public License
23 .\" along with TrIPE. If not, see <https://www.gnu.org/licenses/>.
25 .\"--------------------------------------------------------------------------
26 .so ../common/defs.man \"@@@PRE@@@
28 .\"--------------------------------------------------------------------------
29 .TH peers.in 5tripe "27 March 2008" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
31 .\"--------------------------------------------------------------------------
34 peers.in \- source form for TrIPE peer database
36 .\"--------------------------------------------------------------------------
41 file is a plain text configuration file. It is read by
42 .BR tripe-newpeers (8)
43 in order to produce the
45 database used by services and other tools.
47 .SS "General structure"
48 The configuration file is line-oriented. Blank lines are ignored; lines
53 are ignored. The file is divided into sections by section headers,
54 which are lines of the form
58 Within each section are a number of assignments, of the form
62 or (entirely equivalent)
68 must start in the left hand column. The
70 may span multiple lines if subsequent lines begin with whitespace, in
71 the manner of RFC822 headers.
73 There is a special case to be aware of: if a section doesn't specify a
76 then the section's own name is used as a default.
78 The following substitutions are made in the body of a value.
82 is replaced by the value assigned to the given
87 is replaced by the IP address of the named
95 consist of zero or more of the following characters:
97 returns all of the found addresses, separated by spaces, rather than
100 There is a simple concept of
102 for sections. If a section contains an assignment
104 .BI "@inherit = " parent
109 then any lookups which can't be satisfied in that section will be
110 satisfied instead from its
112 sections (and, if necessary, their parents in turn, and so on).
115 If a value can be found for a key via multiple parents then all of them
118 value. This restriction may be relaxed somewhat, if it turns out that a
119 more flexible notion of multiple inheritance is useful.
121 It's not allowed for a section to inherit, possibly indirectly, from
122 itself. Currently errors of this kind are only diagnosed when a cycle
123 is encountered while looking up a key and none of the sections on the
124 path from the original section up to and round the cycle define a value
125 for it. Future versions of this program might be more picky.
129 substitutions in the resulting value will be satisfied from the original
130 section (though falling back to scanning parent sections). For
131 example, given the sections
135 blurb = expand $(detail)
143 .RB ` "expand in parent" '
147 .RB ` "expand in child" '
151 Apart from its effect on lookups, as just described, the
153 key is entirely ignored. In particular, it is never written to the
156 .SS "Standard keys and their meanings"
157 The following keys have meanings to programs in the TrIPE suite. Other
158 keys may be used by separately distributed extensions or for local use.
159 The descriptions given are summaries only; see the references for
163 If true, include the peer in the
168 .BR tripe-newpeers (8);
172 Shell command for initiating connection to this peer. Used by
176 Don't initiate immediate key exchange. Used by
180 Shell command for closing down connection to this peer. Used by
184 Interval for checking that the peer is still alive and well. Used by
188 Script to bring down tunnel interface connected to the peer. Used by
192 Interface name to set for the tunnel interface to the peer. Used by
196 Script to bring up tunnel interface connected to the peer. Used by
200 Script containing additional interface setup. Used by
204 Local address for the tunnel interface to the peer. Used by
208 Interval for sending keepalive pings. Used by
212 Key tag to use to authenticate the peer. Used by
216 Peer's IP address is highly volatile. Used by
220 Maximum transmission unit for the tunnel interface. Used by
224 Networks to be routed over the tunnel interface. Used by
228 Network address for this peer, or
234 Tag of the private key to use when communicating with the peer.
239 Remote address for the tunnel interface to the peer. Used by
243 Number of failed ping attempts before attempting reconnection. Used by
247 Timeout for ping probes. Used by
251 Tunnel driver to use when adding the peer. Used by
255 Peer will make active connection as
260 .BR tripe-newpeers (8);
264 This section describes how the textual
266 file is converted into the
270 The handling of each section depends on its name.
272 Sections whose names have the form
274 are ignored (though their contents may be relevant if the section is
275 named in another section's
279 Sections whose names have the form
281 are written to local-type database records with the same name. The keys
282 and values defined in the section (and its parent section, if it
285 key) are stored in the record using
287 as defined in RFC1822, except that the key-value pairs are separated by
290 rather than ampersands
292 Keys whose names begin with
294 are not written to the database.
296 Other sections are written to peer-type database records, named
298 in exactly the same way as for local-type records. However, two special
299 actions are also taken.
301 Firstly, if there is a key
303 in the section (or in its parent, etc.), and the value is
311 then the section's name is added in the special
315 Secondly, if there is a key
317 in the section (or in its parent, etc.), then a user record
319 is created whose contents is the section name.
321 .\"--------------------------------------------------------------------------
327 .BR tripe-newpeers (8),
332 .\"--------------------------------------------------------------------------
335 Mark Wooding, <mdw@distorted.org.uk>
337 .\"----- That's all, folks --------------------------------------------------