bird.sgml 190 KB
Newer Older
1
<!doctype birddoc system>
2 3

<!--
Pavel Machek's avatar
Pavel Machek committed
4
	BIRD documentation
5

6 7 8
This documentation can have 4 forms: sgml (this is master copy), html, ASCII
text and dvi/postscript (generated from sgml using sgmltools). You should always
edit master copy.
9

10 11 12 13
This is a slightly modified linuxdoc dtd. Anything in <descrip> tags is
considered definition of configuration primitives, <cf> is fragment of
configuration within normal text, <m> is "meta" information within fragment of
configuration - something in config which is not keyword.
14

15
    (set-fill-column 80)
16 17 18 19 20

    Copyright 1999,2000 Pavel Machek <pavel@ucw.cz>, distribute under GPL version 2 or later.

 -->

21
<book>
22

23
<title>BIRD User's Guide
24
<author>
25 26
Ondrej Filip <it/&lt;feela@network.cz&gt;/,
Pavel Machek <it/&lt;pavel@ucw.cz&gt;/,
27 28
Martin Mares <it/&lt;mj@ucw.cz&gt;/,
Ondrej Zajicek <it/&lt;santiago@crfreenet.org&gt;/
29
</author>
30 31

<abstract>
32
This document contains user documentation for the BIRD Internet Routing Daemon project.
33 34 35 36 37 38 39
</abstract>

<!-- Table of contents -->
<toc>

<!-- Begin the document -->

40

41
<chapt>Introduction
42
<label id="intro">
43

44
<sect>What is BIRD
45
<label id="what-is-bird">
46

47
<p>The name `BIRD' is actually an acronym standing for `BIRD Internet Routing
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
Daemon'. Let's take a closer look at the meaning of the name:

<p><em/BIRD/: Well, we think we have already explained that. It's an acronym
standing for `BIRD Internet Routing Daemon', you remember, don't you? :-)

<p><em/Internet Routing/: It's a program (well, a daemon, as you are going to
discover in a moment) which works as a dynamic router in an Internet type
network (that is, in a network running either the IPv4 or the IPv6 protocol).
Routers are devices which forward packets between interconnected networks in
order to allow hosts not connected directly to the same local area network to
communicate with each other. They also communicate with the other routers in the
Internet to discover the topology of the network which allows them to find
optimal (in terms of some metric) rules for forwarding of packets (which are
called routing tables) and to adapt themselves to the changing conditions such
as outages of network links, building of new connections and so on. Most of
these routers are costly dedicated devices running obscure firmware which is
hard to configure and not open to any changes (on the other hand, their special
hardware design allows them to keep up with lots of high-speed network
interfaces, better than general-purpose computer does). Fortunately, most
operating systems of the UNIX family allow an ordinary computer to act as a
router and forward packets belonging to the other hosts, but only according to a
statically configured table.

<p>A <em/Routing Daemon/ is in UNIX terminology a non-interactive program
running on background which does the dynamic part of Internet routing, that is
it communicates with the other routers, calculates routing tables and sends them
to the OS kernel which does the actual packet forwarding. There already exist
other such routing daemons: routed (RIP only), GateD (non-free),
76 77
<HTMLURL URL="http://www.zebra.org" name="Zebra"> and
<HTMLURL URL="http://sourceforge.net/projects/mrt" name="MRTD">,
78 79
but their capabilities are limited and they are relatively hard to configure
and maintain.
80 81

<p>BIRD is an Internet Routing Daemon designed to avoid all of these shortcomings,
82 83 84 85
to support all the routing technology used in the today's Internet or planned to
be used in near future and to have a clean extensible architecture allowing new
routing protocols to be incorporated easily. Among other features, BIRD
supports:
86 87 88 89 90

<itemize>
	<item>both IPv4 and IPv6 protocols
	<item>multiple routing tables
	<item>the Border Gateway Protocol (BGPv4)
91
	<item>the Routing Information Protocol (RIPv2)
92
	<item>the Open Shortest Path First protocol (OSPFv2, OSPFv3)
93
	<item>the Router Advertisements for IPv6 hosts
94 95
	<item>a virtual protocol for exchange of routes between different
		routing tables on a single host
96 97
	<item>a command-line interface allowing on-line control and inspection
		of status of the daemon
98 99 100 101 102
	<item>soft reconfiguration (no need to use complex online commands to
		change the configuration, just edit the configuration file and
		notify BIRD to re-read it and it will smoothly switch itself to
		the new configuration, not disturbing routing protocols unless
		they are affected by the configuration changes)
103
	<item>a powerful language for route filtering
104 105
</itemize>

106 107 108 109 110 111 112 113
<p>BIRD has been developed at the Faculty of Math and Physics, Charles
University, Prague, Czech Republic as a student project. It can be freely
distributed under the terms of the GNU General Public License.

<p>BIRD has been designed to work on all UNIX-like systems. It has been
developed and tested under Linux 2.0 to 2.6, and then ported to FreeBSD, NetBSD
and OpenBSD, porting to other systems (even non-UNIX ones) should be relatively
easy due to its highly modular architecture.
114

115 116 117 118
<p>BIRD supports either IPv4 or IPv6 protocol, but have to be compiled separately
for each one. Therefore, a dualstack router would run two instances of BIRD (one
for IPv4 and one for IPv6), with completely separate setups (configuration
files, tools ...).
119

120

121
<sect>Installing BIRD
122
<label id="install">
123

124 125
<p>On a recent UNIX system with GNU development tools (GCC, binutils, m4, make)
and Perl, installing BIRD should be as easy as:
126 127

<code>
128 129 130 131
	./configure
	make
	make install
	vi /usr/local/etc/bird.conf
Pavel Machek's avatar
Pavel Machek committed
132
	bird
133 134
</code>

135
<p>You can use <tt>./configure --help</tt> to get a list of configure
136 137 138 139 140
options. The most important ones are: <tt/--enable-ipv6/ which enables building
of an IPv6 version of BIRD, <tt/--with-protocols=/ to produce a slightly smaller
BIRD executable by configuring out routing protocols you don't use, and
<tt/--prefix=/ to install BIRD to a place different from <file>/usr/local</file>.

141

142
<sect>Running BIRD
143
<label id="argv">
144

Pavel Machek's avatar
Pavel Machek committed
145
<p>You can pass several command-line options to bird:
146

Pavel Machek's avatar
Pavel Machek committed
147
<descrip>
148
	<tag><label id="argv-config">-c <m/config name/</tag>
Martin Mareš's avatar
Martin Mareš committed
149
	use given configuration file instead of <it/prefix/<file>/etc/bird.conf</file>.
Pavel Machek's avatar
Pavel Machek committed
150

151
	<tag><label id="argv-debug">-d</tag>
152
	enable debug messages and run bird in foreground.
Pavel Machek's avatar
Pavel Machek committed
153

154
	<tag><label id="argv-log-file">-D <m/filename of debug log/</tag>
155 156
	log debugging information to given file instead of stderr.

157 158
	<tag><label id="argv-foreground">-f</tag>
	run bird in foreground.
159

160
	<tag><label id="argv-group">-g <m/group/</tag>
161
	use that group ID, see the next section for details.
162

163 164
	<tag><label id="argv-help">-h, --help</tag>
	display command-line options to bird.
165

166
	<tag><label id="argv-local">-l</tag>
167
	look for a configuration file and a communication socket in the current
Ondřej Zajíček's avatar
Ondřej Zajíček committed
168
	working directory instead of in default system locations. However, paths
169 170
	specified by options <cf/-c/, <cf/-s/ have higher priority.

171 172 173 174 175 176 177
	<tag><label id="argv-parse">-p</tag>
	just parse the config file and exit. Return value is zero if the config
	file is valid, nonzero if there are some errors.

	<tag><label id="argv-pid">-P <m/name of PID file/</tag>
	create a PID file with given filename.

178
	<tag><label id="argv-recovery">-R</tag>
179
	apply graceful restart recovery after start.
180

181 182 183 184 185 186 187
	<tag><label id="argv-socket">-s <m/name of communication socket/</tag>
	use given filename for a socket for communications with the client,
	default is <it/prefix/<file>/var/run/bird.ctl</file>.

	<tag><label id="argv-user">-u <m/user/</tag>
	drop privileges and use that user ID, see the next section for details.

188 189
	<tag><label id="argv-version">--version</tag>
	display bird version.
Pavel Machek's avatar
Pavel Machek committed
190
</descrip>
191

192 193
<p>BIRD writes messages about its work to log files or syslog (according to config).

194

195
<sect>Privileges
196
<label id="privileges">
197

198 199 200 201 202 203 204 205 206 207
<p>BIRD, as a routing daemon, uses several privileged operations (like setting
routing table and using raw sockets). Traditionally, BIRD is executed and runs
with root privileges, which may be prone to security problems. The recommended
way is to use a privilege restriction (options <cf/-u/, <cf/-g/). In that case
BIRD is executed with root privileges, but it changes its user and group ID to
an unprivileged ones, while using Linux capabilities to retain just required
privileges (capabilities CAP_NET_*). Note that the control socket is created
before the privileges are dropped, but the config file is read after that. The
privilege restriction is not implemented in BSD port of BIRD.

208
<p>An unprivileged user (as an argument to <cf/-u/ options) may be the user
209 210 211 212 213 214 215 216 217
<cf/nobody/, but it is suggested to use a new dedicated user account (like
<cf/bird/). The similar considerations apply for the group option, but there is
one more condition -- the users in the same group can use <file/birdc/ to
control BIRD.

<p>Finally, there is a possibility to use external tools to run BIRD in an
environment with restricted privileges. This may need some configuration, but it
is generally easy -- BIRD needs just the standard library, privileges to read
the config file and create the control socket and the CAP_NET_* capabilities.
218

219

220
<chapt>About routing tables
221
<label id="routing-tables">
222

223 224 225 226
<p>BIRD has one or more routing tables which may or may not be synchronized with
OS kernel and which may or may not be synchronized with each other (see the Pipe
protocol). Each routing table contains a list of known routes. Each route
consists of:
227 228

<itemize>
229 230 231
	<item>network prefix this route is for (network address and prefix
		length -- the number of bits forming the network part of the
		address; also known as a netmask)
232 233
	<item>preference of this route
	<item>IP address of router which told us about this route
234 235
	<item>IP address of router we should forward the packets to using this
		route
236
	<item>other attributes common to all routes
237 238
	<item>dynamic attributes defined by protocols which may or may not be
		present (typically protocol metrics)
239 240
</itemize>

241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258
Routing table maintains multiple entries for a network, but at most one entry
for one network and one protocol. The entry with the highest preference is used
for routing (we will call such an entry the <it/selected route/). If there are
more entries with the same preference and they are from the same protocol, the
protocol decides (typically according to metrics). If they aren't, an internal
ordering is used to break the tie. You can get the list of route attributes in
the Route attributes section.

<p>Each protocol is connected to a routing table through two filters which can
accept, reject and modify the routes. An <it/export/ filter checks routes passed
from the routing table to the protocol, an <it/import/ filter checks routes in
the opposite direction. When the routing table gets a route from a protocol, it
recalculates the selected route and broadcasts it to all protocols connected to
the table. The protocols typically send the update to other routers in the
network. Note that although most protocols are interested in receiving just
selected routes, some protocols (e.g. the <cf/Pipe/ protocol) receive and
process all entries in routing tables (accepted by filters).

259
<p><label id="dsc-table-sorted">Usually, a routing table just chooses a selected route
260 261 262 263 264 265 266 267 268 269 270
from a list of entries for one network. But if the <cf/sorted/ option is
activated, these lists of entries are kept completely sorted (according to
preference or some protocol-dependent metric). This is needed for some features
of some protocols (e.g. <cf/secondary/ option of BGP protocol, which allows to
accept not just a selected route, but the first route (in the sorted list) that
is accepted by filters), but it is incompatible with some other features (e.g.
<cf/deterministic med/ option of BGP protocol, which activates a way of choosing
selected route that cannot be described using comparison and ordering). Minor
advantage is that routes are shown sorted in <cf/show route/, minor disadvantage
is that it is slightly more computationally expensive.

271

272
<sect>Graceful restart
273
<label id="graceful-restart">
274 275 276 277 278 279 280 281 282 283 284 285 286

<p>When BIRD is started after restart or crash, it repopulates routing tables in
an uncoordinated manner, like after clean start. This may be impractical in some
cases, because if the forwarding plane (i.e. kernel routing tables) remains
intact, then its synchronization with BIRD would temporarily disrupt packet
forwarding until protocols converge. Graceful restart is a mechanism that could
help with this issue. Generally, it works by starting protocols and letting them
repopulate routing tables while deferring route propagation until protocols
acknowledge their convergence. Note that graceful restart behavior have to be
configured for all relevant protocols and requires protocol-specific support
(currently implemented for Kernel and BGP protocols), it is activated for
particular boot by option <cf/-R/.

287

288
<chapt>Configuration
289
<label id="config">
Pavel Machek's avatar
Pavel Machek committed
290

291
<sect>Introduction
292
<label id="config-intro">
293

294 295 296 297 298 299 300 301 302 303 304
<p>BIRD is configured using a text configuration file. Upon startup, BIRD reads
<it/prefix/<file>/etc/bird.conf</file> (unless the <tt/-c/ command line option
is given). Configuration may be changed at user's request: if you modify the
config file and then signal BIRD with <tt/SIGHUP/, it will adjust to the new
config. Then there's the client which allows you to talk with BIRD in an
extensive way.

<p>In the config, everything on a line after <cf/#/ or inside <cf>/* */</cf> is
a comment, whitespace characters are treated as a single space. If there's a
variable number of options, they are grouped using the <cf/{ }/ brackets. Each
option is terminated by a <cf/;/. Configuration is case sensitive. There are two
305
ways how to name symbols (like protocol names, filter names, constants etc.). You
306 307 308 309 310 311 312 313 314
can either use a simple string starting with a letter followed by any
combination of letters and numbers (e.g. "R123", "myfilter", "bgp5") or you can
enclose the name into apostrophes (<cf/'/) and than you can use any combination
of numbers, letters. hyphens, dots and colons (e.g. "'1:strange-name'",
"'-NAME-'", "'cool::name'").

<p>Here is an example of a simple config file. It enables synchronization of
routing tables with OS kernel, scans for new network interfaces every 10 seconds
and runs RIP on all network interfaces found.
315

316
<code>
317
protocol kernel {
Pavel Machek's avatar
Pavel Machek committed
318
	persist;		# Don't remove routes on BIRD shutdown
319 320 321 322 323 324 325 326 327 328 329
	scan time 20;		# Scan kernel routing table every 20 seconds
	export all;		# Default is export none
}

protocol device {
	scan time 10;		# Scan interfaces every 10 seconds
}

protocol rip {
	export all;
	import all;
330
	interface "*";
331
}
332
</code>
333

334

335
<sect>Global options
336
<label id="global-opts">
Pavel Machek's avatar
Pavel Machek committed
337

338
<p><descrip>
339
	<tag><label id="opt-include">include "<m/filename/"</tag>
340
	This statement causes inclusion of a new file. <m/Filename/ could also
341 342 343
	be a wildcard, in that case matching files are included in alphabetic
	order. The maximal depth is 8. Note that this statement could be used
	anywhere in the config file, not just as a top-level option.
344

345
	<tag><label id="opt-log">log "<m/filename/"|syslog [name <m/name/]|stderr all|{ <m/list of classes/ }</tag>
346
	Set logging of messages having the given class (either <cf/all/ or
347
	<cf/{ error|trace [, <m/.../] }/ etc.) into selected destination (a file specified
348 349
	as a filename string, syslog with optional name argument, or the stderr
	output). Classes are:
350
	<cf/info/, <cf/warning/, <cf/error/ and <cf/fatal/ for messages about local problems,
351 352 353
	<cf/debug/ for debugging messages,
	<cf/trace/ when you want to know what happens in the network,
	<cf/remote/ for messages about misbehavior of remote machines,
354
	<cf/auth/ about authentication failures,
355 356 357
	<cf/bug/ for internal BIRD bugs.
	You may specify more than one <cf/log/ line to establish logging to
	multiple destinations. Default: log everything to the system log.
358

359
	<tag><label id="opt-debug-protocols">debug protocols all|off|{ states|routes|filters|interfaces|events|packets [, <m/.../] }</tag>
360 361
	Set global defaults of protocol debugging options. See <cf/debug/ in the
	following section. Default: off.
Pavel Machek's avatar
Pavel Machek committed
362

363
	<tag><label id="opt-debug-commands">debug commands <m/number/</tag>
364 365 366
	Control logging of client connections (0 for no logging, 1 for logging
	of connects and disconnects, 2 and higher for logging of all client
	commands). Default: 0.
367

368
	<tag><label id="opt-debug-latency">debug latency <m/switch/</tag>
369 370 371
	Activate tracking of elapsed time for internal events. Recent events
	could be examined using <cf/dump events/ command. Default: off.

372
	<tag><label id="opt-debug-latency-limit">debug latency limit <m/time/</tag>
373 374 375
	If <cf/debug latency/ is enabled, this option allows to specify a limit
	for elapsed time. Events exceeding the limit are logged. Default: 1 s.

376
	<tag><label id="opt-watchdog-warn">watchdog warning <m/time/</tag>
377 378 379
	Set time limit for I/O loop cycle. If one iteration took more time to
	complete, a warning is logged. Default: 5 s.

380
	<tag><label id="opt-watchdog-timeout">watchdog timeout <m/time/</tag>
381 382 383 384
	Set time limit for I/O loop cycle. If the limit is breached, BIRD is
	killed by abort signal. The timeout has effective granularity of
	seconds, zero means disabled. Default: disabled (0).

385
	<tag><label id="opt-mrtdump">mrtdump "<m/filename/"</tag>
386 387
	Set MRTdump file name. This option must be specified to allow MRTdump
	feature. Default: no dump file.
388

389
	<tag><label id="opt-mrtdump-protocols">mrtdump protocols all|off|{ states|messages [, <m/.../] }</tag>
390 391
	Set global defaults of MRTdump options. See <cf/mrtdump/ in the
	following section. Default: off.
392

393
	<tag><label id="opt-filter">filter <m/name local variables/{ <m/commands/ }</tag>
394 395
	Define a filter. You can learn more about filters in the following
	chapter.
396

397
	<tag><label id="opt-function">function <m/name/ (<m/parameters/) <m/local variables/ { <m/commands/ }</tag>
398
	Define a function. You can learn more about functions in the following chapter.
399

400
	<tag><label id="opt-protocol">protocol rip|ospf|bgp|<m/.../ [<m/name/ [from <m/name2/]] { <m>protocol options</m> }</tag>
401 402 403 404 405 406 407
	Define a protocol instance called <cf><m/name/</cf> (or with a name like
	"rip5" generated automatically if you don't specify any
	<cf><m/name/</cf>). You can learn more about configuring protocols in
	their own chapters. When <cf>from <m/name2/</cf> expression is used,
	initial protocol options are taken from protocol or template
	<cf><m/name2/</cf> You can run more than one instance of most protocols
	(like RIP or BGP). By default, no instances are configured.
408

409
	<tag><label id="opt-template">template rip|bgp|<m/.../ [<m/name/ [from <m/name2/]] { <m>protocol options</m> }</tag>
410 411 412 413 414 415 416
	Define a protocol template instance called <m/name/ (or with a name like
	"bgp1" generated automatically if you don't specify any	<m/name/).
	Protocol templates can be used to group common options when many
	similarly configured protocol instances are to be defined. Protocol
	instances (and other templates) can use templates by using <cf/from/
	expression and the name of the template. At the moment templates (and
	<cf/from/ expression) are not implemented for OSPF protocol.
417

418
	<tag><label id="opt-define">define <m/constant/ = <m/expression/</tag>
419 420 421 422
	Define a constant. You can use it later in every place you could use a
	value of the same type. Besides, there are some predefined numeric
	constants based on /etc/iproute2/rt_* files. A list of defined constants
	can be seen (together with other symbols) using 'show symbols' command.
423

424 425
	<tag><label id="opt-router-id">router id <m/IPv4 address/</tag>
	Set BIRD's router ID. It's a world-wide unique identification of your
426 427 428
	router, usually one of router's IPv4 addresses. Default: in IPv4
	version, the lowest IP address of a non-loopback interface. In IPv6
	version, this option is mandatory.
429

430
	<tag><label id="opt-router-id-from">router id from [-] [ "<m/mask/" ] [ <m/prefix/ ] [, <m/.../]</tag>
431 432
	Set BIRD's router ID based on an IP address of an interface specified by
	an interface pattern. The option is applicable for IPv4 version only.
433
	See <ref id="proto-iface" name="interface"> section for detailed
434
	description of interface patterns with extended clauses.
435

436
	<tag><label id="opt-listen-bgp">listen bgp [address <m/address/] [port <m/port/] [dual]</tag>
437 438 439 440 441 442 443
	This option allows to specify address and port where BGP protocol should
	listen. It is global option as listening socket is common to all BGP
	instances. Default is to listen on all addresses (0.0.0.0) and port 179.
	In IPv6 mode, option <cf/dual/ can be used to specify that BGP socket
	should accept both IPv4 and IPv6 connections (but even in that case,
	BIRD would accept IPv6 routes only). Such behavior was default in older
	versions of BIRD.
Ondřej Zajíček's avatar
Ondřej Zajíček committed
444

445
	<tag><label id="opt-graceful-restart">graceful restart wait <m/number/</tag>
446 447 448 449 450
	During graceful restart recovery, BIRD waits for convergence of routing
	protocols. This option allows to specify a timeout for the recovery to
	prevent waiting indefinitely if some protocols cannot converge. Default:
	240 seconds.

451
	<tag><label id="opt-timeformat">timeformat route|protocol|base|log "<m/format1/" [<m/limit/ "<m/format2/"]</tag>
452 453 454 455 456 457 458 459 460 461 462 463 464 465 466
	This option allows to specify a format of date/time used by BIRD. The
	first argument specifies for which purpose such format is used.
	<cf/route/ is a format used in 'show route' command output,
	<cf/protocol/ is used in 'show protocols' command output, <cf/base/ is
	used for other commands and <cf/log/ is used in a log file.

	"<m/format1/" is a format string using <it/strftime(3)/ notation (see
	<it/man strftime/ for details). <m/limit> and "<m/format2/" allow to
	specify the second format string for times in past deeper than <m/limit/
 	seconds. There are few shorthands: <cf/iso long/ is a ISO 8601 date/time
	format (YYYY-MM-DD hh:mm:ss) that can be also specified using <cf/"%F %T"/.
	<cf/iso short/ is a variant of ISO 8601 that uses just the time format
	(hh:mm:ss) for near times (up to 20 hours in the past) and the date
	format (YYYY-MM-DD) for far times. This is a shorthand for
	<cf/"%T" 72000 "%F"/.
467

468 469 470 471
	By default, BIRD uses the <cf/iso short/ format for <cf/route/ and
	<cf/protocol/ times, and the <cf/iso long/ format for <cf/base/ and
	<cf/log/ times.

472 473 474 475
	In pre-1.4.0 versions, BIRD used an short, ad-hoc format for <cf/route/
	and <cf/protocol/ times, and a <cf/iso long/ similar format (DD-MM-YYYY
	hh:mm:ss) for <cf/base/ and <cf/log/. These timeformats could be set by
	<cf/old short/ and <cf/old long/ compatibility shorthands.
476

477
	<tag><label id="opt-table">table <m/name/ [sorted]</tag>
478 479 480
	Create a new routing table. The default routing table is created
	implicitly, other routing tables have to be added by this command.
	Option <cf/sorted/ can be used to enable sorting of routes, see
481
	<ref id="dsc-table-sorted" name="sorted table"> description for details.
Pavel Machek's avatar
Pavel Machek committed
482

483
	<tag><label id="opt-roa-table">roa table <m/name/ [ { <m/roa table options .../ } ]</tag>
484 485 486 487
	Create a new ROA (Route Origin Authorization) table. ROA tables can be
	used to validate route origination of BGP routes. A ROA table contains
	ROA entries, each consist of a network prefix, a max prefix length and
	an AS number. A ROA entry specifies prefixes which could be originated
488 489 490
	by that AS number. ROA tables could be filled with data from RPKI (<rfc
	id="6480">) or from public databases like Whois. ROA tables are
	examined by <cf/roa_check()/ operator in filters.
491 492 493 494 495

	Currently, there is just one option, <cf>roa <m/prefix/ max <m/num/ as
	<m/num/</cf>, which can be used to populate the ROA table with static
	ROA entries. The option may be used multiple times. Other entries can be
	added dynamically by <cf/add roa/ command.
496

497
	<tag><label id="opt-eval">eval <m/expr/</tag>
Ondřej Zajíček's avatar
Ondřej Zajíček committed
498
	Evaluates given filter expression. It is used by us for	testing of filters.
499 500
</descrip>

501

502
<sect>Protocol options
503
<label id="protocol-opts">
504

505 506 507
<p>For each protocol instance, you can configure a bunch of options. Some of
them (those described in this section) are generic, some are specific to the
protocol (see sections talking about the protocols).
508

509 510 511 512 513
<p>Several options use a <m/switch/ argument. It can be either <cf/on/,
<cf/yes/ or a numeric expression with a non-zero value for the option to be
enabled or <cf/off/, <cf/no/ or a numeric expression evaluating to zero to
disable it. An empty <m/switch/ is equivalent to <cf/on/ ("silence means
agreement").
514

Pavel Machek's avatar
Pavel Machek committed
515
<descrip>
516
	<tag><label id="proto-preference">preference <m/expr/</tag>
517 518
	Sets the preference of routes generated by this protocol. Default:
	protocol dependent.
Pavel Machek's avatar
Pavel Machek committed
519

520
	<tag><label id="proto-disabled">disabled <m/switch/</tag>
521 522 523
	Disables the protocol. You can change the disable/enable status from the
	command line interface without needing to touch the configuration.
	Disabled protocols are not activated. Default: protocol is enabled.
Pavel Machek's avatar
Pavel Machek committed
524

525
	<tag><label id="proto-debug">debug all|off|{ states|routes|filters|interfaces|events|packets [, <m/.../] }</tag>
Pavel Machek's avatar
Pavel Machek committed
526 527 528 529
	Set protocol debugging options. If asked, each protocol is capable of
	writing trace messages about its work to the log (with category
	<cf/trace/). You can either request printing of <cf/all/ trace messages
	or only of the types selected: <cf/states/ for protocol state changes
530 531 532 533 534
	(protocol going up, down, starting, stopping etc.), <cf/routes/ for
	routes exchanged with the routing table, <cf/filters/ for details on
	route filtering, <cf/interfaces/ for interface change events sent to the
	protocol, <cf/events/ for events internal to the protocol and <cf/packets/
	for packets sent and received by the protocol. Default: off.
Pavel Machek's avatar
Pavel Machek committed
535

536
	<tag><label id="proto-mrtdump">mrtdump all|off|{ states|messages [, <m/.../] }</tag>
537 538 539 540 541 542 543 544
	Set protocol MRTdump flags. MRTdump is a standard binary format for
	logging information from routing protocols and daemons. These flags
	control what kind of information is logged from the protocol to the
	MRTdump file (which must be specified by global <cf/mrtdump/ option, see
	the previous section). Although these flags are similar to flags of
	<cf/debug/ option, their meaning is different and protocol-specific. For
	BGP protocol, <cf/states/ logs BGP state changes and <cf/messages/ logs
	received BGP messages. Other protocols does not support MRTdump yet.
545

546
	<tag><label id="proto-router-id">router id <m/IPv4 address/</tag>
547 548
	This option can be used to override global router id for a given
	protocol. Default: uses global router id.
549

550
	<tag><label id="proto-import">import all | none | filter <m/name/ | filter { <m/filter commands/ } | where <m/filter expression/</tag>
551 552 553
	Specify a filter to be used for filtering routes coming from the
	protocol to the routing table. <cf/all/ is shorthand for <cf/where true/
	and <cf/none/ is shorthand for <cf/where false/. Default: <cf/all/.
554

555
	<tag><label id="proto-export">export <m/filter/</tag>
556 557
	This is similar to the <cf>import</cf> keyword, except that it works in
	the direction from the routing table to the protocol. Default: <cf/none/.
Pavel Machek's avatar
Pavel Machek committed
558

559
	<tag><label id="proto-import-keep-filtered">import keep filtered <m/switch/</tag>
560 561 562 563 564
	Usually, if an import filter rejects a route, the route is forgotten.
	When this option is active, these routes are kept in the routing table,
	but they are hidden and not propagated to other protocols. But it is
	possible to show them using <cf/show route filtered/. Note that this
	option does not work for the pipe protocol. Default: off.
565

566
	<tag><label id="proto-import-limit">import limit [<m/number/ | off ] [action warn | block | restart | disable]</tag>
567 568 569 570 571 572 573
	Specify an import route limit (a maximum number of routes imported from
	the protocol) and optionally the action to be taken when the limit is
	hit. Warn action just prints warning log message. Block action discards
	new routes coming from the protocol. Restart and disable actions shut
	the protocol down like appropriate commands. Disable is the default
	action if an action is not explicitly specified. Note that limits are
	reset during protocol reconfigure, reload or restart. Default: <cf/off/.
574

575
	<tag><label id="proto-receive-limit">receive limit [<m/number/ | off ] [action warn | block | restart | disable]</tag>
576 577 578 579 580 581 582 583
	Specify an receive route limit (a maximum number of routes received from
	the protocol and remembered). It works almost identically to <cf>import
	limit</cf> option, the only difference is that if <cf/import keep
	filtered/ option is active, filtered routes are counted towards the
	limit and blocked routes are forgotten, as the main purpose of the
	receive limit is to protect routing tables from overflow. Import limit,
	on the contrary, counts accepted routes only and routes blocked by the
	limit are handled like filtered routes. Default: <cf/off/.
584

585
	<tag><label id="proto-export-limit">export limit [ <m/number/ | off ] [action warn | block | restart | disable]</tag>
586 587 588 589 590 591 592 593
	Specify an export route limit, works similarly to the <cf>import
	limit</cf> option, but for the routes exported to the protocol. This
	option is experimental, there are some problems in details of its
	behavior -- the number of exported routes can temporarily exceed the
	limit without triggering it during protocol reload, exported routes
	counter ignores route blocking and block action also blocks route
	updates of already accepted routes -- and these details will probably
	change in the future. Default: <cf/off/.
594

595
	<tag><label id="proto-description">description "<m/text/"</tag>
596
	This is an optional description of the protocol. It is displayed as a
597
	part of the output of 'show protocols all' command.
598

599
	<tag><label id="proto-table">table <m/name/</tag>
Ondřej Zajíček's avatar
Ondřej Zajíček committed
600
	Connect this protocol to a non-default routing table.
Ondřej Zajíček's avatar
Ondřej Zajíček committed
601 602 603 604 605 606

	<tag><label id="proto-vrf">vrf "<m/text/"</tag>
	Associate the protocol with specific VRF. The protocol will be
	restricted to interfaces assigned to the VRF and will use sockets bound
	to the VRF. Appropriate VRF interface must exist on OS level. For kernel
	protocol, an appropriate table still must be explicitly selected by
607 608 609
	<cf/table/ option. Note that for proper VRF support it is necessary to
	use Linux kernel version at least 4.14, older versions have limited
	VRF implementation.
610 611
</descrip>

612
<p>There are several options that give sense only with certain protocols:
613 614

<descrip>
615
	<tag><label id="proto-iface">interface [-] [ "<m/mask/" ] [ <m/prefix/ ] [, <m/.../] [ { <m/option/; [<m/.../] } ]</tag>
616 617
	Specifies a set of interfaces on which the protocol is activated with
	given interface-specific options. A set of interfaces specified by one
618 619
	interface option is described using an interface pattern. The interface
	pattern consists of a sequence of clauses (separated by commas), each
620 621
	clause is a mask specified as a shell-like pattern. Interfaces are
	matched by their name.
622 623 624

	An interface matches the pattern if it matches any of its clauses. If
	the clause begins with <cf/-/, matching interfaces are excluded. Patterns
625
	are processed left-to-right, thus <cf/interface "eth0", -"eth*", "*";/
626 627
	means eth0 and all non-ethernets.

628 629 630 631 632 633
	Some protocols (namely OSPFv2 and Direct) support extended clauses that
	may contain a mask, a prefix, or both of them. An interface matches such
	clause if its name matches the mask (if specified) and its address
	matches the prefix (if specified). Extended clauses are used when the
	protocol handles multiple addresses on an interface independently.

634 635 636
	An interface option can be used more times with different interface-specific
	options, in that case for given interface the first matching interface
	option is used.
637

638 639
	This option is allowed in Babel, BFD, Direct, OSPF, RAdv and RIP
	protocols, but in OSPF protocol it is used in the <cf/area/ subsection.
640 641 642 643 644

	Default: none.

	Examples:

645 646
	<cf>interface "*" { type broadcast; };</cf> - start the protocol on all
	interfaces with <cf>type broadcast</cf> option.
647

648 649
	<cf>interface "eth1", "eth4", "eth5" { type ptp; };</cf> - start the
	protocol on enumerated interfaces with <cf>type ptp</cf> option.
650

651 652 653
	<cf>interface -192.168.1.0/24, 192.168.0.0/16;</cf> - start the protocol
	on all interfaces that have address from 192.168.0.0/16, but not from
	192.168.1.0/24.
654

655 656 657
	<cf>interface -192.168.1.0/24, 192.168.0.0/16;</cf> - start the protocol
	on all interfaces that have address from 192.168.0.0/16, but not from
	192.168.1.0/24.
658 659 660 661

	<cf>interface "eth*" 192.168.1.0/24;</cf> - start the protocol on all
	ethernet interfaces that have address from 192.168.1.0/24.

662
	<tag><label id="proto-tx-class">tx class|dscp <m/num/</tag>
663 664 665 666 667 668 669
	This option specifies the value of ToS/DS/Class field in IP headers of
	the outgoing protocol packets. This may affect how the protocol packets
	are processed by the network relative to the other network traffic. With
	<cf/class/ keyword, the value (0-255) is used for the whole ToS/Class
	octet (but two bits reserved for ECN are ignored). With	<cf/dscp/
	keyword, the value (0-63) is used just for the DS field in the octet.
	Default value is 0xc0 (DSCP 0x30 - CS6).
670

671
	<tag><label id="proto-tx-priority">tx priority <m/num/</tag>
672 673 674
	This option specifies the local packet priority. This may affect how the
	protocol packets are processed in the local TX queues. This option is
	Linux specific. Default value is 7 (highest priority, privileged traffic).
675

676 677 678 679 680 681 682
	<tag><label id="proto-pass">password "<m/password/" [ { <m>password options</m> } ]</tag>
	Specifies a password that can be used by the protocol as a shared secret
	key. Password option can be used more times to specify more passwords.
	If more passwords are specified, it is a protocol-dependent decision
	which one is really used. Specifying passwords does not mean that
	authentication is enabled, authentication can be enabled by separate,
	protocol-dependent <cf/authentication/ option.
683

Ondřej Zajíček's avatar
Ondřej Zajíček committed
684
	This option is allowed in BFD, OSPF and RIP protocols. BGP has also
685 686 687 688 689 690 691 692
	<cf/password/ option, but it is slightly different and described
	separately.
	Default: none.
</descrip>

<p>Password option can contain section with some (not necessary all) password sub-options:

<descrip>
693
	<tag><label id="proto-pass-id">id <M>num</M></tag>
694
	ID of the password, (1-255). If it is not used, BIRD will choose ID based
695 696 697 698
	on an order of the password item in the interface. For example, second
	password item in one interface will have default ID 2. ID is used by
	some routing protocols to identify which password was used to
	authenticate protocol packets.
699

700
	<tag><label id="proto-pass-gen-from">generate from "<m/time/"</tag>
701 702
	The start time of the usage of the password for packet signing.
	The format of <cf><m/time/</cf> is <tt>dd-mm-yyyy HH:MM:SS</tt>.
703

704
	<tag><label id="proto-pass-gen-to">generate to "<m/time/"</tag>
705
	The last time of the usage of the password for packet signing.
706

707
	<tag><label id="proto-pass-accept-from">accept from "<m/time/"</tag>
708
	The start time of the usage of the password for packet verification.
Pavel Machek's avatar
Pavel Machek committed
709

710
	<tag><label id="proto-pass-accept-to">accept to "<m/time/"</tag>
711
	The last time of the usage of the password for packet verification.
712 713 714 715 716 717 718 719 720 721 722 723 724

	<tag><label id="proto-pass-from">from "<m/time/"</tag>
	Shorthand for setting both <cf/generate from/ and <cf/accept from/.

	<tag><label id="proto-pass-to">to "<m/time/"</tag>
	Shorthand for setting both <cf/generate to/ and <cf/accept to/.

	<tag><label id="proto-pass-algorithm">algorithm ( keyed md5 | keyed sha1 | hmac sha1 | hmac sha256 | hmac sha384 | hmac sha512 )</tag>
	The message authentication algorithm for the password when cryptographic
	authentication is enabled. The default value depends on the protocol.
	For RIP and OSPFv2 it is Keyed-MD5 (for compatibility), for OSPFv3
	protocol it is HMAC-SHA-256.

725
</descrip>
726

Pavel Machek's avatar
Pavel Machek committed
727
<chapt>Remote control
728
<label id="remote-control">
729

730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746
<p>You can use the command-line client <file>birdc</file> to talk with a running
BIRD. Communication is done using a <file/bird.ctl/ UNIX domain socket (unless
changed with the <tt/-s/ option given to both the server and the client). The
commands can perform simple actions such as enabling/disabling of protocols,
telling BIRD to show various information, telling it to show routing table
filtered by filter, or asking BIRD to reconfigure. Press <tt/?/ at any time to
get online help. Option <tt/-r/ can be used to enable a restricted mode of BIRD
client, which allows just read-only commands (<cf/show .../). Option <tt/-v/ can
be passed to the client, to make it dump numeric return codes along with the
messages. You do not necessarily need to use <file/birdc/ to talk to BIRD, your
own applications could do that, too -- the format of communication between BIRD
and <file/birdc/ is stable (see the programmer's documentation).

<p>There is also lightweight variant of BIRD client called <file/birdcl/, which
does not support command line editing and history and has minimal dependencies.
This is useful for running BIRD in resource constrained environments, where
Readline library (required for regular BIRD client) is not available.
747 748

<p>Many commands have the <m/name/ of the protocol instance as an argument.
749 750
This argument can be omitted if there exists only a single instance.

Pavel Machek's avatar
Pavel Machek committed
751
<p>Here is a brief list of supported functions:
752 753

<descrip>
754
	<tag><label id="cli-show-status">show status</tag>
755 756
	Show router status, that is BIRD version, uptime and time from last
	reconfiguration.
Pavel Machek's avatar
Pavel Machek committed
757

758
	<tag><label id="cli-show-interfaces">show interfaces [summary]</tag>
Ondřej Zajíček's avatar
Ondřej Zajíček committed
759 760 761
	Show the list of interfaces. For each interface, print its type, state,
	MTU and addresses assigned.

762
	<tag><label id="cli-show-protocols">show protocols [all]</tag>
763 764 765
	Show list of protocol instances along with tables they are connected to
	and protocol status, possibly giving verbose information, if <cf/all/ is
	specified.
766

767
	<tag><label id="cli-show-ospf-iface">show ospf interface [<m/name/] ["<m/interface/"]</tag>
768 769
	Show detailed information about OSPF interfaces.

770
	<tag><label id="cli-show-ospf-neighbors">show ospf neighbors [<m/name/] ["<m/interface/"]</tag>
771 772
	Show a list of OSPF neighbors and a state of adjacency to them.

773
	<tag><label id="cli-show-ospf-state">show ospf state [all] [<m/name/]</tag>
774 775 776 777 778 779
	Show detailed information about OSPF areas based on a content of the
	link-state database. It shows network topology, stub networks,
	aggregated networks and routers from other areas and external routes.
	The command shows information about reachable network nodes, use option
	<cf/all/ to show information about all network nodes in the link-state
	database.
780

781
	<tag><label id="cli-show-ospf-topology">show ospf topology [all] [<m/name/]</tag>
782 783
	Show a topology of OSPF areas based on a content of the link-state
	database. It is just a stripped-down version of 'show ospf state'.
784

785
	<tag><label id="cli-show-ospf-lsadb">show ospf lsadb [global | area <m/id/ | link] [type <m/num/] [lsid <m/id/] [self | router <m/id/] [<m/name/] </tag>
786 787
	Show contents of an OSPF LSA database. Options could be used to filter
	entries.
788

789
	<tag><label id="cli-show-rip-interfaces">show rip interfaces [<m/name/] ["<m/interface/"]</tag>
Ondřej Zajíček's avatar
Ondřej Zajíček committed
790 791
	Show detailed information about RIP interfaces.

792
	<tag><label id="cli-show-rip-neighbors">show rip neighbors [<m/name/] ["<m/interface/"]</tag>
Ondřej Zajíček's avatar
Ondřej Zajíček committed
793 794
	Show a list of RIP neighbors and associated state.

795
	<tag><label id="cli-show-static">show static [<m/name/]</tag>
796 797
	Show detailed information about static routes.

798
	<tag><label id="cli-show-bfd-sessions">show bfd sessions [<m/name/]</tag>
799 800
	Show information about BFD sessions.

801
	<tag><label id="cli-show-symbols">show symbols [table|filter|function|protocol|template|roa|<m/symbol/]</tag>
802 803
	Show the list of symbols defined in the configuration (names of
	protocols, routing tables etc.).
Pavel Machek's avatar
Pavel Machek committed
804

805
	<tag><label id="cli-show-route">show route [[for] <m/prefix/|<m/IP/] [table <m/t/] [filter <m/f/|where <m/c/] [(export|preexport|noexport) <m/p/] [protocol <m/p/] [<m/options/]</tag>
806 807 808
	Show contents of a routing table (by default of the main one or the
	table attached to a respective protocol), that is routes, their metrics
	and (in case the <cf/all/ switch is given) all their attributes.
Pavel Machek's avatar
Pavel Machek committed
809 810 811 812 813 814 815 816 817 818 819

	<p>You can specify a <m/prefix/ if you want to print routes for a
	specific network. If you use <cf>for <m/prefix or IP/</cf>, you'll get
	the entry which will be used for forwarding of packets to the given
	destination. By default, all routes for each network are printed with
	the selected one at the top, unless <cf/primary/ is given in which case
	only the selected route is shown.

	<p>You can also ask for printing only routes processed and accepted by
	a given filter (<cf>filter <m/name/</cf> or <cf>filter { <m/filter/ }
	</cf> or matching a given condition (<cf>where <m/condition/</cf>).
820 821 822 823 824 825 826 827

	The <cf/export/, <cf/preexport/ and <cf/noexport/ switches ask for
	printing of routes that are exported to the specified protocol.
	With <cf/preexport/, the export filter of the protocol is skipped.
	With <cf/noexport/, routes rejected by the export filter are printed
	instead. Note that routes not exported to the protocol for other reasons
	(e.g. secondary routes or routes imported from that protocol) are not
	printed even with <cf/noexport/.
Pavel Machek's avatar
Pavel Machek committed
828

829 830 831
	<p>You can also select just routes added by a specific protocol.
	<cf>protocol <m/p/</cf>.

832 833 834
	<p>If BIRD is configured to keep filtered routes (see <cf/import keep
	filtered/ option), you can show them instead of routes by using
	<cf/filtered/ switch.
835

Pavel Machek's avatar
Pavel Machek committed
836 837 838 839
	<p>The <cf/stats/ switch requests showing of route statistics (the
	number of networks, number of routes before and after filtering). If
	you use <cf/count/ instead, only the statistics will be printed.

Ondřej Zajíček's avatar
Ondřej Zajíček committed
840 841 842 843
	<tag><label id="cli-mrt-dump">mrt dump table <m/name/|"<m/pattern/" to "<m/filename/" [filter <m/f/|where <m/c/]</tag>
	Dump content of a routing table to a specified file in MRT table dump
	format. See <ref id="mrt" name="MRT protocol"> for details.

844
	<tag><label id="cli-show-roa">show roa [<m/prefix/ | in <m/prefix/ | for <m/prefix/] [as <m/num/] [table <m/t/]</tag>
845 846 847 848 849 850
	Show contents of a ROA table (by default of the first one). You can
	specify a <m/prefix/ to print ROA entries for a specific network. If you
	use <cf>for <m/prefix/</cf>, you'll get all entries relevant for route
	validation of the network prefix; i.e., ROA entries whose prefixes cover
	the network prefix. Or you can use <cf>in <m/prefix/</cf> to get ROA
	entries covered by the network prefix. You could also use <cf/as/ option
851 852
	to show just entries for given AS.

853
	<tag><label id="cli-add-roa">add roa <m/prefix/ max <m/num/ as <m/num/ [table <m/t/]</tag>
854 855 856
	Add a new ROA entry to a ROA table. Such entry is called <it/dynamic/
	compared to <it/static/ entries specified in the config file. These
	dynamic entries survive reconfiguration.
857

858
	<tag><label id="cli-delete-roa">delete roa <m/prefix/ max <m/num/ as <m/num/ [table <m/t/]</tag>
859 860
	Delete the specified ROA entry from a ROA table. Only dynamic ROA
	entries (i.e., the ones added by <cf/add roa/ command) can be deleted.
861

862
	<tag><label id="cli-flush-roa">flush roa [table <m/t/]</tag>
863 864
	Remove all dynamic ROA entries from a ROA table.

865
	<tag><label id="cli-configure">configure [soft] ["<m/config file/"] [timeout [<m/num/]]</tag>
866 867 868 869 870 871 872 873 874 875 876 877 878 879
	Reload configuration from a given file. BIRD will smoothly switch itself
	to the new configuration, protocols are reconfigured if possible,
	restarted otherwise. Changes in filters usually lead to restart of
	affected protocols.

	If <cf/soft/ option is used, changes in filters does not cause BIRD to
	restart affected protocols, therefore already accepted routes (according
	to old filters) would be still propagated, but new routes would be
	processed according to the new filters.

	If <cf/timeout/ option is used, config timer is activated. The new
	configuration could be either confirmed using <cf/configure confirm/
	command, or it will be reverted to the old one when the config timer
	expires. This is useful for cases when reconfiguration breaks current
880
	routing and a router becomes inaccessible for an administrator. The
881 882
	config timeout expiration is equivalent to <cf/configure undo/
	command. The timeout duration could be specified, default is 300 s.
883

884
	<tag><label id="cli-configure-confirm">configure confirm</tag>
885 886 887
	Deactivate the config undo timer and therefore confirm the current
	configuration.

888
	<tag><label id="cli-configure-undo">configure undo</tag>
889 890 891 892 893 894
	Undo the last configuration change and smoothly switch back to the
	previous (stored) configuration. If the last configuration change was
	soft, the undo change is also soft. There is only one level of undo, but
	in some specific cases when several reconfiguration requests are given
	immediately in a row and the intermediate ones are skipped then the undo
	also skips them back.
895

896
	<tag><label id="cli-configure-check">configure check ["<m/config file/"]</tag>
897 898
	Read and parse given config file, but do not use it. useful for checking
	syntactic and some semantic validity of an config file.
899

900
	<tag><label id="cli-enable-disable-restart">enable|disable|restart <m/name/|"<m/pattern/"|all</tag>
901 902
	Enable, disable or restart a given protocol instance, instances matching
	the <cf><m/pattern/</cf> or <cf/all/ instances.
903

904
	<tag><label id="cli-reload">reload [in|out] <m/name/|"<m/pattern/"|all</tag>
905 906 907 908 909 910 911 912 913 914 915 916 917 918 919
	Reload a given protocol instance, that means re-import routes from the
	protocol instance and re-export preferred routes to the instance. If
	<cf/in/ or <cf/out/ options are used, the command is restricted to one
	direction (re-import or re-export).

	This command is useful if appropriate filters have changed but the
	protocol instance was not restarted (or reloaded), therefore it still
	propagates the old set of routes. For example when <cf/configure soft/
	command was used to change filters.

	Re-export always succeeds, but re-import is protocol-dependent and might
	fail (for example, if BGP neighbor does not support route-refresh
	extension). In that case, re-export is also skipped. Note that for the
	pipe protocol, both directions are always reloaded together (<cf/in/ or
	<cf/out/ options are ignored in that case).
920

921
	<tag><label id="cli-down">down</tag>
Pavel Machek's avatar
Pavel Machek committed
922
	Shut BIRD down.
923

924
	<tag><label id="cli-debug">debug <m/protocol/|<m/pattern/|all all|off|{ states|routes|filters|events|packets [, <m/.../] }</tag>
925
	Control protocol debugging.
926

927
	<tag><label id="cli-dump">dump resources|sockets|interfaces|neighbors|attributes|routes|protocols</tag>
928 929
	Dump contents of internal data structures to the debugging output.

930
	<tag><label id="cli-echo">echo all|off|{ <m/list of log classes/ } [ <m/buffer-size/ ]</tag>
931
	Control echoing of log messages to the command-line output.
932
	See <ref id="opt-log" name="log option"> for a list of log classes.
933

934
	<tag><label id="cli-eval">eval <m/expr/</tag>
935
	Evaluate given expression.
936
</descrip>
937

938

939
<chapt>Filters
940
<label id="filters">
941

942
<sect>Introduction
943
<label id="filters-intro">
944

945 946 947 948 949 950
<p>BIRD contains a simple programming language. (No, it can't yet read mail :-).
There are two objects in this language: filters and functions. Filters are
interpreted by BIRD core when a route is being passed between protocols and
routing tables. The filter language contains control structures such as if's and
switches, but it allows no loops. An example of a filter using many features can
be found in <file>filter/test.conf</file>.
951

952 953 954 955
<p>Filter gets the route, looks at its attributes and modifies some of them if
it wishes. At the end, it decides whether to pass the changed route through
(using <cf/accept/) or whether to <cf/reject/ it. A simple filter looks like
this:
956

957
<code>
958 959 960 961 962 963 964 965 966 967 968 969 970 971
filter not_too_far
int var;
{
	if defined( rip_metric ) then
		var = rip_metric;
	else {
		var = 1;
		rip_metric = 1;
	}
	if rip_metric &gt; 10 then
		reject "RIP metric is too big";
	else
		accept "ok";
}
972
</code>
973

974 975 976 977 978 979 980 981
<p>As you can see, a filter has a header, a list of local variables, and a body.
The header consists of the <cf/filter/ keyword followed by a (unique) name of
filter. The list of local variables consists of <cf><M>type name</M>;</cf>
pairs where each pair defines one local variable. The body consists of <cf>
{ <M>statements</M> }</cf>. Each <m/statement/ is terminated by a <cf/;/. You
can group several statements to a single compound statement by using braces
(<cf>{ <M>statements</M> }</cf>) which is useful if you want to make a bigger
block of code conditional.
982

983 984 985
<p>BIRD supports functions, so that you don't have to repeat the same blocks of
code over and over. Functions can have zero or more parameters and they can have
local variables. Recursion is not allowed. Function definitions look like this:
986 987 988 989 990 991 992 993 994 995 996 997 998 999

<code>
function name ()
int local_variable;
{
	local_variable = 5;
}

function with_parameters (int parameter)
{
	print parameter;
}
</code>

1000 1001 1002 1003 1004
<p>Unlike in C, variables are declared after the <cf/function/ line, but before
the first <cf/{/. You can't declare variables in nested blocks. Functions are
called like in C: <cf>name(); with_parameters(5);</cf>. Function may return
values using the <cf>return <m/[expr]/</cf> command. Returning a value exits
from current function (this is similar to C).
1005

1006 1007 1008 1009 1010
<p>Filters are declared in a way similar to functions except they can't have
explicit parameters. They get a route table entry as an implicit parameter, it
is also passed automatically to any functions called. The filter must terminate
with either <cf/accept/ or <cf/reject/ statement. If there's a runtime error in
filter, the route is rejected.
1011

1012 1013
<p>A nice trick to debug filters is to use <cf>show route filter <m/name/</cf>
from the command line client. An example session might look like:
Pavel Machek's avatar
Pavel Machek committed
1014 1015 1016 1017 1018 1019 1020 1021 1022

<code>
pavel@bug:~/bird$ ./birdc -s bird.ctl
BIRD 0.0.0 ready.
bird> show route
10.0.0.0/8         dev eth0 [direct1 23:21] (240)
195.113.30.2/32    dev tunl1 [direct1 23:21] (240)
127.0.0.0/8        dev lo [direct1 23:21] (240)
bird> show route ?
1023
show route [<prefix>] [table <t>] [filter <f>] [all] [primary]...
Martin Mareš's avatar
Martin Mareš committed
1024
bird> show route filter { if 127.0.0.5 &tilde; net then accept; }
Pavel Machek's avatar
Pavel Machek committed
1025 1026 1027 1028
127.0.0.0/8        dev lo [direct1 23:21] (240)
bird>
</code>

1029

1030
<sect>Data types
1031
<label id="data-types">
1032

1033 1034 1035
<p>Each variable and each value has certain type. Booleans, integers and enums
are incompatible with each other (that is to prevent you from shooting in the
foot).
1036 1037

<descrip>
1038
	<tag><label id="type-bool">bool</tag>
1039 1040 1041
	This is a boolean type, it can have only two values, <cf/true/ and
	<cf/false/. Boolean is the only type you can use in <cf/if/ statements.

1042
	<tag><label id="type-int">int</tag>
1043 1044 1045 1046
	This is a general integer type. It is an unsigned 32bit type; i.e., you
	can expect it to store values from 0 to 4294967295. Overflows are not
	checked. You can use <cf/0x1234/ syntax to write hexadecimal values.

1047
	<tag><label id="type-pair">pair</tag>
1048 1049 1050 1051 1052
	This is a pair of two short integers. Each component can have values
	from 0 to 65535. Literals of this type are written as <cf/(1234,5678)/.
	The same syntax can also be used to construct a pair from two arbitrary
	integer expressions (for example <cf/(1+2,a)/).

1053
	<tag><label id="type-quad">quad</tag>
1054 1055 1056 1057
	This is a dotted quad of numbers used to represent router IDs (and
	others). Each component can have a value from 0 to 255. Literals of
	this type are written like IPv4 addresses.

1058
	<tag><label id="type-string">string</tag>
1059 1060 1061 1062 1063
	This is a string of characters. There are no ways to modify strings in
	filters. You can pass them between functions, assign them to variables
	of type <cf/string/, print such variables, use standard string
	comparison operations (e.g. <cf/=, !=, &lt;, &gt;, &lt;=, &gt;=/), but
	you can't concatenate two strings. String literals are written as
1064 1065 1066
	<cf/"This is a string constant"/. Additionally matching (<cf/&tilde;,
	!&tilde;/) operators could be used to match a string value against
	a shell pattern (represented also as a string).
1067

1068
	<tag><label id="type-ip">ip</tag>
1069 1070 1071 1072 1073 1074 1075 1076
	This type can hold a single IP address. Depending on the compile-time
	configuration of BIRD you are using, it is either an IPv4 or IPv6
	address. IP addresses are written in the standard notation
	(<cf/10.20.30.40/ or <cf/fec0:3:4::1/). You can apply special operator
	<cf>.mask(<M>num</M>)</cf> on values of type ip. It masks out all but
	first <cf><M>num</M></cf> bits from the IP address. So
	<cf/1.2.3.4.mask(8) = 1.0.0.0/ is true.

1077
	<tag><label id="type-prefix">prefix</tag>
1078 1079 1080 1081 1082
	This type can hold a network prefix consisting of IP address and prefix
	length. Prefix literals are written as <cf><m/ipaddress//<m/pxlen/</cf>,
	or <cf><m>ipaddress</m>/<m>netmask</m></cf>. There are two special
	operators on prefixes: <cf/.ip/ which extracts the IP address from the
	pair, and <cf/.len/, which separates prefix length from the pair.
1083
	So <cf>1.2.0.0/16.len = 16</cf> is true.
1084

1085
	<tag><label id="type-ec">ec</tag>
1086 1087 1088 1089 1090 1091 1092 1093 1094
	This is a specialized type used to represent BGP extended community
	values. It is essentially a 64bit value, literals of this type are
	usually written as <cf>(<m/kind/, <m/key/, <m/value/)</cf>, where
	<cf/kind/ is a kind of extended community (e.g. <cf/rt/ / <cf/ro/ for a
	route target / route origin communities), the format and possible values
	of <cf/key/ and <cf/value/ are usually integers, but it depends on the
	used kind. Similarly to pairs, ECs can be constructed using expressions
	for <cf/key/ and <cf/value/ parts, (e.g. <cf/(ro, myas, 3*10)/, where
	<cf/myas/ is an integer variable).
1095

1096
	<tag><label id="type-lc">lc</tag>
1097 1098 1099 1100 1101 1102 1103 1104
	This is a specialized type used to represent BGP large community
	values. It is essentially a triplet of 32bit values, where the first
	value is reserved for the AS number of the issuer, while meaning of
	remaining parts is defined by the issuer. Literals of this type are
	written as <cf/(123, 456, 789)/, with any integer values. Similarly to
	pairs, LCs can be constructed using expressions for its parts, (e.g.
	<cf/(myas, 10+20, 3*10)/, where <cf/myas/ is an integer variable).

1105
	<tag><label id="type-set">int|pair|quad|ip|prefix|ec|lc|enum set</tag>
1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123
	Filters recognize four types of sets. Sets are similar to strings: you
	can pass them around but you can't modify them. Literals of type <cf>int
	set</cf> look like <cf> [ 1, 2, 5..7 ]</cf>. As you can see, both simple
	values and ranges are permitted in sets.

	For pair sets, expressions like <cf/(123,*)/ can be used to denote
	ranges (in that case <cf/(123,0)..(123,65535)/). You can also use
	<cf/(123,5..100)/ for range <cf/(123,5)..(123,100)/. You can also use
	<cf/*/ and <cf/a..b/ expressions in the first part of a pair, note that
	such expressions are translated to a set of intervals, which may be
	memory intensive. E.g. <cf/(*,4..20)/ is translated to <cf/(0,4..20),
	(1,4..20), (2,4..20), ... (65535, 4..20)/.

	EC sets use similar expressions like pair sets, e.g. <cf/(rt, 123,
	10..20)/ or <cf/(ro, 123, *)/. Expressions requiring the translation
	(like <cf/(rt, *, 3)/) are not allowed (as they usually have 4B range
	for ASNs).

1124 1125 1126 1127 1128 1129 1130 1131 1132
	Also LC sets use similar expressions like pair sets. You can use ranges
	and wildcards, but if one field uses that, more specific (later) fields
	must be wildcards. E.g., <cf/(10, 20..30, *)/ or <cf/(10, 20, 30..40)/
	is valid, while <cf/(10, *, 20..30)/ or <cf/(10, 20..30, 40)/ is not
	valid.

	You can also use expressions for int, pair, EC and LC set values.
	However, it must be possible to evaluate these expressions before daemon
	boots. So you can use only constants inside them. E.g.
1133

1134 1135
	<code>
	 define one=1;
1136
	 define myas=64500;
1137 1138
	 int set odds;
	 pair set ps;
1139
	 ec set es;
1140

1141
	 odds = [ one, 2+1, 6-one, 2*2*2-1, 9, 11 ];
1142
	 ps = [ (1,one+one), (3,4)..(4,8), (5,*), (6,3..6), (7..9,*) ];
1143
	 es = [ (rt, myas, 3*10), (rt, myas+one, 0..16*16*16-1), (ro, myas+2, *) ];
1144
	</code>
1145

1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176
	Sets of prefixes are special: their literals does not allow ranges, but
	allows prefix patterns that are written
	as <cf><M>ipaddress</M>/<M>pxlen</M>{<M>low</M>,<M>high</M>}</cf>.
	Prefix <cf><m>ip1</m>/<m>len1</m></cf> matches prefix
	pattern <cf><m>ip2</m>/<m>len2</m>{<m>l</m>,<m>h</m>}</cf> if the
	first <cf>min(len1, len2)</cf> bits of <cf/ip1/ and <cf/ip2/ are
	identical and <cf>len1 &lt;= ip1 &lt;= len2</cf>. A valid prefix pattern
	has to satisfy <cf>low &lt;= high</cf>, but <cf/pxlen/ is not
	constrained by <cf/low/ or <cf/high/. Obviously, a prefix matches a
	prefix set literal if it matches any prefix pattern in the prefix set
	literal.

	There are also two shorthands for prefix patterns: <cf><m/address//<m/len/+</cf>
	is a shorthand for <cf><m/address//<m/len/{<m/len/,<m/maxlen/}</cf>
	(where <cf><m/maxlen/</cf> is 32 for IPv4 and 128 for IPv6), that means
	network prefix <cf><m/address//<m/len/</cf> and all its	subnets.
	<cf><m/address//<m/len/-</cf> is a shorthand for
	<cf><m/address//<m/len/{0,<m/len/}</cf>, that means network prefix
	<cf><m/address//<m/len/</cf> and all its supernets (network prefixes
	that contain it).

	For example, <cf>[ 1.0.0.0/8, 2.0.0.0/8+, 3.0.0.0/8-, 4.0.0.0/8{16,24}
	]</cf> matches prefix <cf>1.0.0.0/8</cf>, all subprefixes of
	<cf>2.0.0.0/8</cf>, all superprefixes of <cf>3.0.0.0/8</cf> and prefixes
	<cf/4.X.X.X/ whose prefix length is 16 to 24. <cf>[ 0.0.0.0/0{20,24} ]</cf>
	matches all prefixes (regardless of IP address) whose prefix length is
	20 to 24, <cf>[ 1.2.3.4/32- ]</cf> matches any prefix that contains IP
	address <cf>1.2.3.4</cf>. <cf>1.2.0.0/16 &tilde; [ 1.0.0.0/8{15,17} ]</cf>
	is true, but <cf>1.0.0.0/16 &tilde; [ 1.0.0.0/8- ]</cf> is false.

	Cisco-style patterns like <cf>10.0.0.0/8 ge 16 le 24</cf> can be expressed
1177
	in BIRD as <cf>10.0.0.0/8{16,24}</cf>, <cf>192.168.0.0/16 le 24</cf> as
1178 1179
	<cf>192.168.0.0/16{16,24}</cf> and <cf>192.168.0.0/16 ge 24</cf> as
	<cf>192.168.0.0/16{24,32}</cf>.
1180

1181
	<tag><label id="type-enum">enum</tag>
1182 1183 1184
	Enumeration types are fixed sets of possibilities. You can't define your
	own variables of such type, but some route attributes are of enumeration
	type. Enumeration types are incompatible with each other.
1185

1186
	<tag><label id="type-bgppath">bgppath</tag>
1187 1188
	BGP path is a list of autonomous system numbers. You can't write
	literals of this type. There are several special operators on bgppaths:
1189

1190
	<cf><m/P/.first</cf> returns the first ASN (the neighbor ASN) in path <m/P/.
1191

1192
	<cf><m/P/.last</cf> returns the last ASN (the source ASN) in path <m/P/.
1193

1194 1195
	<cf><m/P/.last_nonaggregated</cf> returns the last ASN in the non-aggregated part of the path <m/P/.

1196 1197
	Both <cf/first/ and <cf/last/ return zero if there is no appropriate
	ASN, for example if the path contains an AS set element as the first (or
1198 1199
	the last) part. If the path ends with an AS set, <cf/last_nonaggregated/
	may be used to get last ASN before any AS set.
1200

1201
	<cf><m/P/.len</cf> returns the length of path <m/P/.
1202

1203 1204
	<cf><m/P/.empty</cf> resets path <m/P/ to empty path.

1205 1206
	<cf>prepend(<m/P/,<m/A/)</cf> prepends ASN <m/A/ to path <m/P/ and
	returns the result.
1207

1208 1209 1210 1211
	<cf>delete(<m/P/,<m/A/)</cf> deletes all instances of ASN <m/A/ from
	from path <m/P/ and returns the result. <m/A/ may also be an integer
	set, in that case the operator deletes all ASNs from path <m/P/ that are
	also members of set <m/A/.
1212

1213 1214 1215
	<cf>filter(<m/P/,<m/A/)</cf> deletes all ASNs from path <m/P/ that are
	not members of integer set <m/A/. I.e., <cf/filter/ do the same as
	<cf/delete/ with inverted set <m/A/.
1216

1217 1218 1219
	Statement <cf><m/P/ = prepend(<m/P/, <m/A/);</cf> can be shortened to
	<cf><m/P/.prepend(<m/A/);</cf> if <m/P/ is appropriate route attribute
	(for example <cf/bgp_path/). Similarly for <cf/delete/ and <cf/filter/.
1220

1221
	<tag><label id="type-bgpmask">bgpmask</tag>
1222 1223 1224 1225
	BGP masks are patterns used for BGP path matching (using <cf>path
	&tilde; [= 2 3 5 * =]</cf> syntax). The masks resemble wildcard patterns
	as used by UNIX shells. Autonomous system numbers match themselves,
	<cf/*/ matches any (even empty) sequence of arbitrary AS numbers and
1226
	<cf/?/ matches one arbitrary AS number. For example, if <cf>bgp_path</cf>
1227 1228 1229
 	is 4 3 2 1, then: <tt>bgp_path &tilde; [= * 4 3 * =]</tt> is true,
	but <tt>bgp_path &tilde; [= * 4 5 * =]</tt> is false. BGP mask
	expressions can also contain integer expressions enclosed in parenthesis
1230 1231 1232 1233
	and integer variables, for example <tt>[= * 4 (1+2) a =]</tt>. You can
        also use ranges, for example <tt>[= * 3..5 2 100..200 * =]</tt>.
        There is also old (deprecated) syntax that uses / .. / instead of [= .. =]
        and ? instead of *.
1234

1235
	<tag><label id="type-clist">clist</tag>
1236 1237 1238 1239 1240 1241 1242
	Clist is similar to a set, except that unlike other sets, it can be
	modified. The type is used for community list (a set of pairs) and for
	cluster list (a set of quads). There exist no literals of this type.
	There are three special operators on clists:

	<cf><m/C/.len</cf> returns the length of clist <m/C/.

1243 1244
	<cf><m/C/.empty</cf> resets clist <m/C/ to empty clist.

1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264
	<cf>add(<m/C/,<m/P/)</cf> adds pair (or quad) <m/P/ to clist <m/C/ and
	returns the result. If item <m/P/ is already in clist <m/C/, it does
	nothing. <m/P/ may also be a clist, in that case all its members are
	added; i.e., it works as clist union.

	<cf>delete(<m/C/,<m/P/)</cf> deletes pair (or quad) <m/P/ from clist
	<m/C/ and returns the result. If clist <m/C/ does not contain item
	<m/P/, it does nothing. <m/P/ may also be a pair (or quad) set, in that
	case the operator deletes all items from clist <m/C/ that are also
	members of set <m/P/. Moreover, <m/P/ may also be a clist, which works
	analogously; i.e., it works as clist difference.

	<cf>filter(<m/C/,<m/P/)</cf> deletes all items from clist <m/C/ that are
	not members of pair (or quad) set <m/P/. I.e., <cf/filter/ do the same
	as <cf/delete/ with inverted set <m/P/. <m/P/ may also be a clist, which
	works analogously; i.e., it works as clist intersection.

	Statement <cf><m/C/ = add(<m/C/, <m/P/);</cf> can be shortened to
	<cf><m/C/.add(<m/P/);</cf> if <m/C/ is appropriate route attribute (for
	example <cf/bgp_community/). Similarly for <cf/delete/ and <cf/filter/.
1265

1266
	<tag><label id="type-eclist">eclist</tag>
1267 1268
	Eclist is a data type used for BGP extended community lists. Eclists
	are very similar to clists, but they are sets of ECs instead of pairs.
1269 1270 1271
	The same operations (like <cf/add/, <cf/delete/ or <cf/&tilde;/ and
	<cf/!&tilde;/ membership operators) can be used to modify or test
	eclists, with ECs instead of pairs as arguments.
1272 1273 1274 1275 1276 1277 1278

	<tag/lclist/
	Lclist is a data type used for BGP large community lists. Like eclists,
	lclists are very similar to clists, but they are sets of LCs instead of
	pairs. The same operations (like <cf/add/, <cf/delete/ or <cf/&tilde;/
	and <cf/!&tilde;/ membership operators) can be used to modify or test
	lclists, with LCs instead of pairs as arguments.
1279 1280
</descrip>

1281

1282
<sect>Operators
1283
<label id="operators">
1284

1285 1286 1287
<p>The filter language supports common integer operators <cf>(+,-,*,/)</cf>,
parentheses <cf/(a*(b+c))/, comparison <cf/(a=b, a!=b, a&lt;b, a&gt;=b)/.
Logical operations include unary not (<cf/!/), and (<cf/&amp;&amp;/) and or
1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300
(<cf/&verbar;&verbar;/). Special operators include (<cf/&tilde;/,
<cf/!&tilde;/) for "is (not) element of a set" operation - it can be used on
element and set of elements of the same type (returning true if element is
contained in the given set), or on two strings (returning true if first string
matches a shell-like pattern stored in second string) or on IP and prefix
(returning true if IP is within the range defined by that prefix), or on prefix
and prefix (returning true if first prefix is more specific than second one) or
on bgppath and bgpmask (returning true if the path matches the mask) or on
number and bgppath (returning true if the number is in the path) or on bgppath
and int (number) set (returning true if any ASN from the path is in the set) or
on pair/quad and clist (returning true if the pair/quad is element of the
clist) or on clist and pair/quad set (returning true if there is an element of
the clist that is also a member of the pair/quad set).
1301 1302

<p>There is one operator related to ROA infrastructure - <cf/roa_check()/. It
1303 1304 1305
examines a ROA table and does <rfc id="6483"> route origin validation for a
given network prefix. The basic usage is <cf>roa_check(<m/table/)</cf>, which
checks current route (which should be from BGP to have AS_PATH argument) in the
1306 1307
specified ROA table and returns ROA_UNKNOWN if there is no relevant ROA,
ROA_VALID if there is a matching ROA, or ROA_INVALID if there are some relevant
1308
ROAs but none of them match. There is also an extended variant
1309 1310
<cf>roa_check(<m/table/, <m/prefix/, <m/asn/)</cf>, which allows to specify a
prefix and an ASN as arguments.
1311

1312

1313
<sect>Control structures
1314
<label id="control-structures">
1315

1316
<p>Filters support two control structures: conditions and case switches.
1317

1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331
<p>Syntax of a condition is: <cf>if <M>boolean expression</M> then <m/command1/;
else <m/command2/;</cf> and you can use <cf>{ <m/command_1/; <m/command_2/;
<M>...</M> }</cf> instead of either command. The <cf>else</cf> clause may be
omitted. If the <cf><m>boolean expression</m></cf> is true, <m/command1/ is
executed, otherwise <m/command2/ is executed.

<p>The <cf>case</cf> is similar to case from Pascal. Syntax is <cf>case
<m/expr/ { else: | <m/num_or_prefix [ .. num_or_prefix]/: <m/statement/ ; [
... ] }</cf>. The expression after <cf>case</cf> can be of any type which can be
on the left side of the &tilde; operator and anything that could be a member of
a set is allowed before <cf/:/. Multiple commands are allowed without <cf/{}/
grouping. If <cf><m/expr/</cf> matches one of the <cf/:/ clauses, statements
between it and next <cf/:/ statement are executed. If <cf><m/expr/</cf> matches
neither of the <cf/:/ clauses, the statements after <cf/else:/ are executed.
1332

1333
<p>Here is example that uses <cf/if/ and <cf/case/ structures:
Pavel Machek's avatar
Pavel Machek committed
1334 1335 1336 1337 1338 1339

<code>
case arg1 {
	2: print "two"; print "I can do more commands without {}";
	3 .. 5: print "three to five";
	else: print "something else";
1340
}
Pavel Machek's avatar
Pavel Machek committed
1341

1342 1343 1344
if 1234 = i then printn "."; else {
  print "not 1234";
  print "You need {} around multiple commands";
Pavel Machek's avatar
Pavel Machek committed
1345
}
Pavel Machek's avatar
Pavel Machek committed
1346 1347
</code>

1348

1349
<sect>Route attributes
1350
<label id="route-attributes">
1351

1352 1353 1354 1355 1356 1357
<p>A filter is implicitly passed a route, and it can access its attributes just
like it accesses variables. Attempts to access undefined attribute result in a
runtime error; you can check if an attribute is defined by using the
<cf>defined( <m>attribute</m> )</cf> operator. One notable exception to this
rule are attributes of clist type, where undefined value is regarded as empty
clist for most purposes.
1358

1359
<descrip>
1360
	<tag><label id="rta-net"><m/prefix/ net</tag>
1361 1362
	Network the route is talking about. Read-only. (See the chapter about
	routing tables.)
1363

1364
	<tag><label id="rta-scope"><m/enum/ scope</tag>
1365 1366 1367 1368 1369 1370
	The scope of the route. Possible values: <cf/SCOPE_HOST/ for routes
	local to this host, <cf/SCOPE_LINK/ for those specific for a physical
	link, <cf/SCOPE_SITE/ and <cf/SCOPE_ORGANIZATION/ for private routes and
	<cf/SCOPE_UNIVERSE/ for globally visible routes. This attribute is not
	interpreted by BIRD and can be used to mark routes in filters. The
	default value for new routes is <cf/SCOPE_UNIVERSE/.
1371

1372
	<tag><label id="rta-preference"><m/int/ preference</tag>
1373 1374
	Preference of the route. Valid values are 0-65535. (See the chapter
	about routing tables.)
Pavel Machek's avatar
Pavel Machek committed
1375

1376
	<tag><label id="rta-from"><m/ip/ from</tag>
1377
	The router which the route has originated from.
1378

1379
	<tag><label id="rta-gw"><m/ip/ gw</tag>
1380
	Next hop packets routed using this route should be forwarded to.
1381

1382
	<tag><label id="rta-proto"><m/string