xref: /freebsd/usr.sbin/rrenumd/rrenumd.conf.5 (revision 77a0943ded95b9e6438f7db70c4a28e4d93946d4)
1.\"	$KAME$
2.\"
3.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
4.\" All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. Neither the name of the project nor the names of its contributors
15.\"    may be used to endorse or promote products derived from this software
16.\"    without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28.\" SUCH DAMAGE.
29.\"
30.\"     $FreeBSD$
31.\"
32.Dd Nov 5, 1998
33.Dt RRENUMD.CONF 5
34.Os KAME
35.Sh NAME
36.\"
37.Nm rrenumd.conf
38.Nd configuration file for router renumbering daemon
39.\"
40.Sh DESCRIPTION
41The rrenumd config file describes how the router renumbering packet
42must be constructed and to which destinations it should be sent.
43This file consists of a sequence of statements terminated by a semi-colon (`;').
44Statements are composed of tokens
45separated by white space, which can be any combination of blanks, tabs
46and newlines.
47This structure simplifies identification of
48the parts of the configuration associated with each other.
49Lines beginning with
50.Ql #
51are comments.
52.\"
53.Sh Meta Syntax
54Keywords and special characters that the parser expects exactly are
55displayed using the
56.Ic bold
57font.
58Parameters are specifying with
59.Ar underline .
60Parameters shown in
61square brackets (`[' and `]') are used to show optional
62keywords and parameters.
63The vertical bar (`|') is used to indicate
64between a choice of optional parameters.
65Parentheses (`(' and
66`)') are used to group keywords and parameters when necessary.
67.\"
68.Sh Interface specification
69There are some statements that may or have to specify interface.
70Interfaces are specified in the form of "name unit", such as
71.Ar lo0
72and
73.Ar ep1.
74.\"
75.Sh Configuration Statements
76.Bl -tag -width Ds
77.\"
78.It Ic debug on|off ;
79Enables configuration file parser debugging.
80If
81.Ic on
82is specified,
83then debugging is enabled,
84If
85.Ic off
86is specified,
87then debugging is disabled. It is disabled by default.
88.\"
89.It Ic dest Ar dest-list Op Ar retrycmd ;
90Specifies destinations to which router renumbering messages should be
91sent.
92.Ar dest-list
93can be any combination of single or multiple numerical IPv6 addrs,
94or Full Qualified Domain Names.
95.Ar retrycmd
96has following syntax.
97
98.\"
99.Bl -tag -width Ds -compact
100.It Ic retry Ar retry-num
101.Ar retry-num
102specifies how many router renumbering messages are sent repeatedly.
103.El
104.It Op Ic add|change|setglobal
105.Cm match-prefix Ar match-prefix-val
106.Op /match-prefix-len
107.Op Cm maxlen Ar maxlen-val
108.Op Cm minlen Ar minlen-val
109.Op Cm use-prefix Ar use-prefix-val
110.Op /use-prefix-len
111.Op Cm keeplen Ar keeplen-val
112.Op Ar use-prefix-values ;
113.Pp
114Specifies contents of sending router renumbering message with seqnum 0.
115If
116.Cm add|change|setglobal
117is not specified, then
118.Cm add
119is assumed.
120.Ar use-prefix-values
121has following syntax.
122.Pp
123{
124.Op Cm vltime Ar vltime-val
125.Op Cm pltime Ar pltime-val
126.Op Cm raf_onlink Cm on|off
127.Op Cm raf_auto Cm on|off
128.Op Cm rrf_decrprefd Cm on|off
129.Op Cm rrf_decrvalid Cm on|off
130}
131.Pp
132Each value has following meaning.
133.Pp
134.Bl -tag -width Ds -compact
135.It Cm match-prefix Ar match-prefix-val Op /match-prefix-len
136Specify
137.Ar match-prefix-val
138that is used for matching with preassigned prefixes to which
139.Cm add|change|setglobal
140command should be applied.
141.Ar /match-prefix-len
142Specify the starting part of
143.Ar match-prefix-val
144to be used for matching with preassigned prefixes, as decimal bit number.
145.It Cm maxlen Ar maxlen-val
146Specify the maximum length of prefixes which is allowed to be
147matched to
148.Ar match-prefix-val ,
149as decimal bit number.
150.It Cm minlen Ar minlen-val
151Specify the minimum length of prefixes which is allowed to be matched to
152.Ar match-prefix-val ,
153as decimal bit number.
154.It Cm use-prefix Ar use-prefix-val Op /usr-prefix-len
155Specify
156.Ar use-prefix-val
157that is used for prefixes to be added on
158.Cm add|change|setglobal
159command.
160.Ar /use-prefix-len
161Specify the starting part of
162.Ar use-prefix-val
163copied to the starting part of prefixes to be added on
164.Cm add|change|setglobal
165command, as decimal bit number.
166.It Cm keeplen Ar keeplen-val
167Specify the midium part of
168.Ar use-prefix-val
169just next to the starting part specified by
170.Ar use-prefix-len
171, as decimal bit number.
172Contiguous bits part in the same bit position of an existent prefix
173matched with
174.Ar match-prefix-val
175is copied to the same bit position of prefixes to be added.
176.It Cm vltime Ar vmtime-val
177Assign an
178.Ar time
179as prefix valid life time for a prefix to be added.
180Valid value for
181.Ar time
182is decimal seconds number or special format as "d00h00m00s00",
183where 00 can take any decimal number, and "d" means days, "h" means hours,
184"m" means minutes, "s" means seconds. And alternatively, special keyword
185"infinity" can be also be specified.
186.It Cm pltime Ar pltime-val
187Assign an
188.Ar time
189as prefix preferred life time for a prefix to be added.
190Valid value for
191.Ar time
192is same as for
193.Ar vltime-val .
194.It Cm raf_onlink Cm on|off
195Let the prefix to be added to have on-link or off-link nature
196for the assigned interface. If
197.Cm on
198is specified, the prefix have on-link nature. (e.g. the prefix
199belong to the link) If
200.Cm off
201is specified, the prefix have off-link nature. (e.g. the
202prefix does not belong to the link)
203.It Cm raf_auto Cm on|off
204Enable or disable the autonomous address auto configuration
205for the prefix to be added. If
206.Cm on
207is specified, autonomous address auto configuration is
208enabled. If
209.Cm off
210is specified, it is disabled.
211.It Cm rrf_decrprefd Cm on|off
212Enable or disable the decrementation of the pltime. If
213.Cm on
214is specified, decrementation of the pltime is enabled. If
215.Cm off
216is specified, decrementation of the pltime is disabled.
217.It Cm rrf_decrvalid Cm on|off
218Enable or disable the decrementation of the vltime. If
219.Cm on
220is specified, decrementation of the vltime is enabled. If
221.Cm off
222is specified, decrementation of the vltime is disabled.
223.El
224.\"
225.It seqnum Ar seqnum-val { Ar rrenum-cmd } ;
226Specifies contents of sending router renumbering message with some
227specific seqnum. Multiple of this statement can be specified if they
228have different
229.Ar seqnum-val
230each other.
231.Ar rrenum-cmd
232has just same syntax with above add|change|setglobal statement.
233.El
234.\"
235.Sh EXAMPLES
236For each configuration file example shown below, we suppose
237every IPv6 subnet has its own prefix beginning with
238fec0:0:0::/48 and with its own subnet number. (in this case,
239subnet number is 7th and 8th octet value of the prefix)
240.Pp
241If you want to assigne prefixes beginning with fec0:1:1::/48
242to each subnet, then following configuration will be enough,
243if each of your routers supports IPv6 multicast forwarding.
244The subnet number of the existing fec0:0:0::/48 prefix and the
245newly assigned fec0:1:1::/48 prefix will be same.
246.\"
247.Bd -literal -offset indent
248dest ff05::2;
249
250add match-prefix fec0:0:0:: /48 use-prefix fec0:1:1:: /48 keeplen 16;
251.Ed
252.\"
253
254If your routers don't support IPv6 multicast forwarding,
255you'll need to specify each destination at
256.Cm dest
257command.
258.\"
259.Bd -literal -offset indent
260dest fec0:0:0:1:260:8ff:fe24:fb3a fec0:0:0:2:200:eff:fe2e:dfe1 fec0:0:0:3:5254:ff:fedc:5217;
261
262add match-prefix fec0:0:0:: /48 use-prefix fec0:1:1:: /48 keeplen 16;
263.Ed
264.\"
265
266If you are going to do renumbering, then following procedure will be natural.
267.Bl -enum -offset indent
268.It
269Assigne new prefix.
270.It
271Set old prefix lifetimes to some appropriate transition
272period. In the followng example we use 1 week for valid
273lifetime, and 0 for preferred lifetime.
274Also, enable old prefix lifetime expiration.
275(By default, it is static and does not expire)
276.It
277After the transition period, old prefixes should become
278invalid, and may have been deleted.
279To make sure that they are deleted, send new router
280renumbering message, which specifies old prefixes as match
281prefix, and no use prefix.
282.El
283.\"
284
285The following configuration file will do 1 and 2.
286.\"
287.Bd -literal -offset indent
288dest ff05::2;
289
290seqnum 0 {
291	add match-prefix fec0:0:0:: /48 use-prefix fec0:2:2:: /48 keeplen 16;
292	};
293
294seqnum 1 {
295	change match-prefix fec0:1:1:: /48 use-prefix fec0:1:1:: /48 keeplen 16 vltime d7 pltime 0 rrf_decrvalid on rrf_decrprefd on;
296	};
297.Ed
298.\"
299
300And the following configuration file will do 3. (should be
301used for the router renumbering message to be sent 1 week
302afterward)
303.\"
304.Bd -literal -offset indent
305dest ff05::2;
306
307change match-prefix fec0:1:1:: /48;
308.Ed
309.\"
310
311In the above example, only
312.Cm add
313and
314.Cm change
315commands are used, and there is no example for
316.Cm setglobal
317command.
318.Cm setglobal
319command is almost same with
320.Cm change
321command except that it deletes all pre-defined IPv6 global address.
322
323.Sh SEE ALSO
324.Xr rrenumd 8
325.Xr prefix 8
326.Sh HISTORY
327The
328.Nm
329configuration file was first appeared in KAME IPv6 protocol stack kit.
330.\" .Sh BUGS
331.\" (to be written)
332