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:
101 returns all of the found addresses, separated by spaces, rather than
104 There is a simple concept of
106 for sections. If a section contains an assignment
108 .BI "@inherit = " parent
113 then any lookups which can't be satisfied in that section will be
114 satisfied instead from its
116 sections (and, if necessary, their parents in turn, and so on).
119 If a value can be found for a key via multiple parents then all of them
122 value. This restriction may be relaxed somewhat, if it turns out that a
123 more flexible notion of multiple inheritance is useful.
125 It's not allowed for a section to inherit, possibly indirectly, from
126 itself. Currently errors of this kind are only diagnosed when a cycle
127 is encountered while looking up a key and none of the sections on the
128 path from the original section up to and round the cycle define a value
129 for it. Future versions of this program might be more picky.
133 substitutions in the resulting value will be satisfied from the original
134 section (though falling back to scanning parent sections). For
135 example, given the sections
139 blurb = expand $(detail)
147 .RB ` "expand in parent" '
151 .RB ` "expand in child" '
155 Apart from its effect on lookups, as just described, the
157 key is entirely ignored. In particular, it is never written to the
160 .SS "Standard keys and their meanings"
161 The following keys have meanings to programs in the TrIPE suite. Other
162 keys may be used by separately distributed extensions or for local use.
163 The descriptions given are summaries only; see the references for
167 If true, include the peer in the
172 .BR tripe-newpeers (8);
176 Shell command for initiating connection to this peer. Used by
180 Don't initiate immediate key exchange. Used by
184 Shell command for closing down connection to this peer. Used by
188 Interval for checking that the peer is still alive and well. Used by
192 Script to bring down tunnel interface connected to the peer. Used by
196 Interface name to set for the tunnel interface to the peer. Used by
200 Script to bring up tunnel interface connected to the peer. Used by
204 Script containing additional interface setup. Used by
208 Local address for the tunnel interface to the peer. Used by
212 Interval for sending keepalive pings. Used by
216 Key tag to use to authenticate the peer. Used by
220 Peer's IP address is highly volatile. Used by
224 Maximum transmission unit for the tunnel interface. Used by
228 Networks to be routed over the tunnel interface. Used by
232 Network address for this peer, or
238 Tag of the private key to use when communicating with the peer.
243 Remote address for the tunnel interface to the peer. Used by
247 Number of failed ping attempts before attempting reconnection. Used by
251 Timeout for ping probes. Used by
255 Tunnel driver to use when adding the peer. Used by
259 Peer will make active connection as
264 .BR tripe-newpeers (8);
268 This section describes how the textual
270 file is converted into the
274 The handling of each section depends on its name.
276 Sections whose names have the form
278 are ignored (though their contents may be relevant if the section is
279 named in another section's
283 Sections whose names have the form
285 are written to local-type database records with the same name. The keys
286 and values defined in the section (and its parent section, if it
289 key) are stored in the record using
291 as defined in RFC1822, except that the key-value pairs are separated by
294 rather than ampersands
296 Keys whose names begin with
298 are not written to the database.
300 Other sections are written to peer-type database records, named
302 in exactly the same way as for local-type records. However, two special
303 actions are also taken.
305 Firstly, if there is a key
307 in the section (or in its parent, etc.), and the value is
315 then the section's name is added in the special
319 Secondly, if there is a key
321 in the section (or in its parent, etc.), then a user record
323 is created whose contents is the section name.
325 .\"--------------------------------------------------------------------------
331 .BR tripe-newpeers (8),
336 .\"--------------------------------------------------------------------------
339 Mark Wooding, <mdw@distorted.org.uk>
341 .\"----- That's all, folks --------------------------------------------------