]>
Commit | Line | Data |
---|---|---|
04a22949 | 1 | <!doctype birddoc system> |
d37f899b PM |
2 | |
3 | <!-- | |
3e52d112 | 4 | BIRD 2.0 documentation |
d37f899b | 5 | |
dad92c30 OZ |
6 | This documentation can have 4 forms: sgml (this is master copy), html, ASCII |
7 | text and dvi/postscript (generated from sgml using sgmltools). You should always | |
8 | edit master copy. | |
02357f96 | 9 | |
dad92c30 OZ |
10 | This is a slightly modified linuxdoc dtd. Anything in <descrip> tags is |
11 | considered definition of configuration primitives, <cf> is fragment of | |
12 | configuration within normal text, <m> is "meta" information within fragment of | |
13 | configuration - something in config which is not keyword. | |
d37f899b | 14 | |
dad92c30 | 15 | (set-fill-column 80) |
d37f899b PM |
16 | |
17 | Copyright 1999,2000 Pavel Machek <pavel@ucw.cz>, distribute under GPL version 2 or later. | |
18 | ||
19 | --> | |
20 | ||
371adba6 | 21 | <book> |
d37f899b | 22 | |
3e52d112 | 23 | <title>BIRD 2.0 User's Guide |
d37f899b | 24 | <author> |
aa185265 MM |
25 | Ondrej Filip <it/<feela@network.cz>/, |
26 | Pavel Machek <it/<pavel@ucw.cz>/, | |
5516a66d | 27 | Martin Mares <it/<mj@ucw.cz>/, |
82b74253 | 28 | Maria Matejka <it/<mq@jmq.cz>/, |
5516a66d | 29 | Ondrej Zajicek <it/<santiago@crfreenet.org>/ |
aa185265 | 30 | </author> |
d37f899b | 31 | |
d37f899b | 32 | <abstract> |
aa185265 | 33 | This document contains user documentation for the BIRD Internet Routing Daemon project. |
d37f899b PM |
34 | </abstract> |
35 | ||
36 | <!-- Table of contents --> | |
37 | <toc> | |
38 | ||
39 | <!-- Begin the document --> | |
40 | ||
dad92c30 | 41 | |
371adba6 | 42 | <chapt>Introduction |
b9864aa8 | 43 | <label id="intro"> |
d37f899b | 44 | |
371adba6 | 45 | <sect>What is BIRD |
b9864aa8 | 46 | <label id="what-is-bird"> |
d37f899b | 47 | |
b9864aa8 | 48 | <p>The name `BIRD' is actually an acronym standing for `BIRD Internet Routing |
dad92c30 OZ |
49 | Daemon'. Let's take a closer look at the meaning of the name: |
50 | ||
51 | <p><em/BIRD/: Well, we think we have already explained that. It's an acronym | |
52 | standing for `BIRD Internet Routing Daemon', you remember, don't you? :-) | |
53 | ||
54 | <p><em/Internet Routing/: It's a program (well, a daemon, as you are going to | |
55 | discover in a moment) which works as a dynamic router in an Internet type | |
56 | network (that is, in a network running either the IPv4 or the IPv6 protocol). | |
57 | Routers are devices which forward packets between interconnected networks in | |
58 | order to allow hosts not connected directly to the same local area network to | |
59 | communicate with each other. They also communicate with the other routers in the | |
60 | Internet to discover the topology of the network which allows them to find | |
61 | optimal (in terms of some metric) rules for forwarding of packets (which are | |
62 | called routing tables) and to adapt themselves to the changing conditions such | |
63 | as outages of network links, building of new connections and so on. Most of | |
64 | these routers are costly dedicated devices running obscure firmware which is | |
65 | hard to configure and not open to any changes (on the other hand, their special | |
66 | hardware design allows them to keep up with lots of high-speed network | |
67 | interfaces, better than general-purpose computer does). Fortunately, most | |
68 | operating systems of the UNIX family allow an ordinary computer to act as a | |
69 | router and forward packets belonging to the other hosts, but only according to a | |
70 | statically configured table. | |
71 | ||
72 | <p>A <em/Routing Daemon/ is in UNIX terminology a non-interactive program | |
73 | running on background which does the dynamic part of Internet routing, that is | |
74 | it communicates with the other routers, calculates routing tables and sends them | |
75 | to the OS kernel which does the actual packet forwarding. There already exist | |
76 | other such routing daemons: routed (RIP only), GateD (non-free), | |
7935b9d2 PT |
77 | <HTMLURL URL="http://www.zebra.org" name="Zebra"> and |
78 | <HTMLURL URL="http://sourceforge.net/projects/mrt" name="MRTD">, | |
dad92c30 OZ |
79 | but their capabilities are limited and they are relatively hard to configure |
80 | and maintain. | |
897cd7aa MM |
81 | |
82 | <p>BIRD is an Internet Routing Daemon designed to avoid all of these shortcomings, | |
dad92c30 OZ |
83 | to support all the routing technology used in the today's Internet or planned to |
84 | be used in near future and to have a clean extensible architecture allowing new | |
85 | routing protocols to be incorporated easily. Among other features, BIRD | |
86 | supports: | |
897cd7aa MM |
87 | |
88 | <itemize> | |
89 | <item>both IPv4 and IPv6 protocols | |
90 | <item>multiple routing tables | |
91 | <item>the Border Gateway Protocol (BGPv4) | |
3e52d112 | 92 | <item>the Routing Information Protocol (RIPv2, RIPng) |
0c75411b | 93 | <item>the Open Shortest Path First protocol (OSPFv2, OSPFv3) |
cf3e3845 | 94 | <item>the Babel Routing Protocol |
6bcef225 | 95 | <item>the Router Advertisements for IPv6 hosts |
dad92c30 OZ |
96 | <item>a virtual protocol for exchange of routes between different |
97 | routing tables on a single host | |
897cd7aa MM |
98 | <item>a command-line interface allowing on-line control and inspection |
99 | of status of the daemon | |
dad92c30 OZ |
100 | <item>soft reconfiguration (no need to use complex online commands to |
101 | change the configuration, just edit the configuration file and | |
102 | notify BIRD to re-read it and it will smoothly switch itself to | |
103 | the new configuration, not disturbing routing protocols unless | |
104 | they are affected by the configuration changes) | |
02357f96 | 105 | <item>a powerful language for route filtering |
897cd7aa MM |
106 | </itemize> |
107 | ||
dad92c30 OZ |
108 | <p>BIRD has been developed at the Faculty of Math and Physics, Charles |
109 | University, Prague, Czech Republic as a student project. It can be freely | |
110 | distributed under the terms of the GNU General Public License. | |
111 | ||
112 | <p>BIRD has been designed to work on all UNIX-like systems. It has been | |
113 | developed and tested under Linux 2.0 to 2.6, and then ported to FreeBSD, NetBSD | |
114 | and OpenBSD, porting to other systems (even non-UNIX ones) should be relatively | |
115 | easy due to its highly modular architecture. | |
897cd7aa | 116 | |
3e52d112 JMM |
117 | <p>BIRD 1.x supported either IPv4 or IPv6 protocol, but had to be compiled separately |
118 | for each one. BIRD~2 supports both of them with a possibility of further extension. | |
119 | BIRD~2 supports Linux at least 3.16, FreeBSD 10, NetBSD 7.0, and OpenBSD 5.8. | |
120 | Anyway, it will probably work well also on older systems. | |
d37f899b | 121 | |
371adba6 | 122 | <sect>Installing BIRD |
b9864aa8 | 123 | <label id="install"> |
440439e3 | 124 | |
dad92c30 OZ |
125 | <p>On a recent UNIX system with GNU development tools (GCC, binutils, m4, make) |
126 | and Perl, installing BIRD should be as easy as: | |
440439e3 PM |
127 | |
128 | <code> | |
dad92c30 OZ |
129 | ./configure |
130 | make | |
131 | make install | |
132 | vi /usr/local/etc/bird.conf | |
c184d9d0 | 133 | bird |
440439e3 PM |
134 | </code> |
135 | ||
02357f96 | 136 | <p>You can use <tt>./configure --help</tt> to get a list of configure |
3e52d112 | 137 | options. The most important ones are: <tt/--with-protocols=/ to produce a slightly smaller |
dad92c30 OZ |
138 | BIRD executable by configuring out routing protocols you don't use, and |
139 | <tt/--prefix=/ to install BIRD to a place different from <file>/usr/local</file>. | |
140 | ||
b093c328 | 141 | |
02357f96 | 142 | <sect>Running BIRD |
b9864aa8 | 143 | <label id="argv"> |
36032ded | 144 | |
c184d9d0 | 145 | <p>You can pass several command-line options to bird: |
d26524fa | 146 | |
c184d9d0 | 147 | <descrip> |
b9864aa8 | 148 | <tag><label id="argv-config">-c <m/config name/</tag> |
66701947 | 149 | use given configuration file instead of <it/prefix/<file>/etc/bird.conf</file>. |
c184d9d0 | 150 | |
b9864aa8 | 151 | <tag><label id="argv-debug">-d</tag> |
3fda08e4 | 152 | enable debug messages to stderr, and run bird in foreground. |
c184d9d0 | 153 | |
3fda08e4 OZ |
154 | <tag><label id="argv-debug-file">-D <m/filename of debug log/</tag> |
155 | enable debug messages to given file. | |
a4644ed6 | 156 | |
f5952c73 PT |
157 | <tag><label id="argv-foreground">-f</tag> |
158 | run bird in foreground. | |
e8b89a61 | 159 | |
b9864aa8 | 160 | <tag><label id="argv-group">-g <m/group/</tag> |
e8b89a61 | 161 | use that group ID, see the next section for details. |
1cd198cf | 162 | |
f5952c73 PT |
163 | <tag><label id="argv-help">-h, --help</tag> |
164 | display command-line options to bird. | |
6eda3f13 | 165 | |
b9864aa8 | 166 | <tag><label id="argv-local">-l</tag> |
f2ae2bad | 167 | look for a configuration file and a communication socket in the current |
43fc6bb0 | 168 | working directory instead of in default system locations. However, paths |
f2ae2bad OZ |
169 | specified by options <cf/-c/, <cf/-s/ have higher priority. |
170 | ||
f5952c73 PT |
171 | <tag><label id="argv-parse">-p</tag> |
172 | just parse the config file and exit. Return value is zero if the config | |
173 | file is valid, nonzero if there are some errors. | |
174 | ||
175 | <tag><label id="argv-pid">-P <m/name of PID file/</tag> | |
176 | create a PID file with given filename. | |
177 | ||
b9864aa8 | 178 | <tag><label id="argv-recovery">-R</tag> |
6eda3f13 | 179 | apply graceful restart recovery after start. |
22558357 | 180 | |
f5952c73 PT |
181 | <tag><label id="argv-socket">-s <m/name of communication socket/</tag> |
182 | use given filename for a socket for communications with the client, | |
183 | default is <it/prefix/<file>/var/run/bird.ctl</file>. | |
184 | ||
185 | <tag><label id="argv-user">-u <m/user/</tag> | |
186 | drop privileges and use that user ID, see the next section for details. | |
187 | ||
22558357 PT |
188 | <tag><label id="argv-version">--version</tag> |
189 | display bird version. | |
c184d9d0 | 190 | </descrip> |
d26524fa | 191 | |
02357f96 PM |
192 | <p>BIRD writes messages about its work to log files or syslog (according to config). |
193 | ||
dad92c30 | 194 | |
e8b89a61 | 195 | <sect>Privileges |
b9864aa8 | 196 | <label id="privileges"> |
e8b89a61 | 197 | |
dad92c30 OZ |
198 | <p>BIRD, as a routing daemon, uses several privileged operations (like setting |
199 | routing table and using raw sockets). Traditionally, BIRD is executed and runs | |
200 | with root privileges, which may be prone to security problems. The recommended | |
201 | way is to use a privilege restriction (options <cf/-u/, <cf/-g/). In that case | |
202 | BIRD is executed with root privileges, but it changes its user and group ID to | |
203 | an unprivileged ones, while using Linux capabilities to retain just required | |
204 | privileges (capabilities CAP_NET_*). Note that the control socket is created | |
205 | before the privileges are dropped, but the config file is read after that. The | |
206 | privilege restriction is not implemented in BSD port of BIRD. | |
207 | ||
fff7498d | 208 | <p>An unprivileged user (as an argument to <cf/-u/ options) may be the user |
dad92c30 OZ |
209 | <cf/nobody/, but it is suggested to use a new dedicated user account (like |
210 | <cf/bird/). The similar considerations apply for the group option, but there is | |
211 | one more condition -- the users in the same group can use <file/birdc/ to | |
212 | control BIRD. | |
213 | ||
214 | <p>Finally, there is a possibility to use external tools to run BIRD in an | |
215 | environment with restricted privileges. This may need some configuration, but it | |
216 | is generally easy -- BIRD needs just the standard library, privileges to read | |
217 | the config file and create the control socket and the CAP_NET_* capabilities. | |
e8b89a61 | 218 | |
6eda3f13 | 219 | |
3e52d112 JMM |
220 | <chapt>Architecture |
221 | <label id="architecture"> | |
222 | ||
223 | <sect>Routing tables | |
b9864aa8 | 224 | <label id="routing-tables"> |
a852c139 | 225 | |
3e52d112 JMM |
226 | <p>The heart of BIRD is a routing table. BIRD has several independent routing tables; |
227 | each of them contains routes of exactly one <m/nettype/ (see below). There are two | |
228 | default tables -- <cf/master4/ for IPv4 routes and <cf/master6/ for IPv6 routes. | |
229 | Other tables must be explicitly configured. | |
230 | ||
231 | <p> | |
cf3e3845 OZ |
232 | These routing tables are not kernel forwarding tables. No forwarding is done by |
233 | BIRD. If you want to forward packets using the routes in BIRD tables, you may | |
234 | use the Kernel protocol (see below) to synchronize them with kernel FIBs. | |
3e52d112 JMM |
235 | |
236 | <p> | |
cf3e3845 OZ |
237 | Every nettype defines a (kind of) primary key on routes. Every route source can |
238 | supply one route for every possible primary key; new route announcement replaces | |
239 | the old route from the same source, keeping other routes intact. BIRD always | |
240 | chooses the best route for each primary key among the known routes and keeps the | |
241 | others as suboptimal. When the best route is retracted, BIRD re-runs the best | |
242 | route selection algorithm to find the current best route. | |
3e52d112 JMM |
243 | |
244 | <p> | |
245 | The global best route selection algorithm is (roughly) as follows: | |
a852c139 PM |
246 | |
247 | <itemize> | |
3e52d112 JMM |
248 | <item>Preferences of the routes are compared. |
249 | <item>Source protocol instance preferences are compared. | |
3e52d112 | 250 | <item>If source protocols are the same (e.g. BGP vs. BGP), the protocol's route selection algorithm is invoked. |
cf3e3845 | 251 | <item>If source protocols are different (e.g. BGP vs. OSPF), result of the algorithm is undefined. |
a852c139 PM |
252 | </itemize> |
253 | ||
cf3e3845 OZ |
254 | <p><label id="dsc-table-sorted">Usually, a routing table just chooses a selected |
255 | route from a list of entries for one network. But if the <cf/sorted/ option is | |
dad92c30 OZ |
256 | activated, these lists of entries are kept completely sorted (according to |
257 | preference or some protocol-dependent metric). This is needed for some features | |
258 | of some protocols (e.g. <cf/secondary/ option of BGP protocol, which allows to | |
259 | accept not just a selected route, but the first route (in the sorted list) that | |
260 | is accepted by filters), but it is incompatible with some other features (e.g. | |
261 | <cf/deterministic med/ option of BGP protocol, which activates a way of choosing | |
262 | selected route that cannot be described using comparison and ordering). Minor | |
263 | advantage is that routes are shown sorted in <cf/show route/, minor disadvantage | |
264 | is that it is slightly more computationally expensive. | |
265 | ||
3e52d112 JMM |
266 | <sect>Routes and network types |
267 | <label id="routes"> | |
268 | ||
269 | <p>BIRD works with several types of routes. Some of them are typical IP routes, | |
270 | others are better described as forwarding rules. We call them all routes, | |
cf3e3845 | 271 | regardless of this difference. |
3e52d112 | 272 | |
cf3e3845 OZ |
273 | <p>Every route consists of several attributes (read more about them in the |
274 | <ref id="route-attributes" name="Route attributes"> section); the common for all | |
275 | routes are: | |
3e52d112 JMM |
276 | |
277 | <itemize> | |
278 | <item>IP address of router which told us about this route | |
279 | <item>Source protocol instance | |
280 | <item>Route preference | |
281 | <item>Optional attributes defined by protocols | |
282 | </itemize> | |
283 | ||
284 | <p>Other attributes depend on nettypes. Some of them are part of the primary key, these are marked (PK). | |
285 | ||
286 | <sect1>IPv4 and IPv6 routes | |
cf3e3845 | 287 | <label id="ip-routes"> |
3e52d112 JMM |
288 | |
289 | <p>The traditional routes. Configuration keywords are <cf/ipv4/ and <cf/ipv6/. | |
290 | ||
291 | <itemize> | |
292 | <item>(PK) Route destination (IP prefix together with its length) | |
293 | <item>Route next hops (see below) | |
294 | </itemize> | |
295 | ||
159d619c OZ |
296 | <sect1>IPv6 source-specific routes |
297 | <label id="ip-sadr-routes"> | |
298 | ||
299 | <p>The IPv6 routes containing both destination and source prefix. They are used | |
300 | for source-specific routing (SSR), also called source-address dependent routing | |
301 | (SADR), see <rfc id="8043">. Currently limited mostly to the Babel protocol. | |
302 | Configuration keyword is <cf/ipv6 sadr/. | |
303 | ||
304 | <itemize> | |
305 | <item>(PK) Route destination (IP prefix together with its length) | |
306 | <item>(PK) Route source (IP prefix together with its length) | |
307 | <item>Route next hops (see below) | |
308 | </itemize> | |
309 | ||
3e52d112 | 310 | <sect1>VPN IPv4 and IPv6 routes |
cf3e3845 | 311 | <label id="vpn-routes"> |
3e52d112 JMM |
312 | |
313 | <p>Routes for IPv4 and IPv6 with VPN Route Distinguisher (<rfc id="4364">). | |
314 | Configuration keywords are <cf/vpn4/ and <cf/vpn6/. | |
315 | ||
316 | <itemize> | |
317 | <item>(PK) Route destination (IP prefix together with its length) | |
318 | <item>(PK) Route distinguisher (according to <rfc id="4364">) | |
319 | <item>Route next hops | |
320 | </itemize> | |
321 | ||
322 | <sect1>Route Origin Authorization for IPv4 and IPv6 | |
cf3e3845 | 323 | <label id="roa-routes"> |
3e52d112 JMM |
324 | |
325 | <p>These entries can be used to validate route origination of BGP routes. | |
cf3e3845 | 326 | A ROA entry specifies prefixes which could be originated by an AS number. |
3e52d112 JMM |
327 | Their keywords are <cf/roa4/ and <cf/roa6/. |
328 | ||
329 | <itemize> | |
330 | <item>(PK) IP prefix together with its length | |
331 | <item>(PK) Matching prefix maximal length | |
332 | <item>(PK) AS number | |
333 | </itemize> | |
334 | ||
335 | <sect1>Flowspec for IPv4 and IPv6 | |
cf3e3845 | 336 | <label id="flow-routes"> |
3e52d112 JMM |
337 | |
338 | <p>Flowspec rules are a form of firewall and traffic flow control rules | |
339 | distributed mostly via BGP. These rules may help the operators stop various | |
340 | network attacks in the beginning before eating up the whole bandwidth. | |
341 | Configuration keywords are <cf/flow4/ and <cf/flow6/. | |
342 | ||
343 | <itemize> | |
344 | <item>(PK) IP prefix together with its length | |
345 | <item>(PK) Flow definition data | |
346 | <item>Flow action (encoded internally as BGP communities according to <rfc id="5575">) | |
347 | </itemize> | |
348 | ||
349 | <sect1>MPLS switching rules | |
350 | <label id="mpls-routes"> | |
351 | ||
352 | <p>This nettype is currently a stub before implementing more support of <rfc id="3031">. | |
353 | BIRD currently does not support any label distribution protocol nor any label assignment method. | |
354 | Only the Kernel, Pipe and Static protocols can use MPLS tables. | |
355 | Configuration keyword is <cf/mpls/. | |
356 | ||
357 | <itemize> | |
358 | <item>(PK) MPLS label | |
359 | <item>Route next hops | |
360 | </itemize> | |
361 | ||
362 | <sect1>Route next hops | |
363 | <label id="route-next-hop"> | |
364 | ||
365 | <p>This is not a nettype. The route next hop is a complex attribute common for many | |
366 | nettypes as you can see before. Every next hop has its assigned device | |
367 | (either assumed from its IP address or set explicitly). It may have also | |
368 | an IP address and an MPLS stack (one or both independently). | |
369 | Maximal MPLS stack depth is set (in compile time) to 8 labels. | |
370 | ||
371 | <p>Every route (when eligible to have a next hop) can have more than one next hop. | |
372 | In that case, every next hop has also its weight. | |
373 | ||
374 | <sect>Protocols and channels | |
375 | <label id="protocols-concept"> | |
376 | ||
cf3e3845 | 377 | <p>BIRD protocol is an abstract class of producers and consumers of the routes. |
3e52d112 JMM |
378 | Each protocol may run in multiple instances and bind on one side to route |
379 | tables via channels, on the other side to specified listen sockets (BGP), | |
380 | interfaces (Babel, OSPF, RIP), APIs (Kernel, Direct), or nothing (Static, Pipe). | |
381 | ||
cf3e3845 | 382 | <p>There are also two protocols that do not have any channels -- BFD and Device. |
3e52d112 JMM |
383 | Both of them are kind of service for other protocols. |
384 | ||
385 | <p>Each protocol is connected to a routing table through a channel. Some protocols | |
386 | support only one channel (OSPF, RIP), some protocols support more channels (BGP, Direct). | |
387 | Each channel has two filters which can accept, reject and modify the routes. | |
388 | An <it/export/ filter is applied to routes passed from the routing table to the protocol, | |
389 | an <it/import/ filter is applied to routes in the opposite direction. | |
48cf5e84 | 390 | |
6eda3f13 | 391 | <sect>Graceful restart |
b9864aa8 | 392 | <label id="graceful-restart"> |
6eda3f13 OZ |
393 | |
394 | <p>When BIRD is started after restart or crash, it repopulates routing tables in | |
395 | an uncoordinated manner, like after clean start. This may be impractical in some | |
396 | cases, because if the forwarding plane (i.e. kernel routing tables) remains | |
397 | intact, then its synchronization with BIRD would temporarily disrupt packet | |
398 | forwarding until protocols converge. Graceful restart is a mechanism that could | |
399 | help with this issue. Generally, it works by starting protocols and letting them | |
400 | repopulate routing tables while deferring route propagation until protocols | |
401 | acknowledge their convergence. Note that graceful restart behavior have to be | |
402 | configured for all relevant protocols and requires protocol-specific support | |
403 | (currently implemented for Kernel and BGP protocols), it is activated for | |
404 | particular boot by option <cf/-R/. | |
405 | ||
96e4d096 OZ |
406 | <p>Some protocols (e.g. BGP) could be restarted gracefully after both |
407 | intentional outage and crash, while others (e.g. OSPF) after intentional outage | |
408 | only. For planned graceful restart, BIRD must be shut down by | |
409 | <ref id="cli-graceful-restart" name="graceful restart"> command instead of | |
410 | regular <ref id="cli-down" name="down"> command. In this way routing neighbors | |
411 | are notified about planned graceful restart and routes are kept in kernel table | |
412 | after shutdown. | |
413 | ||
a852c139 | 414 | |
371adba6 | 415 | <chapt>Configuration |
b9864aa8 | 416 | <label id="config"> |
af0b25d2 | 417 | |
371adba6 | 418 | <sect>Introduction |
b9864aa8 | 419 | <label id="config-intro"> |
d37f899b | 420 | |
dad92c30 OZ |
421 | <p>BIRD is configured using a text configuration file. Upon startup, BIRD reads |
422 | <it/prefix/<file>/etc/bird.conf</file> (unless the <tt/-c/ command line option | |
423 | is given). Configuration may be changed at user's request: if you modify the | |
424 | config file and then signal BIRD with <tt/SIGHUP/, it will adjust to the new | |
425 | config. Then there's the client which allows you to talk with BIRD in an | |
426 | extensive way. | |
427 | ||
428 | <p>In the config, everything on a line after <cf/#/ or inside <cf>/* */</cf> is | |
429 | a comment, whitespace characters are treated as a single space. If there's a | |
430 | variable number of options, they are grouped using the <cf/{ }/ brackets. Each | |
431 | option is terminated by a <cf/;/. Configuration is case sensitive. There are two | |
72163bd5 | 432 | ways how to name symbols (like protocol names, filter names, constants etc.). |
eeb2c616 OZ |
433 | You can either use a simple string starting with a letter (or underscore) |
434 | followed by any combination of letters, numbers and underscores (e.g. <cf/R123/, | |
435 | <cf/my_filter/, <cf/bgp5/) or you can enclose the name into apostrophes (<cf/'/) | |
436 | and than you can use any combination of numbers, letters, underscores, hyphens, | |
437 | dots and colons (e.g. <cf/'1:strange-name'/, <cf/'-NAME-'/, <cf/'cool::name'/). | |
dad92c30 OZ |
438 | |
439 | <p>Here is an example of a simple config file. It enables synchronization of | |
72163bd5 OZ |
440 | routing tables with OS kernel, learns network interfaces and runs RIP on all |
441 | network interfaces found. | |
d37f899b | 442 | |
a0dd1c74 | 443 | <code> |
d37f899b | 444 | protocol kernel { |
72163bd5 OZ |
445 | ipv4 { |
446 | export all; # Default is export none | |
447 | }; | |
d150c637 | 448 | persist; # Don't remove routes on BIRD shutdown |
d37f899b PM |
449 | } |
450 | ||
451 | protocol device { | |
d37f899b PM |
452 | } |
453 | ||
454 | protocol rip { | |
72163bd5 OZ |
455 | ipv4 { |
456 | import all; | |
457 | export all; | |
458 | }; | |
f434d191 | 459 | interface "*"; |
d37f899b | 460 | } |
a0dd1c74 | 461 | </code> |
d37f899b | 462 | |
326e33f5 | 463 | |
371adba6 | 464 | <sect>Global options |
b9864aa8 | 465 | <label id="global-opts"> |
af0b25d2 | 466 | |
a0dd1c74 | 467 | <p><descrip> |
3e52d112 | 468 | <tag><label id="opt-include">include "<m/filename/";</tag> |
cf3e3845 OZ |
469 | This statement causes inclusion of a new file. The <m/filename/ could |
470 | also be a wildcard, in that case matching files are included in | |
471 | alphabetic order. The maximal depth is 8. Note that this statement can | |
472 | be used anywhere in the config file, even inside other options, but | |
473 | always on the beginning of line. In the following example, the first | |
474 | semicolon belongs to the <cf/include/, the second to <cf/ipv6 table/. | |
475 | If the <file/tablename.conf/ contains exactly one token (the name of the | |
476 | table), this construction is correct: | |
3e52d112 JMM |
477 | <code> |
478 | ipv6 table | |
479 | include "tablename.conf";; | |
480 | </code> | |
48ec367a | 481 | |
6b5ad206 OZ |
482 | <tag><label id="opt-log">log "<m/filename/" [<m/limit/ "<m/backup/"] | syslog [name <m/name/] | stderr all|{ <m/list of classes/ }</tag> |
483 | Set logging of messages having the given class (either <cf/all/ or <cf>{ | |
484 | error|trace [, <m/.../] }</cf> etc.) into selected destination - a file | |
485 | specified as a filename string (with optional log rotation information), | |
486 | syslog (with optional name argument), or the stderr output. | |
487 | ||
488 | Classes are: | |
1632f1fe | 489 | <cf/info/, <cf/warning/, <cf/error/ and <cf/fatal/ for messages about local problems, |
523f020b OZ |
490 | <cf/debug/ for debugging messages, |
491 | <cf/trace/ when you want to know what happens in the network, | |
492 | <cf/remote/ for messages about misbehavior of remote machines, | |
02357f96 | 493 | <cf/auth/ about authentication failures, |
dad92c30 | 494 | <cf/bug/ for internal BIRD bugs. |
6b5ad206 OZ |
495 | |
496 | Logging directly to file supports basic log rotation -- there is an | |
497 | optional log file limit and a backup filename, when log file reaches the | |
498 | limit, the current log file is renamed to the backup filename and a new | |
499 | log file is created. | |
500 | ||
dad92c30 | 501 | You may specify more than one <cf/log/ line to establish logging to |
3fda08e4 OZ |
502 | multiple destinations. Default: log everything to the system log, or |
503 | to the debug output if debugging is enabled by <cf/-d//<cf/-D/ | |
504 | command-line option. | |
02357f96 | 505 | |
9df52a98 | 506 | <tag><label id="opt-debug-protocols">debug protocols all|off|{ states|routes|filters|interfaces|events|packets [, <m/.../] }</tag> |
dad92c30 OZ |
507 | Set global defaults of protocol debugging options. See <cf/debug/ in the |
508 | following section. Default: off. | |
5a203dac | 509 | |
b9864aa8 | 510 | <tag><label id="opt-debug-commands">debug commands <m/number/</tag> |
dad92c30 OZ |
511 | Control logging of client connections (0 for no logging, 1 for logging |
512 | of connects and disconnects, 2 and higher for logging of all client | |
513 | commands). Default: 0. | |
249d238c | 514 | |
b9864aa8 | 515 | <tag><label id="opt-debug-latency">debug latency <m/switch/</tag> |
8bcb5fb1 OZ |
516 | Activate tracking of elapsed time for internal events. Recent events |
517 | could be examined using <cf/dump events/ command. Default: off. | |
518 | ||
b9864aa8 | 519 | <tag><label id="opt-debug-latency-limit">debug latency limit <m/time/</tag> |
8bcb5fb1 OZ |
520 | If <cf/debug latency/ is enabled, this option allows to specify a limit |
521 | for elapsed time. Events exceeding the limit are logged. Default: 1 s. | |
522 | ||
b9864aa8 | 523 | <tag><label id="opt-watchdog-warn">watchdog warning <m/time/</tag> |
8bcb5fb1 OZ |
524 | Set time limit for I/O loop cycle. If one iteration took more time to |
525 | complete, a warning is logged. Default: 5 s. | |
526 | ||
b9864aa8 | 527 | <tag><label id="opt-watchdog-timeout">watchdog timeout <m/time/</tag> |
8bcb5fb1 OZ |
528 | Set time limit for I/O loop cycle. If the limit is breached, BIRD is |
529 | killed by abort signal. The timeout has effective granularity of | |
530 | seconds, zero means disabled. Default: disabled (0). | |
531 | ||
b9864aa8 | 532 | <tag><label id="opt-mrtdump">mrtdump "<m/filename/"</tag> |
dad92c30 OZ |
533 | Set MRTdump file name. This option must be specified to allow MRTdump |
534 | feature. Default: no dump file. | |
cf31112f | 535 | |
9df52a98 | 536 | <tag><label id="opt-mrtdump-protocols">mrtdump protocols all|off|{ states|messages [, <m/.../] }</tag> |
dad92c30 OZ |
537 | Set global defaults of MRTdump options. See <cf/mrtdump/ in the |
538 | following section. Default: off. | |
cf31112f | 539 | |
b9864aa8 | 540 | <tag><label id="opt-filter">filter <m/name local variables/{ <m/commands/ }</tag> |
dad92c30 OZ |
541 | Define a filter. You can learn more about filters in the following |
542 | chapter. | |
326e33f5 | 543 | |
b9864aa8 | 544 | <tag><label id="opt-function">function <m/name/ (<m/parameters/) <m/local variables/ { <m/commands/ }</tag> |
dad92c30 | 545 | Define a function. You can learn more about functions in the following chapter. |
523f020b | 546 | |
cf3e3845 | 547 | <tag><label id="opt-protocol">protocol rip|ospf|bgp|<m/.../ [<m/name/ [from <m/name2/]] { <m>protocol options</m> }</tag> |
dad92c30 OZ |
548 | Define a protocol instance called <cf><m/name/</cf> (or with a name like |
549 | "rip5" generated automatically if you don't specify any | |
550 | <cf><m/name/</cf>). You can learn more about configuring protocols in | |
551 | their own chapters. When <cf>from <m/name2/</cf> expression is used, | |
552 | initial protocol options are taken from protocol or template | |
553 | <cf><m/name2/</cf> You can run more than one instance of most protocols | |
554 | (like RIP or BGP). By default, no instances are configured. | |
a7f23f58 | 555 | |
cf3e3845 | 556 | <tag><label id="opt-template">template rip|ospf|bgp|<m/.../ [<m/name/ [from <m/name2/]] { <m>protocol options</m> }</tag> |
dad92c30 OZ |
557 | Define a protocol template instance called <m/name/ (or with a name like |
558 | "bgp1" generated automatically if you don't specify any <m/name/). | |
559 | Protocol templates can be used to group common options when many | |
560 | similarly configured protocol instances are to be defined. Protocol | |
561 | instances (and other templates) can use templates by using <cf/from/ | |
562 | expression and the name of the template. At the moment templates (and | |
563 | <cf/from/ expression) are not implemented for OSPF protocol. | |
249d238c | 564 | |
b9864aa8 | 565 | <tag><label id="opt-define">define <m/constant/ = <m/expression/</tag> |
dad92c30 OZ |
566 | Define a constant. You can use it later in every place you could use a |
567 | value of the same type. Besides, there are some predefined numeric | |
568 | constants based on /etc/iproute2/rt_* files. A list of defined constants | |
569 | can be seen (together with other symbols) using 'show symbols' command. | |
249d238c | 570 | |
265419a3 | 571 | <tag><label id="opt-attribute">attribute <m/type/ <m/name/</tag> |
3a22a6e8 | 572 | Declare a custom route attribute. You can set and get it in filters like |
eeb2c616 | 573 | any other route attribute. This feature is intended for marking routes |
265419a3 MM |
574 | in import filters for export filtering purposes instead of locally |
575 | assigned BGP communities which have to be deleted in export filters. | |
576 | ||
b9864aa8 PT |
577 | <tag><label id="opt-router-id">router id <m/IPv4 address/</tag> |
578 | Set BIRD's router ID. It's a world-wide unique identification of your | |
3e52d112 JMM |
579 | router, usually one of router's IPv4 addresses. Default: the lowest |
580 | IPv4 address of a non-loopback interface. | |
79b4e12e | 581 | |
9df52a98 | 582 | <tag><label id="opt-router-id-from">router id from [-] [ "<m/mask/" ] [ <m/prefix/ ] [, <m/.../]</tag> |
3e52d112 JMM |
583 | Set BIRD's router ID based on an IPv4 address of an interface specified by |
584 | an interface pattern. | |
b9864aa8 | 585 | See <ref id="proto-iface" name="interface"> section for detailed |
d7c06285 | 586 | description of interface patterns with extended clauses. |
249d238c | 587 | |
b9864aa8 | 588 | <tag><label id="opt-graceful-restart">graceful restart wait <m/number/</tag> |
6eda3f13 OZ |
589 | During graceful restart recovery, BIRD waits for convergence of routing |
590 | protocols. This option allows to specify a timeout for the recovery to | |
591 | prevent waiting indefinitely if some protocols cannot converge. Default: | |
592 | 240 seconds. | |
593 | ||
b9864aa8 | 594 | <tag><label id="opt-timeformat">timeformat route|protocol|base|log "<m/format1/" [<m/limit/ "<m/format2/"]</tag> |
dad92c30 OZ |
595 | This option allows to specify a format of date/time used by BIRD. The |
596 | first argument specifies for which purpose such format is used. | |
597 | <cf/route/ is a format used in 'show route' command output, | |
598 | <cf/protocol/ is used in 'show protocols' command output, <cf/base/ is | |
599 | used for other commands and <cf/log/ is used in a log file. | |
600 | ||
601 | "<m/format1/" is a format string using <it/strftime(3)/ notation (see | |
f047271c OZ |
602 | <it/man strftime/ for details). It is extended to support sub-second |
603 | time part with variable precision (up to microseconds) using "%f" | |
604 | conversion code (e.g., "%T.%3f" is hh:mm:ss.sss time). <m/limit/ and | |
605 | "<m/format2/" allow to specify the second format string for times in | |
606 | past deeper than <m/limit/ seconds. | |
607 | ||
608 | There are several shorthands: <cf/iso long/ is a ISO 8601 date/time | |
609 | format (YYYY-MM-DD hh:mm:ss) that can be also specified using <cf/"%F | |
610 | %T"/. Similarly, <cf/iso long ms/ and <cf/iso long us/ are ISO 8601 | |
611 | date/time formats with millisecond or microsecond precision. | |
dad92c30 OZ |
612 | <cf/iso short/ is a variant of ISO 8601 that uses just the time format |
613 | (hh:mm:ss) for near times (up to 20 hours in the past) and the date | |
f047271c OZ |
614 | format (YYYY-MM-DD) for far times. This is a shorthand for <cf/"%T" |
615 | 72000 "%F"/. And there are also <cf/iso short ms/ and <cf/iso short us/ | |
616 | high-precision variants of that. | |
c37e7851 | 617 | |
f047271c OZ |
618 | By default, BIRD uses the <cf/iso short ms/ format for <cf/route/ and |
619 | <cf/protocol/ times, and the <cf/iso long ms/ format for <cf/base/ and | |
90eb5e7a OZ |
620 | <cf/log/ times. |
621 | ||
3e52d112 | 622 | <tag><label id="opt-table"><m/nettype/ table <m/name/ [sorted]</tag> |
cf3e3845 OZ |
623 | Create a new routing table. The default routing tables <cf/master4/ and |
624 | <cf/master6/ are created implicitly, other routing tables have to be | |
625 | added by this command. Option <cf/sorted/ can be used to enable sorting | |
626 | of routes, see <ref id="dsc-table-sorted" name="sorted table"> | |
627 | description for details. | |
af582c48 | 628 | |
b9864aa8 | 629 | <tag><label id="opt-eval">eval <m/expr/</tag> |
3e52d112 | 630 | Evaluates given filter expression. It is used by the developers for testing of filters. |
249d238c PM |
631 | </descrip> |
632 | ||
cf3e3845 | 633 | |
371adba6 | 634 | <sect>Protocol options |
b9864aa8 | 635 | <label id="protocol-opts"> |
bfd71178 | 636 | |
dad92c30 OZ |
637 | <p>For each protocol instance, you can configure a bunch of options. Some of |
638 | them (those described in this section) are generic, some are specific to the | |
639 | protocol (see sections talking about the protocols). | |
7581b81b | 640 | |
dad92c30 OZ |
641 | <p>Several options use a <m/switch/ argument. It can be either <cf/on/, |
642 | <cf/yes/ or a numeric expression with a non-zero value for the option to be | |
643 | enabled or <cf/off/, <cf/no/ or a numeric expression evaluating to zero to | |
644 | disable it. An empty <m/switch/ is equivalent to <cf/on/ ("silence means | |
645 | agreement"). | |
7581b81b | 646 | |
5a203dac | 647 | <descrip> |
b9864aa8 | 648 | <tag><label id="proto-disabled">disabled <m/switch/</tag> |
dad92c30 OZ |
649 | Disables the protocol. You can change the disable/enable status from the |
650 | command line interface without needing to touch the configuration. | |
651 | Disabled protocols are not activated. Default: protocol is enabled. | |
5a203dac | 652 | |
9df52a98 | 653 | <tag><label id="proto-debug">debug all|off|{ states|routes|filters|interfaces|events|packets [, <m/.../] }</tag> |
5a203dac PM |
654 | Set protocol debugging options. If asked, each protocol is capable of |
655 | writing trace messages about its work to the log (with category | |
656 | <cf/trace/). You can either request printing of <cf/all/ trace messages | |
657 | or only of the types selected: <cf/states/ for protocol state changes | |
dad92c30 OZ |
658 | (protocol going up, down, starting, stopping etc.), <cf/routes/ for |
659 | routes exchanged with the routing table, <cf/filters/ for details on | |
660 | route filtering, <cf/interfaces/ for interface change events sent to the | |
661 | protocol, <cf/events/ for events internal to the protocol and <cf/packets/ | |
662 | for packets sent and received by the protocol. Default: off. | |
5a203dac | 663 | |
9df52a98 | 664 | <tag><label id="proto-mrtdump">mrtdump all|off|{ states|messages [, <m/.../] }</tag> |
dad92c30 OZ |
665 | Set protocol MRTdump flags. MRTdump is a standard binary format for |
666 | logging information from routing protocols and daemons. These flags | |
667 | control what kind of information is logged from the protocol to the | |
668 | MRTdump file (which must be specified by global <cf/mrtdump/ option, see | |
669 | the previous section). Although these flags are similar to flags of | |
670 | <cf/debug/ option, their meaning is different and protocol-specific. For | |
671 | BGP protocol, <cf/states/ logs BGP state changes and <cf/messages/ logs | |
672 | received BGP messages. Other protocols does not support MRTdump yet. | |
cf31112f | 673 | |
b9864aa8 | 674 | <tag><label id="proto-router-id">router id <m/IPv4 address/</tag> |
dad92c30 OZ |
675 | This option can be used to override global router id for a given |
676 | protocol. Default: uses global router id. | |
4cdd0784 | 677 | |
b9864aa8 | 678 | <tag><label id="proto-description">description "<m/text/"</tag> |
dad92c30 | 679 | This is an optional description of the protocol. It is displayed as a |
a043f2d7 | 680 | part of the output of 'show protocols all' command. |
62aa96ca | 681 | |
8c703ecf | 682 | <tag><label id="proto-vrf">vrf "<m/text/"|default</tag> |
943478b0 OZ |
683 | Associate the protocol with specific VRF. The protocol will be |
684 | restricted to interfaces assigned to the VRF and will use sockets bound | |
8c703ecf OZ |
685 | to the VRF. A corresponding VRF interface must exist on OS level. For |
686 | kernel protocol, an appropriate table still must be explicitly selected | |
687 | by <cf/table/ option. | |
688 | ||
689 | By selecting <cf/default/, the protocol is associated with the default | |
690 | VRF; i.e., it will be restricted to interfaces not assigned to any | |
691 | regular VRF. That is different from not specifying <cf/vrf/ at all, in | |
692 | which case the protocol may use any interface regardless of its VRF | |
693 | status. | |
694 | ||
695 | Note that for proper VRF support it is necessary to use Linux kernel | |
696 | version at least 4.14, older versions have limited VRF implementation. | |
697 | Before Linux kernel 5.0, a socket bound to a port in default VRF collide | |
698 | with others in regular VRFs. In BGP, this can be avoided by using | |
699 | <ref id="bgp-strict-bind" name="strict bind"> option. | |
3e52d112 JMM |
700 | |
701 | <tag><label id="proto-channel"><m/channel name/ [{<m/channel config/}]</tag> | |
cf3e3845 OZ |
702 | Every channel must be explicitly stated. See the protocol-specific |
703 | configuration for the list of supported channel names. See the | |
704 | <ref id="channel-opts" name="channel configuration section"> for channel | |
705 | definition. | |
7581b81b PM |
706 | </descrip> |
707 | ||
a7c9f7c0 | 708 | <p>There are several options that give sense only with certain protocols: |
7581b81b PM |
709 | |
710 | <descrip> | |
9df52a98 | 711 | <tag><label id="proto-iface">interface [-] [ "<m/mask/" ] [ <m/prefix/ ] [, <m/.../] [ { <m/option/; [<m/.../] } ]</tag> |
f434d191 OZ |
712 | Specifies a set of interfaces on which the protocol is activated with |
713 | given interface-specific options. A set of interfaces specified by one | |
dad92c30 OZ |
714 | interface option is described using an interface pattern. The interface |
715 | pattern consists of a sequence of clauses (separated by commas), each | |
d7c06285 OZ |
716 | clause is a mask specified as a shell-like pattern. Interfaces are |
717 | matched by their name. | |
dad92c30 OZ |
718 | |
719 | An interface matches the pattern if it matches any of its clauses. If | |
720 | the clause begins with <cf/-/, matching interfaces are excluded. Patterns | |
d7c06285 | 721 | are processed left-to-right, thus <cf/interface "eth0", -"eth*", "*";/ |
dad92c30 OZ |
722 | means eth0 and all non-ethernets. |
723 | ||
d7c06285 OZ |
724 | Some protocols (namely OSPFv2 and Direct) support extended clauses that |
725 | may contain a mask, a prefix, or both of them. An interface matches such | |
726 | clause if its name matches the mask (if specified) and its address | |
727 | matches the prefix (if specified). Extended clauses are used when the | |
728 | protocol handles multiple addresses on an interface independently. | |
729 | ||
dad92c30 OZ |
730 | An interface option can be used more times with different interface-specific |
731 | options, in that case for given interface the first matching interface | |
732 | option is used. | |
523f020b | 733 | |
cf3e3845 | 734 | This option is allowed in Babel, BFD, Device, Direct, OSPF, RAdv and RIP |
3e52d112 | 735 | protocols. In OSPF protocol it is used in the <cf/area/ subsection. |
f434d191 OZ |
736 | |
737 | Default: none. | |
738 | ||
739 | Examples: | |
740 | ||
dad92c30 OZ |
741 | <cf>interface "*" { type broadcast; };</cf> - start the protocol on all |
742 | interfaces with <cf>type broadcast</cf> option. | |
f434d191 | 743 | |
dad92c30 OZ |
744 | <cf>interface "eth1", "eth4", "eth5" { type ptp; };</cf> - start the |
745 | protocol on enumerated interfaces with <cf>type ptp</cf> option. | |
523f020b | 746 | |
dad92c30 OZ |
747 | <cf>interface -192.168.1.0/24, 192.168.0.0/16;</cf> - start the protocol |
748 | on all interfaces that have address from 192.168.0.0/16, but not from | |
749 | 192.168.1.0/24. | |
f434d191 | 750 | |
f434d191 OZ |
751 | <cf>interface "eth*" 192.168.1.0/24;</cf> - start the protocol on all |
752 | ethernet interfaces that have address from 192.168.1.0/24. | |
753 | ||
b9864aa8 | 754 | <tag><label id="proto-tx-class">tx class|dscp <m/num/</tag> |
dad92c30 OZ |
755 | This option specifies the value of ToS/DS/Class field in IP headers of |
756 | the outgoing protocol packets. This may affect how the protocol packets | |
757 | are processed by the network relative to the other network traffic. With | |
758 | <cf/class/ keyword, the value (0-255) is used for the whole ToS/Class | |
759 | octet (but two bits reserved for ECN are ignored). With <cf/dscp/ | |
760 | keyword, the value (0-63) is used just for the DS field in the octet. | |
761 | Default value is 0xc0 (DSCP 0x30 - CS6). | |
ef4a50be | 762 | |
b9864aa8 | 763 | <tag><label id="proto-tx-priority">tx priority <m/num/</tag> |
dad92c30 OZ |
764 | This option specifies the local packet priority. This may affect how the |
765 | protocol packets are processed in the local TX queues. This option is | |
766 | Linux specific. Default value is 7 (highest priority, privileged traffic). | |
ef4a50be | 767 | |
64385aee PT |
768 | <tag><label id="proto-pass">password "<m/password/" [ { <m>password options</m> } ]</tag> |
769 | Specifies a password that can be used by the protocol as a shared secret | |
770 | key. Password option can be used more times to specify more passwords. | |
771 | If more passwords are specified, it is a protocol-dependent decision | |
772 | which one is really used. Specifying passwords does not mean that | |
773 | authentication is enabled, authentication can be enabled by separate, | |
774 | protocol-dependent <cf/authentication/ option. | |
523f020b | 775 | |
e03dc6a9 | 776 | This option is allowed in BFD, OSPF and RIP protocols. BGP has also |
f434d191 OZ |
777 | <cf/password/ option, but it is slightly different and described |
778 | separately. | |
f434d191 OZ |
779 | Default: none. |
780 | </descrip> | |
781 | ||
782 | <p>Password option can contain section with some (not necessary all) password sub-options: | |
783 | ||
784 | <descrip> | |
b9864aa8 | 785 | <tag><label id="proto-pass-id">id <M>num</M></tag> |
0a21c211 | 786 | ID of the password, (1-255). If it is not used, BIRD will choose ID based |
dad92c30 OZ |
787 | on an order of the password item in the interface. For example, second |
788 | password item in one interface will have default ID 2. ID is used by | |
789 | some routing protocols to identify which password was used to | |
790 | authenticate protocol packets. | |
f434d191 | 791 | |
b9864aa8 | 792 | <tag><label id="proto-pass-gen-from">generate from "<m/time/"</tag> |
dad92c30 OZ |
793 | The start time of the usage of the password for packet signing. |
794 | The format of <cf><m/time/</cf> is <tt>dd-mm-yyyy HH:MM:SS</tt>. | |
f434d191 | 795 | |
b9864aa8 | 796 | <tag><label id="proto-pass-gen-to">generate to "<m/time/"</tag> |
dad92c30 | 797 | The last time of the usage of the password for packet signing. |
f434d191 | 798 | |
b9864aa8 | 799 | <tag><label id="proto-pass-accept-from">accept from "<m/time/"</tag> |
dad92c30 | 800 | The start time of the usage of the password for packet verification. |
5a203dac | 801 | |
b9864aa8 | 802 | <tag><label id="proto-pass-accept-to">accept to "<m/time/"</tag> |
dad92c30 | 803 | The last time of the usage of the password for packet verification. |
64385aee PT |
804 | |
805 | <tag><label id="proto-pass-from">from "<m/time/"</tag> | |
806 | Shorthand for setting both <cf/generate from/ and <cf/accept from/. | |
807 | ||
808 | <tag><label id="proto-pass-to">to "<m/time/"</tag> | |
809 | Shorthand for setting both <cf/generate to/ and <cf/accept to/. | |
810 | ||
811 | <tag><label id="proto-pass-algorithm">algorithm ( keyed md5 | keyed sha1 | hmac sha1 | hmac sha256 | hmac sha384 | hmac sha512 )</tag> | |
812 | The message authentication algorithm for the password when cryptographic | |
813 | authentication is enabled. The default value depends on the protocol. | |
814 | For RIP and OSPFv2 it is Keyed-MD5 (for compatibility), for OSPFv3 | |
815 | protocol it is HMAC-SHA-256. | |
816 | ||
7581b81b | 817 | </descrip> |
d37f899b | 818 | |
cf3e3845 | 819 | |
3e52d112 JMM |
820 | <sect>Channel options |
821 | <label id="channel-opts"> | |
77234bbb | 822 | |
3e52d112 | 823 | <p>Every channel belongs to a protocol and is configured inside its block. The |
72163bd5 OZ |
824 | minimal channel config is empty, then it uses default values. The name of the |
825 | channel implies its nettype. Channel definitions can be inherited from protocol | |
826 | templates. Multiple definitions of the same channel are forbidden, but channels | |
827 | inherited from templates can be updated by new definitions. | |
77234bbb | 828 | |
3e52d112 JMM |
829 | <descrip> |
830 | <tag><label id="proto-table">table <m/name/</tag> | |
cf3e3845 OZ |
831 | Specify a table to which the channel is connected. Default: the first |
832 | table of given nettype. | |
833 | ||
834 | <tag><label id="proto-preference">preference <m/expr/</tag> | |
835 | Sets the preference of routes generated by the protocol and imported | |
836 | through this channel. Default: protocol dependent. | |
77234bbb | 837 | |
3e52d112 JMM |
838 | <tag><label id="proto-import">import all | none | filter <m/name/ | filter { <m/filter commands/ } | where <m/boolean filter expression/</tag> |
839 | Specify a filter to be used for filtering routes coming from the | |
840 | protocol to the routing table. <cf/all/ is for keeping all routes, | |
3831b619 OZ |
841 | <cf/none/ is for dropping all routes. Default: <cf/all/ (except for |
842 | EBGP). | |
77234bbb | 843 | |
3e52d112 JMM |
844 | <tag><label id="proto-export">export <m/filter/</tag> |
845 | This is similar to the <cf>import</cf> keyword, except that it works in | |
3831b619 OZ |
846 | the direction from the routing table to the protocol. Default: <cf/none/ |
847 | (except for EBGP). | |
77234bbb | 848 | |
3e52d112 JMM |
849 | <tag><label id="proto-import-keep-filtered">import keep filtered <m/switch/</tag> |
850 | Usually, if an import filter rejects a route, the route is forgotten. | |
851 | When this option is active, these routes are kept in the routing table, | |
852 | but they are hidden and not propagated to other protocols. But it is | |
853 | possible to show them using <cf/show route filtered/. Note that this | |
854 | option does not work for the pipe protocol. Default: off. | |
77234bbb | 855 | |
3e52d112 JMM |
856 | <tag><label id="proto-import-limit">import limit [<m/number/ | off ] [action warn | block | restart | disable]</tag> |
857 | Specify an import route limit (a maximum number of routes imported from | |
858 | the protocol) and optionally the action to be taken when the limit is | |
859 | hit. Warn action just prints warning log message. Block action discards | |
860 | new routes coming from the protocol. Restart and disable actions shut | |
861 | the protocol down like appropriate commands. Disable is the default | |
862 | action if an action is not explicitly specified. Note that limits are | |
863 | reset during protocol reconfigure, reload or restart. Default: <cf/off/. | |
77234bbb | 864 | |
3e52d112 JMM |
865 | <tag><label id="proto-receive-limit">receive limit [<m/number/ | off ] [action warn | block | restart | disable]</tag> |
866 | Specify an receive route limit (a maximum number of routes received from | |
867 | the protocol and remembered). It works almost identically to <cf>import | |
868 | limit</cf> option, the only difference is that if <cf/import keep | |
869 | filtered/ option is active, filtered routes are counted towards the | |
870 | limit and blocked routes are forgotten, as the main purpose of the | |
871 | receive limit is to protect routing tables from overflow. Import limit, | |
872 | on the contrary, counts accepted routes only and routes blocked by the | |
873 | limit are handled like filtered routes. Default: <cf/off/. | |
77234bbb | 874 | |
3e52d112 JMM |
875 | <tag><label id="proto-export-limit">export limit [ <m/number/ | off ] [action warn | block | restart | disable]</tag> |
876 | Specify an export route limit, works similarly to the <cf>import | |
877 | limit</cf> option, but for the routes exported to the protocol. This | |
878 | option is experimental, there are some problems in details of its | |
879 | behavior -- the number of exported routes can temporarily exceed the | |
880 | limit without triggering it during protocol reload, exported routes | |
881 | counter ignores route blocking and block action also blocks route | |
882 | updates of already accepted routes -- and these details will probably | |
883 | change in the future. Default: <cf/off/. | |
77234bbb OZ |
884 | </descrip> |
885 | ||
3e52d112 JMM |
886 | <p>This is a trivial example of RIP configured for IPv6 on all interfaces: |
887 | <code> | |
888 | protocol rip ng { | |
889 | ipv6; | |
890 | interface "*"; | |
77234bbb OZ |
891 | } |
892 | </code> | |
893 | ||
72163bd5 | 894 | <p>This is a non-trivial example. |
3e52d112 JMM |
895 | <code> |
896 | protocol rip ng { | |
897 | ipv6 { | |
898 | table mytable6; | |
899 | import filter { ... }; | |
900 | export filter { ... }; | |
901 | import limit 50; | |
902 | }; | |
903 | interface "*"; | |
77234bbb OZ |
904 | } |
905 | </code> | |
906 | ||
72163bd5 OZ |
907 | <p>And this is even more complicated example using templates. |
908 | <code> | |
909 | template bgp { | |
910 | local 198.51.100.14 as 65000; | |
911 | ||
912 | ipv4 { | |
913 | table mytable4; | |
914 | import filter { ... }; | |
3831b619 | 915 | export none; |
72163bd5 OZ |
916 | }; |
917 | ipv6 { | |
918 | table mytable6; | |
919 | import filter { ... }; | |
3831b619 | 920 | export none; |
72163bd5 OZ |
921 | }; |
922 | } | |
923 | ||
924 | protocol bgp from { | |
925 | neighbor 198.51.100.130 as 64496; | |
926 | ||
927 | # IPv4 channel is inherited as-is, while IPv6 | |
928 | # channel is adjusted by export filter option | |
929 | ipv6 { | |
930 | export filter { ... }; | |
931 | }; | |
932 | } | |
933 | </code> | |
934 | ||
935 | ||
5a203dac | 936 | <chapt>Remote control |
b9864aa8 | 937 | <label id="remote-control"> |
36032ded | 938 | |
dad92c30 OZ |
939 | <p>You can use the command-line client <file>birdc</file> to talk with a running |
940 | BIRD. Communication is done using a <file/bird.ctl/ UNIX domain socket (unless | |
941 | changed with the <tt/-s/ option given to both the server and the client). The | |
942 | commands can perform simple actions such as enabling/disabling of protocols, | |
943 | telling BIRD to show various information, telling it to show routing table | |
944 | filtered by filter, or asking BIRD to reconfigure. Press <tt/?/ at any time to | |
945 | get online help. Option <tt/-r/ can be used to enable a restricted mode of BIRD | |
946 | client, which allows just read-only commands (<cf/show .../). Option <tt/-v/ can | |
947 | be passed to the client, to make it dump numeric return codes along with the | |
948 | messages. You do not necessarily need to use <file/birdc/ to talk to BIRD, your | |
949 | own applications could do that, too -- the format of communication between BIRD | |
950 | and <file/birdc/ is stable (see the programmer's documentation). | |
951 | ||
952 | <p>There is also lightweight variant of BIRD client called <file/birdcl/, which | |
953 | does not support command line editing and history and has minimal dependencies. | |
954 | This is useful for running BIRD in resource constrained environments, where | |
955 | Readline library (required for regular BIRD client) is not available. | |
a5e9f3d2 OZ |
956 | |
957 | <p>Many commands have the <m/name/ of the protocol instance as an argument. | |
f434d191 OZ |
958 | This argument can be omitted if there exists only a single instance. |
959 | ||
5a203dac | 960 | <p>Here is a brief list of supported functions: |
64722c98 PM |
961 | |
962 | <descrip> | |
b9864aa8 | 963 | <tag><label id="cli-show-status">show status</tag> |
dad92c30 OZ |
964 | Show router status, that is BIRD version, uptime and time from last |
965 | reconfiguration. | |
5a203dac | 966 | |
b9864aa8 | 967 | <tag><label id="cli-show-interfaces">show interfaces [summary]</tag> |
43fc6bb0 OZ |
968 | Show the list of interfaces. For each interface, print its type, state, |
969 | MTU and addresses assigned. | |
970 | ||
b9864aa8 | 971 | <tag><label id="cli-show-protocols">show protocols [all]</tag> |
dad92c30 OZ |
972 | Show list of protocol instances along with tables they are connected to |
973 | and protocol status, possibly giving verbose information, if <cf/all/ is | |
974 | specified. | |
64722c98 | 975 | |
3e52d112 | 976 | <!-- TODO: Move these protocol-specific remote control commands to the protocol sections --> |
b9864aa8 | 977 | <tag><label id="cli-show-ospf-iface">show ospf interface [<m/name/] ["<m/interface/"]</tag> |
f434d191 OZ |
978 | Show detailed information about OSPF interfaces. |
979 | ||
b9864aa8 | 980 | <tag><label id="cli-show-ospf-neighbors">show ospf neighbors [<m/name/] ["<m/interface/"]</tag> |
f434d191 OZ |
981 | Show a list of OSPF neighbors and a state of adjacency to them. |
982 | ||
b9864aa8 | 983 | <tag><label id="cli-show-ospf-state">show ospf state [all] [<m/name/]</tag> |
dad92c30 OZ |
984 | Show detailed information about OSPF areas based on a content of the |
985 | link-state database. It shows network topology, stub networks, | |
986 | aggregated networks and routers from other areas and external routes. | |
987 | The command shows information about reachable network nodes, use option | |
988 | <cf/all/ to show information about all network nodes in the link-state | |
989 | database. | |
0ea8fb4a | 990 | |
b9864aa8 | 991 | <tag><label id="cli-show-ospf-topology">show ospf topology [all] [<m/name/]</tag> |
dad92c30 OZ |
992 | Show a topology of OSPF areas based on a content of the link-state |
993 | database. It is just a stripped-down version of 'show ospf state'. | |
64722c98 | 994 | |
b9864aa8 | 995 | <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> |
dad92c30 OZ |
996 | Show contents of an OSPF LSA database. Options could be used to filter |
997 | entries. | |
20ab192b | 998 | |
b9864aa8 | 999 | <tag><label id="cli-show-rip-interfaces">show rip interfaces [<m/name/] ["<m/interface/"]</tag> |
43fc6bb0 OZ |
1000 | Show detailed information about RIP interfaces. |
1001 | ||
b9864aa8 | 1002 | <tag><label id="cli-show-rip-neighbors">show rip neighbors [<m/name/] ["<m/interface/"]</tag> |
43fc6bb0 OZ |
1003 | Show a list of RIP neighbors and associated state. |
1004 | ||
b9864aa8 | 1005 | <tag><label id="cli-show-static">show static [<m/name/]</tag> |
f434d191 OZ |
1006 | Show detailed information about static routes. |
1007 | ||
b9864aa8 | 1008 | <tag><label id="cli-show-bfd-sessions">show bfd sessions [<m/name/]</tag> |
12201fd8 OZ |
1009 | Show information about BFD sessions. |
1010 | ||
b9864aa8 | 1011 | <tag><label id="cli-show-symbols">show symbols [table|filter|function|protocol|template|roa|<m/symbol/]</tag> |
dad92c30 OZ |
1012 | Show the list of symbols defined in the configuration (names of |
1013 | protocols, routing tables etc.). | |
5a203dac | 1014 | |
b2949999 | 1015 | <tag><label id="cli-show-route">show route [[for] <m/prefix/|<m/IP/] [table (<m/t/ | all)] [filter <m/f/|where <m/c/] [(export|preexport|noexport) <m/p/] [protocol <m/p/] [(stats|count)] [<m/options/]</tag> |
2faf519c | 1016 | Show contents of specified routing tables, that is routes, their metrics |
dad92c30 | 1017 | and (in case the <cf/all/ switch is given) all their attributes. |
5a203dac PM |
1018 | |
1019 | <p>You can specify a <m/prefix/ if you want to print routes for a | |
1020 | specific network. If you use <cf>for <m/prefix or IP/</cf>, you'll get | |
1021 | the entry which will be used for forwarding of packets to the given | |
1022 | destination. By default, all routes for each network are printed with | |
1023 | the selected one at the top, unless <cf/primary/ is given in which case | |
1024 | only the selected route is shown. | |
1025 | ||
b2949999 OZ |
1026 | <p>The <cf/show route/ command can process one or multiple routing |
1027 | tables. The set of selected tables is determined on three levels: First, | |
1028 | tables can be explicitly selected by <cf/table/ switch, which could be | |
1029 | used multiple times, all tables are specified by <cf/table all/. Second, | |
1030 | tables can be implicitly selected by channels or protocols that are | |
1031 | arguments of several other switches (e.g., <cf/export/, <cf/protocol/). | |
1032 | Last, the set of default tables is used: <cf/master4/, <cf/master6/ and | |
1033 | each first table of any other network type. | |
1034 | ||
5a203dac PM |
1035 | <p>You can also ask for printing only routes processed and accepted by |
1036 | a given filter (<cf>filter <m/name/</cf> or <cf>filter { <m/filter/ } | |
1037 | </cf> or matching a given condition (<cf>where <m/condition/</cf>). | |
7aa80901 OZ |
1038 | |
1039 | The <cf/export/, <cf/preexport/ and <cf/noexport/ switches ask for | |
b2949999 OZ |
1040 | printing of routes that are exported to the specified protocol or |
1041 | channel. With <cf/preexport/, the export filter of the channel is | |
1042 | skipped. With <cf/noexport/, routes rejected by the export filter are | |
1043 | printed instead. Note that routes not exported for other reasons | |
7aa80901 | 1044 | (e.g. secondary routes or routes imported from that protocol) are not |
b2949999 OZ |
1045 | printed even with <cf/noexport/. These switches also imply that |
1046 | associated routing tables are selected instead of default ones. | |
5a203dac | 1047 | |
4d176e14 | 1048 | <p>You can also select just routes added by a specific protocol. |
b2949999 OZ |
1049 | <cf>protocol <m/p/</cf>. This switch also implies that associated |
1050 | routing tables are selected instead of default ones. | |
4d176e14 | 1051 | |
dad92c30 OZ |
1052 | <p>If BIRD is configured to keep filtered routes (see <cf/import keep |
1053 | filtered/ option), you can show them instead of routes by using | |
1054 | <cf/filtered/ switch. | |
cf98be7b | 1055 | |
5a203dac PM |
1056 | <p>The <cf/stats/ switch requests showing of route statistics (the |
1057 | number of networks, number of routes before and after filtering). If | |
1058 | you use <cf/count/ instead, only the statistics will be printed. | |
af582c48 | 1059 | |
fc1b9333 OZ |
1060 | <tag><label id="cli-mrt-dump">mrt dump table <m/name/|"<m/pattern/" to "<m/filename/" [filter <m/f/|where <m/c/]</tag> |
1061 | Dump content of a routing table to a specified file in MRT table dump | |
1062 | format. See <ref id="mrt" name="MRT protocol"> for details. | |
1063 | ||
b9864aa8 | 1064 | <tag><label id="cli-configure">configure [soft] ["<m/config file/"] [timeout [<m/num/]]</tag> |
dad92c30 OZ |
1065 | Reload configuration from a given file. BIRD will smoothly switch itself |
1066 | to the new configuration, protocols are reconfigured if possible, | |
1067 | restarted otherwise. Changes in filters usually lead to restart of | |
1068 | affected protocols. | |
1069 | ||
1070 | If <cf/soft/ option is used, changes in filters does not cause BIRD to | |
1071 | restart affected protocols, therefore already accepted routes (according | |
1072 | to old filters) would be still propagated, but new routes would be | |
1073 | processed according to the new filters. | |
1074 | ||
1075 | If <cf/timeout/ option is used, config timer is activated. The new | |
1076 | configuration could be either confirmed using <cf/configure confirm/ | |
1077 | command, or it will be reverted to the old one when the config timer | |
1078 | expires. This is useful for cases when reconfiguration breaks current | |
fff7498d | 1079 | routing and a router becomes inaccessible for an administrator. The |
dad92c30 OZ |
1080 | config timeout expiration is equivalent to <cf/configure undo/ |
1081 | command. The timeout duration could be specified, default is 300 s. | |
a92cf57d | 1082 | |
b9864aa8 | 1083 | <tag><label id="cli-configure-confirm">configure confirm</tag> |
a92cf57d OZ |
1084 | Deactivate the config undo timer and therefore confirm the current |
1085 | configuration. | |
1086 | ||
b9864aa8 | 1087 | <tag><label id="cli-configure-undo">configure undo</tag> |
dad92c30 OZ |
1088 | Undo the last configuration change and smoothly switch back to the |
1089 | previous (stored) configuration. If the last configuration change was | |
1090 | soft, the undo change is also soft. There is only one level of undo, but | |
1091 | in some specific cases when several reconfiguration requests are given | |
1092 | immediately in a row and the intermediate ones are skipped then the undo | |
1093 | also skips them back. | |
a92cf57d | 1094 | |
b9864aa8 | 1095 | <tag><label id="cli-configure-check">configure check ["<m/config file/"]</tag> |
dad92c30 OZ |
1096 | Read and parse given config file, but do not use it. useful for checking |
1097 | syntactic and some semantic validity of an config file. | |
a92cf57d | 1098 | |
b9864aa8 | 1099 | <tag><label id="cli-enable-disable-restart">enable|disable|restart <m/name/|"<m/pattern/"|all</tag> |
dad92c30 OZ |
1100 | Enable, disable or restart a given protocol instance, instances matching |
1101 | the <cf><m/pattern/</cf> or <cf/all/ instances. | |
bf47fe4b | 1102 | |
b9864aa8 | 1103 | <tag><label id="cli-reload">reload [in|out] <m/name/|"<m/pattern/"|all</tag> |
dad92c30 OZ |
1104 | Reload a given protocol instance, that means re-import routes from the |
1105 | protocol instance and re-export preferred routes to the instance. If | |
1106 | <cf/in/ or <cf/out/ options are used, the command is restricted to one | |
1107 | direction (re-import or re-export). | |
1108 | ||
1109 | This command is useful if appropriate filters have changed but the | |
1110 | protocol instance was not restarted (or reloaded), therefore it still | |
1111 | propagates the old set of routes. For example when <cf/configure soft/ | |
1112 | command was used to change filters. | |
1113 | ||
1114 | Re-export always succeeds, but re-import is protocol-dependent and might | |
1115 | fail (for example, if BGP neighbor does not support route-refresh | |
1116 | extension). In that case, re-export is also skipped. Note that for the | |
1117 | pipe protocol, both directions are always reloaded together (<cf/in/ or | |
1118 | <cf/out/ options are ignored in that case). | |
8a7fb885 | 1119 | |
b9864aa8 | 1120 | <tag><label id="cli-down">down</tag> |
5a203dac | 1121 | Shut BIRD down. |
64722c98 | 1122 | |
96e4d096 OZ |
1123 | <tag><label id="cli-graceful-restart">graceful restart</tag> |
1124 | Shut BIRD down for graceful restart. See <ref id="graceful-restart" | |
1125 | name="graceful restart"> section for details. | |
1126 | ||
9df52a98 | 1127 | <tag><label id="cli-debug">debug <m/protocol/|<m/pattern/|all all|off|{ states|routes|filters|events|packets [, <m/.../] }</tag> |
64722c98 | 1128 | Control protocol debugging. |
508d9360 | 1129 | |
b9864aa8 | 1130 | <tag><label id="cli-dump">dump resources|sockets|interfaces|neighbors|attributes|routes|protocols</tag> |
508d9360 OZ |
1131 | Dump contents of internal data structures to the debugging output. |
1132 | ||
b9864aa8 | 1133 | <tag><label id="cli-echo">echo all|off|{ <m/list of log classes/ } [ <m/buffer-size/ ]</tag> |
508d9360 | 1134 | Control echoing of log messages to the command-line output. |
b9864aa8 | 1135 | See <ref id="opt-log" name="log option"> for a list of log classes. |
508d9360 | 1136 | |
b9864aa8 | 1137 | <tag><label id="cli-eval">eval <m/expr/</tag> |
508d9360 | 1138 | Evaluate given expression. |
64722c98 | 1139 | </descrip> |
36032ded | 1140 | |
72163bd5 | 1141 | |
371adba6 | 1142 | <chapt>Filters |
b9864aa8 | 1143 | <label id="filters"> |
d37f899b | 1144 | |
371adba6 | 1145 | <sect>Introduction |
b9864aa8 | 1146 | <label id="filters-intro"> |
d37f899b | 1147 | |
dad92c30 OZ |
1148 | <p>BIRD contains a simple programming language. (No, it can't yet read mail :-). |
1149 | There are two objects in this language: filters and functions. Filters are | |
1150 | interpreted by BIRD core when a route is being passed between protocols and | |
1151 | routing tables. The filter language contains control structures such as if's and | |
1152 | switches, but it allows no loops. An example of a filter using many features can | |
1153 | be found in <file>filter/test.conf</file>. | |
d37f899b | 1154 | |
dad92c30 OZ |
1155 | <p>Filter gets the route, looks at its attributes and modifies some of them if |
1156 | it wishes. At the end, it decides whether to pass the changed route through | |
1157 | (using <cf/accept/) or whether to <cf/reject/ it. A simple filter looks like | |
1158 | this: | |
d37f899b | 1159 | |
a0dd1c74 | 1160 | <code> |
d37f899b PM |
1161 | filter not_too_far |
1162 | int var; | |
1163 | { | |
1164 | if defined( rip_metric ) then | |
1165 | var = rip_metric; | |
1166 | else { | |
1167 | var = 1; | |
1168 | rip_metric = 1; | |
1169 | } | |
1170 | if rip_metric > 10 then | |
1171 | reject "RIP metric is too big"; | |
1172 | else | |
1173 | accept "ok"; | |
1174 | } | |
a0dd1c74 | 1175 | </code> |
d37f899b | 1176 | |
dad92c30 OZ |
1177 | <p>As you can see, a filter has a header, a list of local variables, and a body. |
1178 | The header consists of the <cf/filter/ keyword followed by a (unique) name of | |
1179 | filter. The list of local variables consists of <cf><M>type name</M>;</cf> | |
3a22a6e8 | 1180 | pairs where each pair declares one local variable. The body consists of <cf> |
dad92c30 OZ |
1181 | { <M>statements</M> }</cf>. Each <m/statement/ is terminated by a <cf/;/. You |
1182 | can group several statements to a single compound statement by using braces | |
1183 | (<cf>{ <M>statements</M> }</cf>) which is useful if you want to make a bigger | |
1184 | block of code conditional. | |
1632f1fe | 1185 | |
dad92c30 OZ |
1186 | <p>BIRD supports functions, so that you don't have to repeat the same blocks of |
1187 | code over and over. Functions can have zero or more parameters and they can have | |
1188 | local variables. Recursion is not allowed. Function definitions look like this: | |
0e5373fd PM |
1189 | |
1190 | <code> | |
1191 | function name () | |
1192 | int local_variable; | |
1193 | { | |
1194 | local_variable = 5; | |
1195 | } | |
1196 | ||
1197 | function with_parameters (int parameter) | |
1198 | { | |
1199 | print parameter; | |
1200 | } | |
1201 | </code> | |
1202 | ||
dad92c30 OZ |
1203 | <p>Unlike in C, variables are declared after the <cf/function/ line, but before |
1204 | the first <cf/{/. You can't declare variables in nested blocks. Functions are | |
1205 | called like in C: <cf>name(); with_parameters(5);</cf>. Function may return | |
1206 | values using the <cf>return <m/[expr]/</cf> command. Returning a value exits | |
1207 | from current function (this is similar to C). | |
0e5373fd | 1208 | |
3a22a6e8 | 1209 | <p>Filters are defined in a way similar to functions except they can't have |
dad92c30 OZ |
1210 | explicit parameters. They get a route table entry as an implicit parameter, it |
1211 | is also passed automatically to any functions called. The filter must terminate | |
1212 | with either <cf/accept/ or <cf/reject/ statement. If there's a runtime error in | |
1213 | filter, the route is rejected. | |
0e5373fd | 1214 | |
dad92c30 OZ |
1215 | <p>A nice trick to debug filters is to use <cf>show route filter <m/name/</cf> |
1216 | from the command line client. An example session might look like: | |
c184d9d0 PM |
1217 | |
1218 | <code> | |
1219 | pavel@bug:~/bird$ ./birdc -s bird.ctl | |
1220 | BIRD 0.0.0 ready. | |
c184d9d0 PM |
1221 | bird> show route |
1222 | 10.0.0.0/8 dev eth0 [direct1 23:21] (240) | |
1223 | 195.113.30.2/32 dev tunl1 [direct1 23:21] (240) | |
1224 | 127.0.0.0/8 dev lo [direct1 23:21] (240) | |
1225 | bird> show route ? | |
1632f1fe | 1226 | show route [<prefix>] [table <t>] [filter <f>] [all] [primary]... |
66701947 | 1227 | bird> show route filter { if 127.0.0.5 ˜ net then accept; } |
c184d9d0 PM |
1228 | 127.0.0.0/8 dev lo [direct1 23:21] (240) |
1229 | bird> | |
1230 | </code> | |
1231 | ||
dad92c30 | 1232 | |
371adba6 | 1233 | <sect>Data types |
b9864aa8 | 1234 | <label id="data-types"> |
d37f899b | 1235 | |
dad92c30 | 1236 | <p>Each variable and each value has certain type. Booleans, integers and enums |
eeb2c616 OZ |
1237 | are incompatible with each other (that is to prevent you from shooting oneself |
1238 | in the foot). | |
d37f899b PM |
1239 | |
1240 | <descrip> | |
b9864aa8 | 1241 | <tag><label id="type-bool">bool</tag> |
dad92c30 OZ |
1242 | This is a boolean type, it can have only two values, <cf/true/ and |
1243 | <cf/false/. Boolean is the only type you can use in <cf/if/ statements. | |
1244 | ||
b9864aa8 | 1245 | <tag><label id="type-int">int</tag> |
dad92c30 OZ |
1246 | This is a general integer type. It is an unsigned 32bit type; i.e., you |
1247 | can expect it to store values from 0 to 4294967295. Overflows are not | |
1248 | checked. You can use <cf/0x1234/ syntax to write hexadecimal values. | |
1249 | ||
b9864aa8 | 1250 | <tag><label id="type-pair">pair</tag> |
dad92c30 OZ |
1251 | This is a pair of two short integers. Each component can have values |
1252 | from 0 to 65535. Literals of this type are written as <cf/(1234,5678)/. | |
1253 | The same syntax can also be used to construct a pair from two arbitrary | |
1254 | integer expressions (for example <cf/(1+2,a)/). | |
1255 | ||
b9864aa8 | 1256 | <tag><label id="type-quad">quad</tag> |
dad92c30 OZ |
1257 | This is a dotted quad of numbers used to represent router IDs (and |
1258 | others). Each component can have a value from 0 to 255. Literals of | |
1259 | this type are written like IPv4 addresses. | |
1260 | ||
b9864aa8 | 1261 | <tag><label id="type-string">string</tag> |
dad92c30 OZ |
1262 | This is a string of characters. There are no ways to modify strings in |
1263 | filters. You can pass them between functions, assign them to variables | |
1264 | of type <cf/string/, print such variables, use standard string | |
1265 | comparison operations (e.g. <cf/=, !=, <, >, <=, >=/), but | |
1266 | you can't concatenate two strings. String literals are written as | |
768d5e10 PT |
1267 | <cf/"This is a string constant"/. Additionally matching (<cf/˜, |
1268 | !˜/) operators could be used to match a string value against | |
1269 | a shell pattern (represented also as a string). | |
dad92c30 | 1270 | |
b9864aa8 | 1271 | <tag><label id="type-ip">ip</tag> |
cf3e3845 OZ |
1272 | This type can hold a single IP address. The IPv4 addresses are stored as |
1273 | IPv4-Mapped IPv6 addresses so one data type for both of them is used. | |
1274 | Whether the address is IPv4 or not may be checked by <cf>.is_ip4</cf> | |
eeb2c616 | 1275 | which returns a <cf/bool/. IP addresses are written in the standard |
cf3e3845 OZ |
1276 | notation (<cf/10.20.30.40/ or <cf/fec0:3:4::1/). You can apply special |
1277 | operator <cf>.mask(<M>num</M>)</cf> on values of type ip. It masks out | |
1278 | all but first <cf><M>num</M></cf> bits from the IP address. So | |
dad92c30 OZ |
1279 | <cf/1.2.3.4.mask(8) = 1.0.0.0/ is true. |
1280 | ||
b9864aa8 | 1281 | <tag><label id="type-prefix">prefix</tag> |
8c9986d3 JMM |
1282 | This type can hold a network prefix consisting of IP address, prefix |
1283 | length and several other values. This is the key in route tables. | |
1284 | ||
a5d2a344 OZ |
1285 | Prefixes may be of several types, which can be determined by the special |
1286 | operator <cf/.type/. The type may be: | |
8c9986d3 | 1287 | |
a5d2a344 | 1288 | <cf/NET_IP4/ and <cf/NET_IP6/ prefixes hold an IP prefix. The literals |
0575c7db | 1289 | are written as <cf><m/ipaddress//<m/pxlen/</cf>. There are two special |
cf3e3845 OZ |
1290 | operators on these: <cf/.ip/ which extracts the IP address from the |
1291 | pair, and <cf/.len/, which separates prefix length from the pair. | |
90dc0f08 | 1292 | So <cf>1.2.0.0/16.len = 16</cf> is true. |
dad92c30 | 1293 | |
159d619c OZ |
1294 | <cf/NET_IP6_SADR/ nettype holds both destination and source IPv6 |
1295 | prefix. The literals are written as <cf><m/ipaddress//<m/pxlen/ from | |
1296 | <m/ipaddress//<m/pxlen/</cf>, where the first part is the destination | |
1297 | prefix and the second art is the source prefix. They support the same | |
1298 | operators as IP prefixes, but just for the destination part. | |
1299 | ||
a5d2a344 OZ |
1300 | <cf/NET_VPN4/ and <cf/NET_VPN6/ prefixes hold an IP prefix with VPN |
1301 | Route Distinguisher (<rfc id="4364">). They support the same special | |
1302 | operators as IP prefixes, and also <cf/.rd/ which extracts the Route | |
1303 | Distinguisher. Their literals are written | |
1304 | as <cf><m/vpnrd/ <m/ipprefix/</cf> | |
8c9986d3 | 1305 | |
a5d2a344 OZ |
1306 | <cf/NET_ROA4/ and <cf/NET_ROA6/ prefixes hold an IP prefix range |
1307 | together with an ASN. They support the same special operators as IP | |
1308 | prefixes, and also <cf/.maxlen/ which extracts maximal prefix length, | |
1309 | and <cf/.asn/ which extracts the ASN. | |
8c9986d3 | 1310 | |
a5d2a344 OZ |
1311 | <cf/NET_FLOW4/ and <cf/NET_FLOW6/ hold an IP prefix together with a |
1312 | flowspec rule. Filters currently don't support flowspec parsing. | |
8c9986d3 | 1313 | |
cf3e3845 OZ |
1314 | <cf/NET_MPLS/ holds a single MPLS label and its handling is currently |
1315 | not implemented. | |
3e52d112 JMM |
1316 | |
1317 | <tag><label id="type-vpnrd">vpnrd</tag> | |
1318 | This is a route distinguisher according to <rfc id="4364">. There are | |
1319 | three kinds of RD's: <cf><m/asn/:<m/32bit int/</cf>, <cf><m/asn4/:<m/16bit int/</cf> | |
1320 | and <cf><m/IPv4 address/:<m/32bit int/</cf> | |
1321 | ||
b9864aa8 | 1322 | <tag><label id="type-ec">ec</tag> |
dad92c30 OZ |
1323 | This is a specialized type used to represent BGP extended community |
1324 | values. It is essentially a 64bit value, literals of this type are | |
1325 | usually written as <cf>(<m/kind/, <m/key/, <m/value/)</cf>, where | |
1326 | <cf/kind/ is a kind of extended community (e.g. <cf/rt/ / <cf/ro/ for a | |
1327 | route target / route origin communities), the format and possible values | |
1328 | of <cf/key/ and <cf/value/ are usually integers, but it depends on the | |
1329 | used kind. Similarly to pairs, ECs can be constructed using expressions | |
1330 | for <cf/key/ and <cf/value/ parts, (e.g. <cf/(ro, myas, 3*10)/, where | |
1331 | <cf/myas/ is an integer variable). | |
dcde7ae5 | 1332 | |
b9864aa8 | 1333 | <tag><label id="type-lc">lc</tag> |
cec4a73c OZ |
1334 | This is a specialized type used to represent BGP large community |
1335 | values. It is essentially a triplet of 32bit values, where the first | |
1336 | value is reserved for the AS number of the issuer, while meaning of | |
1337 | remaining parts is defined by the issuer. Literals of this type are | |
1338 | written as <cf/(123, 456, 789)/, with any integer values. Similarly to | |
1339 | pairs, LCs can be constructed using expressions for its parts, (e.g. | |
1340 | <cf/(myas, 10+20, 3*10)/, where <cf/myas/ is an integer variable). | |
1341 | ||
b9864aa8 | 1342 | <tag><label id="type-set">int|pair|quad|ip|prefix|ec|lc|enum set</tag> |
dad92c30 OZ |
1343 | Filters recognize four types of sets. Sets are similar to strings: you |
1344 | can pass them around but you can't modify them. Literals of type <cf>int | |
1345 | set</cf> look like <cf> [ 1, 2, 5..7 ]</cf>. As you can see, both simple | |
1346 | values and ranges are permitted in sets. | |
1347 | ||
1348 | For pair sets, expressions like <cf/(123,*)/ can be used to denote | |
1349 | ranges (in that case <cf/(123,0)..(123,65535)/). You can also use | |
1350 | <cf/(123,5..100)/ for range <cf/(123,5)..(123,100)/. You can also use | |
1351 | <cf/*/ and <cf/a..b/ expressions in the first part of a pair, note that | |
1352 | such expressions are translated to a set of intervals, which may be | |
1353 | memory intensive. E.g. <cf/(*,4..20)/ is translated to <cf/(0,4..20), | |
1354 | (1,4..20), (2,4..20), ... (65535, 4..20)/. | |
1355 | ||
1356 | EC sets use similar expressions like pair sets, e.g. <cf/(rt, 123, | |
1357 | 10..20)/ or <cf/(ro, 123, *)/. Expressions requiring the translation | |
1358 | (like <cf/(rt, *, 3)/) are not allowed (as they usually have 4B range | |
1359 | for ASNs). | |
1360 | ||
cec4a73c OZ |
1361 | Also LC sets use similar expressions like pair sets. You can use ranges |
1362 | and wildcards, but if one field uses that, more specific (later) fields | |
1363 | must be wildcards. E.g., <cf/(10, 20..30, *)/ or <cf/(10, 20, 30..40)/ | |
1364 | is valid, while <cf/(10, *, 20..30)/ or <cf/(10, 20..30, 40)/ is not | |
1365 | valid. | |
1366 | ||
1367 | You can also use expressions for int, pair, EC and LC set values. | |
1368 | However, it must be possible to evaluate these expressions before daemon | |
1369 | boots. So you can use only constants inside them. E.g. | |
dad92c30 | 1370 | |
946dc15c OF |
1371 | <code> |
1372 | define one=1; | |
8815d846 | 1373 | define myas=64500; |
946dc15c OF |
1374 | int set odds; |
1375 | pair set ps; | |
8815d846 | 1376 | ec set es; |
946dc15c | 1377 | |
8815d846 | 1378 | odds = [ one, 2+1, 6-one, 2*2*2-1, 9, 11 ]; |
b54ad333 | 1379 | ps = [ (1,one+one), (3,4)..(4,8), (5,*), (6,3..6), (7..9,*) ]; |
8815d846 | 1380 | es = [ (rt, myas, 3*10), (rt, myas+one, 0..16*16*16-1), (ro, myas+2, *) ]; |
946dc15c | 1381 | </code> |
b1a597e0 | 1382 | |
dad92c30 OZ |
1383 | Sets of prefixes are special: their literals does not allow ranges, but |
1384 | allows prefix patterns that are written | |
1385 | as <cf><M>ipaddress</M>/<M>pxlen</M>{<M>low</M>,<M>high</M>}</cf>. | |
1386 | Prefix <cf><m>ip1</m>/<m>len1</m></cf> matches prefix | |
1387 | pattern <cf><m>ip2</m>/<m>len2</m>{<m>l</m>,<m>h</m>}</cf> if the | |
1388 | first <cf>min(len1, len2)</cf> bits of <cf/ip1/ and <cf/ip2/ are | |
1389 | identical and <cf>len1 <= ip1 <= len2</cf>. A valid prefix pattern | |
1390 | has to satisfy <cf>low <= high</cf>, but <cf/pxlen/ is not | |
1391 | constrained by <cf/low/ or <cf/high/. Obviously, a prefix matches a | |
1392 | prefix set literal if it matches any prefix pattern in the prefix set | |
1393 | literal. | |
1394 | ||
1395 | There are also two shorthands for prefix patterns: <cf><m/address//<m/len/+</cf> | |
1396 | is a shorthand for <cf><m/address//<m/len/{<m/len/,<m/maxlen/}</cf> | |
1397 | (where <cf><m/maxlen/</cf> is 32 for IPv4 and 128 for IPv6), that means | |
1398 | network prefix <cf><m/address//<m/len/</cf> and all its subnets. | |
1399 | <cf><m/address//<m/len/-</cf> is a shorthand for | |
1400 | <cf><m/address//<m/len/{0,<m/len/}</cf>, that means network prefix | |
1401 | <cf><m/address//<m/len/</cf> and all its supernets (network prefixes | |
1402 | that contain it). | |
1403 | ||
1404 | 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} | |
1405 | ]</cf> matches prefix <cf>1.0.0.0/8</cf>, all subprefixes of | |
1406 | <cf>2.0.0.0/8</cf>, all superprefixes of <cf>3.0.0.0/8</cf> and prefixes | |
1407 | <cf/4.X.X.X/ whose prefix length is 16 to 24. <cf>[ 0.0.0.0/0{20,24} ]</cf> | |
1408 | matches all prefixes (regardless of IP address) whose prefix length is | |
1409 | 20 to 24, <cf>[ 1.2.3.4/32- ]</cf> matches any prefix that contains IP | |
1410 | address <cf>1.2.3.4</cf>. <cf>1.2.0.0/16 ˜ [ 1.0.0.0/8{15,17} ]</cf> | |
1411 | is true, but <cf>1.0.0.0/16 ˜ [ 1.0.0.0/8- ]</cf> is false. | |
1412 | ||
1413 | Cisco-style patterns like <cf>10.0.0.0/8 ge 16 le 24</cf> can be expressed | |
523f020b | 1414 | in BIRD as <cf>10.0.0.0/8{16,24}</cf>, <cf>192.168.0.0/16 le 24</cf> as |
dad92c30 OZ |
1415 | <cf>192.168.0.0/16{16,24}</cf> and <cf>192.168.0.0/16 ge 24</cf> as |
1416 | <cf>192.168.0.0/16{24,32}</cf>. | |
d37f899b | 1417 | |
cf3e3845 | 1418 | It is possible to mix IPv4 and IPv6 prefixes/addresses in a prefix/ip set |
3e52d112 JMM |
1419 | but its behavior may change between versions without any warning; don't do |
1420 | it unless you are more than sure what you are doing. (Really, don't do it.) | |
1421 | ||
b9864aa8 | 1422 | <tag><label id="type-enum">enum</tag> |
dad92c30 OZ |
1423 | Enumeration types are fixed sets of possibilities. You can't define your |
1424 | own variables of such type, but some route attributes are of enumeration | |
1425 | type. Enumeration types are incompatible with each other. | |
0e5373fd | 1426 | |
b9864aa8 | 1427 | <tag><label id="type-bgppath">bgppath</tag> |
dad92c30 OZ |
1428 | BGP path is a list of autonomous system numbers. You can't write |
1429 | literals of this type. There are several special operators on bgppaths: | |
4cdd0784 | 1430 | |
dad92c30 | 1431 | <cf><m/P/.first</cf> returns the first ASN (the neighbor ASN) in path <m/P/. |
4cdd0784 | 1432 | |
dad92c30 | 1433 | <cf><m/P/.last</cf> returns the last ASN (the source ASN) in path <m/P/. |
4cdd0784 | 1434 | |
9c9cc35c OZ |
1435 | <cf><m/P/.last_nonaggregated</cf> returns the last ASN in the non-aggregated part of the path <m/P/. |
1436 | ||
dad92c30 OZ |
1437 | Both <cf/first/ and <cf/last/ return zero if there is no appropriate |
1438 | ASN, for example if the path contains an AS set element as the first (or | |
9c9cc35c OZ |
1439 | the last) part. If the path ends with an AS set, <cf/last_nonaggregated/ |
1440 | may be used to get last ASN before any AS set. | |
4cdd0784 | 1441 | |
dad92c30 | 1442 | <cf><m/P/.len</cf> returns the length of path <m/P/. |
4cdd0784 | 1443 | |
4842eeaa | 1444 | <cf><m/P/.empty</cf> makes the path <m/P/ empty. |
18ea2ea7 | 1445 | |
dad92c30 OZ |
1446 | <cf>prepend(<m/P/,<m/A/)</cf> prepends ASN <m/A/ to path <m/P/ and |
1447 | returns the result. | |
bff9ce51 | 1448 | |
dad92c30 OZ |
1449 | <cf>delete(<m/P/,<m/A/)</cf> deletes all instances of ASN <m/A/ from |
1450 | from path <m/P/ and returns the result. <m/A/ may also be an integer | |
1451 | set, in that case the operator deletes all ASNs from path <m/P/ that are | |
1452 | also members of set <m/A/. | |
bff9ce51 | 1453 | |
dad92c30 OZ |
1454 | <cf>filter(<m/P/,<m/A/)</cf> deletes all ASNs from path <m/P/ that are |
1455 | not members of integer set <m/A/. I.e., <cf/filter/ do the same as | |
1456 | <cf/delete/ with inverted set <m/A/. | |
bff9ce51 | 1457 | |
dad92c30 OZ |
1458 | Statement <cf><m/P/ = prepend(<m/P/, <m/A/);</cf> can be shortened to |
1459 | <cf><m/P/.prepend(<m/A/);</cf> if <m/P/ is appropriate route attribute | |
1460 | (for example <cf/bgp_path/). Similarly for <cf/delete/ and <cf/filter/. | |
4a5bb2bf | 1461 | |
b9864aa8 | 1462 | <tag><label id="type-bgpmask">bgpmask</tag> |
dad92c30 OZ |
1463 | BGP masks are patterns used for BGP path matching (using <cf>path |
1464 | ˜ [= 2 3 5 * =]</cf> syntax). The masks resemble wildcard patterns | |
1465 | as used by UNIX shells. Autonomous system numbers match themselves, | |
1466 | <cf/*/ matches any (even empty) sequence of arbitrary AS numbers and | |
523f020b | 1467 | <cf/?/ matches one arbitrary AS number. For example, if <cf>bgp_path</cf> |
dad92c30 OZ |
1468 | is 4 3 2 1, then: <tt>bgp_path ˜ [= * 4 3 * =]</tt> is true, |
1469 | but <tt>bgp_path ˜ [= * 4 5 * =]</tt> is false. BGP mask | |
1470 | expressions can also contain integer expressions enclosed in parenthesis | |
a0fe1944 | 1471 | and integer variables, for example <tt>[= * 4 (1+2) a =]</tt>. You can |
53247196 OZ |
1472 | also use ranges (e.g. <tt>[= * 3..5 2 100..200 * =]</tt>) and sets |
1473 | (e.g. <tt>[= 1 2 [3, 5, 7] * =]</tt>). | |
4cdd0784 | 1474 | |
b9864aa8 | 1475 | <tag><label id="type-clist">clist</tag> |
dad92c30 OZ |
1476 | Clist is similar to a set, except that unlike other sets, it can be |
1477 | modified. The type is used for community list (a set of pairs) and for | |
1478 | cluster list (a set of quads). There exist no literals of this type. | |
1479 | There are three special operators on clists: | |
1480 | ||
1481 | <cf><m/C/.len</cf> returns the length of clist <m/C/. | |
1482 | ||
3e52d112 | 1483 | <cf><m/C/.empty</cf> makes the list <m/C/ empty. |
18ea2ea7 | 1484 | |
dad92c30 OZ |
1485 | <cf>add(<m/C/,<m/P/)</cf> adds pair (or quad) <m/P/ to clist <m/C/ and |
1486 | returns the result. If item <m/P/ is already in clist <m/C/, it does | |
1487 | nothing. <m/P/ may also be a clist, in that case all its members are | |
1488 | added; i.e., it works as clist union. | |
1489 | ||
1490 | <cf>delete(<m/C/,<m/P/)</cf> deletes pair (or quad) <m/P/ from clist | |
1491 | <m/C/ and returns the result. If clist <m/C/ does not contain item | |
1492 | <m/P/, it does nothing. <m/P/ may also be a pair (or quad) set, in that | |
1493 | case the operator deletes all items from clist <m/C/ that are also | |
1494 | members of set <m/P/. Moreover, <m/P/ may also be a clist, which works | |
1495 | analogously; i.e., it works as clist difference. | |
1496 | ||
1497 | <cf>filter(<m/C/,<m/P/)</cf> deletes all items from clist <m/C/ that are | |
1498 | not members of pair (or quad) set <m/P/. I.e., <cf/filter/ do the same | |
1499 | as <cf/delete/ with inverted set <m/P/. <m/P/ may also be a clist, which | |
1500 | works analogously; i.e., it works as clist intersection. | |
1501 | ||
1502 | Statement <cf><m/C/ = add(<m/C/, <m/P/);</cf> can be shortened to | |
1503 | <cf><m/C/.add(<m/P/);</cf> if <m/C/ is appropriate route attribute (for | |
1504 | example <cf/bgp_community/). Similarly for <cf/delete/ and <cf/filter/. | |
8815d846 | 1505 | |
b9864aa8 | 1506 | <tag><label id="type-eclist">eclist</tag> |
dad92c30 OZ |
1507 | Eclist is a data type used for BGP extended community lists. Eclists |
1508 | are very similar to clists, but they are sets of ECs instead of pairs. | |
768d5e10 PT |
1509 | The same operations (like <cf/add/, <cf/delete/ or <cf/˜/ and |
1510 | <cf/!˜/ membership operators) can be used to modify or test | |
1511 | eclists, with ECs instead of pairs as arguments. | |
cec4a73c | 1512 | |
eeb2c616 | 1513 | <tag><label id="type-lclist">lclist</tag> |
cec4a73c OZ |
1514 | Lclist is a data type used for BGP large community lists. Like eclists, |
1515 | lclists are very similar to clists, but they are sets of LCs instead of | |
1516 | pairs. The same operations (like <cf/add/, <cf/delete/ or <cf/˜/ | |
1517 | and <cf/!˜/ membership operators) can be used to modify or test | |
1518 | lclists, with LCs instead of pairs as arguments. | |
d37f899b PM |
1519 | </descrip> |
1520 | ||
159d619c | 1521 | |
a7c9f7c0 | 1522 | <sect>Operators |
b9864aa8 | 1523 | <label id="operators"> |
d37f899b | 1524 | |
dad92c30 OZ |
1525 | <p>The filter language supports common integer operators <cf>(+,-,*,/)</cf>, |
1526 | parentheses <cf/(a*(b+c))/, comparison <cf/(a=b, a!=b, a<b, a>=b)/. | |
3e52d112 | 1527 | Logical operations include unary not (<cf/!/), and (<cf/&&/), and or |
768d5e10 PT |
1528 | (<cf/||/). Special operators include (<cf/˜/, |
1529 | <cf/!˜/) for "is (not) element of a set" operation - it can be used on | |
1530 | element and set of elements of the same type (returning true if element is | |
1531 | contained in the given set), or on two strings (returning true if first string | |
1532 | matches a shell-like pattern stored in second string) or on IP and prefix | |
1533 | (returning true if IP is within the range defined by that prefix), or on prefix | |
1534 | and prefix (returning true if first prefix is more specific than second one) or | |
1535 | on bgppath and bgpmask (returning true if the path matches the mask) or on | |
1536 | number and bgppath (returning true if the number is in the path) or on bgppath | |
1537 | and int (number) set (returning true if any ASN from the path is in the set) or | |
1538 | on pair/quad and clist (returning true if the pair/quad is element of the | |
1539 | clist) or on clist and pair/quad set (returning true if there is an element of | |
1540 | the clist that is also a member of the pair/quad set). | |
dad92c30 OZ |
1541 | |
1542 | <p>There is one operator related to ROA infrastructure - <cf/roa_check()/. It | |
7935b9d2 PT |
1543 | examines a ROA table and does <rfc id="6483"> route origin validation for a |
1544 | given network prefix. The basic usage is <cf>roa_check(<m/table/)</cf>, which | |
eeb2c616 OZ |
1545 | checks the current route (which should be from BGP to have AS_PATH argument) in |
1546 | the specified ROA table and returns ROA_UNKNOWN if there is no relevant ROA, | |
dad92c30 | 1547 | ROA_VALID if there is a matching ROA, or ROA_INVALID if there are some relevant |
af582c48 | 1548 | ROAs but none of them match. There is also an extended variant |
dad92c30 OZ |
1549 | <cf>roa_check(<m/table/, <m/prefix/, <m/asn/)</cf>, which allows to specify a |
1550 | prefix and an ASN as arguments. | |
af582c48 | 1551 | |
d37f899b | 1552 | |
371adba6 | 1553 | <sect>Control structures |
b9864aa8 | 1554 | <label id="control-structures"> |
d37f899b | 1555 | |
523f020b | 1556 | <p>Filters support two control structures: conditions and case switches. |
a7c9f7c0 | 1557 | |
3e52d112 JMM |
1558 | <p>Syntax of a condition is: <cf>if <M>boolean expression</M> then <m/commandT/; |
1559 | else <m/commandF/;</cf> and you can use <cf>{ <m/command1/; <m/command2/; | |
dad92c30 | 1560 | <M>...</M> }</cf> instead of either command. The <cf>else</cf> clause may be |
3e52d112 JMM |
1561 | omitted. If the <cf><m>boolean expression</m></cf> is true, <m/commandT/ is |
1562 | executed, otherwise <m/commandF/ is executed. | |
dad92c30 OZ |
1563 | |
1564 | <p>The <cf>case</cf> is similar to case from Pascal. Syntax is <cf>case | |
1565 | <m/expr/ { else: | <m/num_or_prefix [ .. num_or_prefix]/: <m/statement/ ; [ | |
1566 | ... ] }</cf>. The expression after <cf>case</cf> can be of any type which can be | |
1567 | on the left side of the ˜ operator and anything that could be a member of | |
1568 | a set is allowed before <cf/:/. Multiple commands are allowed without <cf/{}/ | |
1569 | grouping. If <cf><m/expr/</cf> matches one of the <cf/:/ clauses, statements | |
1570 | between it and next <cf/:/ statement are executed. If <cf><m/expr/</cf> matches | |
1571 | neither of the <cf/:/ clauses, the statements after <cf/else:/ are executed. | |
d37f899b | 1572 | |
a7c9f7c0 | 1573 | <p>Here is example that uses <cf/if/ and <cf/case/ structures: |
af0b25d2 PM |
1574 | |
1575 | <code> | |
1576 | case arg1 { | |
1577 | 2: print "two"; print "I can do more commands without {}"; | |
1578 | 3 .. 5: print "three to five"; | |
1579 | else: print "something else"; | |
a7c9f7c0 | 1580 | } |
af0b25d2 | 1581 | |
523f020b OZ |
1582 | if 1234 = i then printn "."; else { |
1583 | print "not 1234"; | |
1584 | print "You need {} around multiple commands"; | |
8798c811 | 1585 | } |
af0b25d2 PM |
1586 | </code> |
1587 | ||
dad92c30 | 1588 | |
371adba6 | 1589 | <sect>Route attributes |
b9864aa8 | 1590 | <label id="route-attributes"> |
0e5373fd | 1591 | |
dad92c30 | 1592 | <p>A filter is implicitly passed a route, and it can access its attributes just |
3a22a6e8 OZ |
1593 | like it accesses variables. There are common route attributes, protocol-specific |
1594 | route attributes and custom route attributes. Most common attributes are | |
1595 | mandatory (always defined), while remaining are optional. Attempts to access | |
1596 | undefined attribute result in a runtime error; you can check if an attribute is | |
1597 | defined by using the <cf>defined( <m>attribute</m> )</cf> operator. One notable | |
1598 | exception to this rule are attributes of bgppath and *clist types, where | |
1599 | undefined value is regarded as empty bgppath/*clist for most purposes. | |
1600 | ||
1601 | Attributes can be defined by just setting them in filters. Custom attributes | |
1602 | have to be first declared by <ref id="opt-attribute" name="attribute"> global | |
1603 | option. You can also undefine optional attribute back to non-existence by using | |
1604 | the <cf>unset( <m/attribute/ )</cf> operator. | |
1605 | ||
1606 | Common route attributes are: | |
a7c9f7c0 | 1607 | |
36032ded | 1608 | <descrip> |
b9864aa8 | 1609 | <tag><label id="rta-net"><m/prefix/ net</tag> |
cf3e3845 OZ |
1610 | The network prefix or anything else the route is talking about. The |
1611 | primary key of the routing table. Read-only. (See the <ref id="routes" | |
1612 | name="chapter about routes">.) | |
a7c9f7c0 | 1613 | |
b9864aa8 | 1614 | <tag><label id="rta-scope"><m/enum/ scope</tag> |
dad92c30 OZ |
1615 | The scope of the route. Possible values: <cf/SCOPE_HOST/ for routes |
1616 | local to this host, <cf/SCOPE_LINK/ for those specific for a physical | |
1617 | link, <cf/SCOPE_SITE/ and <cf/SCOPE_ORGANIZATION/ for private routes and | |
1618 | <cf/SCOPE_UNIVERSE/ for globally visible routes. This attribute is not | |
1619 | interpreted by BIRD and can be used to mark routes in filters. The | |
1620 | default value for new routes is <cf/SCOPE_UNIVERSE/. | |
0e5373fd | 1621 | |
b9864aa8 | 1622 | <tag><label id="rta-preference"><m/int/ preference</tag> |
dad92c30 OZ |
1623 | Preference of the route. Valid values are 0-65535. (See the chapter |
1624 | about routing tables.) | |
c184d9d0 | 1625 | |
b9864aa8 | 1626 | <tag><label id="rta-from"><m/ip/ from</tag> |
00192d5a | 1627 | The router which the route has originated from. |
523f020b | 1628 | |
b9864aa8 | 1629 | <tag><label id="rta-gw"><m/ip/ gw</tag> |
a7c9f7c0 | 1630 | Next hop packets routed using this route should be forwarded to. |
0e5373fd | 1631 | |
b9864aa8 | 1632 | <tag><label id="rta-proto"><m/string/ proto</tag> |
dad92c30 OZ |
1633 | The name of the protocol which the route has been imported from. |
1634 | Read-only. | |
e29fa06e | 1635 | |
b9864aa8 | 1636 | <tag><label id="rta-source"><m/enum/ source</tag> |
dad92c30 OZ |
1637 | what protocol has told me about this route. Possible values: |
1638 | <cf/RTS_DUMMY/, <cf/RTS_STATIC/, <cf/RTS_INHERIT/, <cf/RTS_DEVICE/, | |
1639 | <cf/RTS_STATIC_DEVICE/, <cf/RTS_REDIRECT/, <cf/RTS_RIP/, <cf/RTS_OSPF/, | |
1640 | <cf/RTS_OSPF_IA/, <cf/RTS_OSPF_EXT1/, <cf/RTS_OSPF_EXT2/, <cf/RTS_BGP/, | |
12640c14 | 1641 | <cf/RTS_PIPE/, <cf/RTS_BABEL/. |
c184d9d0 | 1642 | |
b9864aa8 | 1643 | <tag><label id="rta-dest"><m/enum/ dest</tag> |
182a7895 OZ |
1644 | Type of destination the packets should be sent to |
1645 | (<cf/RTD_ROUTER/ for forwarding to a neighboring router, | |
1646 | <cf/RTD_DEVICE/ for routing to a directly-connected network, | |
1647 | <cf/RTD_MULTIPATH/ for multipath destinations, | |
1648 | <cf/RTD_BLACKHOLE/ for packets to be silently discarded, | |
dad92c30 OZ |
1649 | <cf/RTD_UNREACHABLE/, <cf/RTD_PROHIBIT/ for packets that should be |
1650 | returned with ICMP host unreachable / ICMP administratively prohibited | |
1651 | messages). Can be changed, but only to <cf/RTD_BLACKHOLE/, | |
1652 | <cf/RTD_UNREACHABLE/ or <cf/RTD_PROHIBIT/. | |
b74f45f8 | 1653 | |
b9864aa8 | 1654 | <tag><label id="rta-ifname"><m/string/ ifname</tag> |
dad92c30 OZ |
1655 | Name of the outgoing interface. Sink routes (like blackhole, unreachable |
1656 | or prohibit) and multipath routes have no interface associated with | |
f2d8e680 OZ |
1657 | them, so <cf/ifname/ returns an empty string for such routes. Setting it |
1658 | would also change route to a direct one (remove gateway). | |
a5fc5958 | 1659 | |
b9864aa8 | 1660 | <tag><label id="rta-ifindex"><m/int/ ifindex</tag> |
dad92c30 OZ |
1661 | Index of the outgoing interface. System wide index of the interface. May |
1662 | be used for interface matching, however indexes might change on interface | |
1663 | creation/removal. Zero is returned for routes with undefined outgoing | |
a5fc5958 OZ |
1664 | interfaces. Read-only. |
1665 | ||
b9864aa8 | 1666 | <tag><label id="rta-igp-metric"><m/int/ igp_metric</tag> |
dad92c30 OZ |
1667 | The optional attribute that can be used to specify a distance to the |
1668 | network for routes that do not have a native protocol metric attribute | |
1669 | (like <cf/ospf_metric1/ for OSPF routes). It is used mainly by BGP to | |
feae132e | 1670 | compare internal distances to boundary routers (see below). |
ba1dda49 | 1671 | </descrip> |
0e5373fd | 1672 | |
3a22a6e8 OZ |
1673 | <p>Protocol-specific route attributes are described in the corresponding |
1674 | protocol sections. | |
dad92c30 | 1675 | |
0e5373fd | 1676 | |
1632f1fe | 1677 | <sect>Other statements |
b9864aa8 | 1678 | <label id="other-statements"> |
69477cad | 1679 | |
a7c9f7c0 | 1680 | <p>The following statements are available: |
69477cad PM |
1681 | |
1682 | <descrip> | |
b9864aa8 | 1683 | <tag><label id="assignment"><m/variable/ = <m/expr/</tag> |
3a22a6e8 | 1684 | Set variable (or route attribute) to a given value. |
326e33f5 | 1685 | |
b9864aa8 | 1686 | <tag><label id="filter-accept-reject">accept|reject [ <m/expr/ ]</tag> |
dad92c30 | 1687 | Accept or reject the route, possibly printing <cf><m>expr</m></cf>. |
326e33f5 | 1688 | |
b9864aa8 | 1689 | <tag><label id="return">return <m/expr/</tag> |
dad92c30 OZ |
1690 | Return <cf><m>expr</m></cf> from the current function, the function ends |
1691 | at this point. | |
326e33f5 | 1692 | |
b9864aa8 | 1693 | <tag><label id="print">print|printn <m/expr/ [<m/, expr.../]</tag> |
dad92c30 OZ |
1694 | Prints given expressions; useful mainly while debugging filters. The |
1695 | <cf/printn/ variant does not terminate the line. | |
69477cad | 1696 | |
b9864aa8 | 1697 | <tag><label id="quitbird">quitbird</tag> |
1632f1fe | 1698 | Terminates BIRD. Useful when debugging the filter interpreter. |
69477cad PM |
1699 | </descrip> |
1700 | ||
dad92c30 | 1701 | |
371adba6 | 1702 | <chapt>Protocols |
b9864aa8 | 1703 | <label id="protocols"> |
d37f899b | 1704 | |
937e75d8 | 1705 | <sect>Babel |
b9864aa8 | 1706 | <label id="babel"> |
937e75d8 OZ |
1707 | |
1708 | <sect1>Introduction | |
b9864aa8 | 1709 | <label id="babel-intro"> |
937e75d8 | 1710 | |
7935b9d2 PT |
1711 | <p>The Babel protocol |
1712 | (<rfc id="6126">) is a loop-avoiding distance-vector routing protocol that is | |
1713 | robust and efficient both in ordinary wired networks and in wireless mesh | |
1714 | networks. Babel is conceptually very simple in its operation and "just works" | |
1715 | in its default configuration, though some configuration is possible and in some | |
1716 | cases desirable. | |
937e75d8 | 1717 | |
300bd0eb OZ |
1718 | <p>The Babel protocol is dual stack; i.e., it can carry both IPv4 and IPv6 |
1719 | routes over the same IPv6 transport. For sending and receiving Babel packets, | |
1720 | only a link-local IPv6 address is needed. | |
937e75d8 | 1721 | |
159d619c OZ |
1722 | <p>BIRD implements an extension for IPv6 source-specific routing (SSR or SADR), |
1723 | but must be configured accordingly to use it. SADR-enabled Babel router can | |
1724 | interoperate with non-SADR Babel router, but the later would ignore routes | |
1725 | with specific (non-zero) source prefix. | |
937e75d8 OZ |
1726 | |
1727 | <sect1>Configuration | |
b9864aa8 | 1728 | <label id="babel-config"> |
937e75d8 | 1729 | |
159d619c OZ |
1730 | <p>The Babel protocol support both IPv4 and IPv6 channels; both can be |
1731 | configured simultaneously. It can also be configured with <ref | |
1732 | id="ip-sadr-routes" name="IPv6 SADR"> channel instead of regular IPv6 | |
1733 | channel, in such case SADR support is enabled. Babel supports no global | |
1734 | configuration options apart from those common to all other protocols, but | |
1735 | supports the following per-interface configuration options: | |
937e75d8 OZ |
1736 | |
1737 | <code> | |
1738 | protocol babel [<name>] { | |
3e52d112 | 1739 | ipv4 { <channel config> }; |
159d619c | 1740 | ipv6 [sadr] { <channel config> }; |
70fab178 | 1741 | randomize router id <switch>; |
937e75d8 OZ |
1742 | interface <interface pattern> { |
1743 | type <wired|wireless>; | |
1744 | rxcost <number>; | |
b47eaefe | 1745 | limit <number>; |
cf3e3845 OZ |
1746 | hello interval <time>; |
1747 | update interval <time>; | |
937e75d8 OZ |
1748 | port <number>; |
1749 | tx class|dscp <number>; | |
1750 | tx priority <number>; | |
1751 | rx buffer <number>; | |
1752 | tx length <number>; | |
1753 | check link <switch>; | |
300bd0eb OZ |
1754 | next hop ipv4 <address>; |
1755 | next hop ipv6 <address>; | |
937e75d8 OZ |
1756 | }; |
1757 | } | |
1758 | </code> | |
1759 | ||
1760 | <descrip> | |
159d619c OZ |
1761 | <tag><label id="babel-channel">ipv4 | ipv6 [sadr] <m/channel config/</tag> |
1762 | The supported channels are IPv4, IPv6, and IPv6 SADR. | |
3e52d112 | 1763 | |
70fab178 OZ |
1764 | <tag><label id="babel-random-router-id">randomize router id <m/switch/</tag> |
1765 | If enabled, Bird will randomize the top 32 bits of its router ID whenever | |
1766 | the protocol instance starts up. If a Babel node restarts, it loses its | |
1767 | sequence number, which can cause its routes to be rejected by peers until | |
1768 | the state is cleared out by other nodes in the network (which can take on | |
1769 | the order of minutes). Enabling this option causes Bird to pick a random | |
1770 | router ID every time it starts up, which avoids this problem at the cost | |
1771 | of not having stable router IDs in the network. Default: no. | |
1772 | ||
b9864aa8 | 1773 | <tag><label id="babel-type">type wired|wireless </tag> |
b47eaefe OZ |
1774 | This option specifies the interface type: Wired or wireless. On wired |
1775 | interfaces a neighbor is considered unreachable after a small number of | |
1776 | Hello packets are lost, as described by <cf/limit/ option. On wireless | |
1777 | interfaces the ETX link quality estimation technique is used to compute | |
1778 | the metrics of routes discovered over this interface. This technique will | |
1779 | gradually degrade the metric of routes when packets are lost rather than | |
1780 | the more binary up/down mechanism of wired type links. Default: | |
1781 | <cf/wired/. | |
937e75d8 | 1782 | |
b9864aa8 | 1783 | <tag><label id="babel-rxcost">rxcost <m/num/</tag> |
b47eaefe OZ |
1784 | This option specifies the nominal RX cost of the interface. The effective |
1785 | neighbor costs for route metrics will be computed from this value with a | |
1786 | mechanism determined by the interface <cf/type/. Note that in contrast to | |
1787 | other routing protocols like RIP or OSPF, the <cf/rxcost/ specifies the | |
1788 | cost of RX instead of TX, so it affects primarily neighbors' route | |
1789 | selection and not local route selection. Default: 96 for wired interfaces, | |
1790 | 256 for wireless. | |
1791 | ||
1792 | <tag><label id="babel-limit">limit <m/num/</tag> | |
1793 | BIRD keeps track of received Hello messages from each neighbor to | |
1794 | establish neighbor reachability. For wired type interfaces, this option | |
1795 | specifies how many of last 16 hellos have to be correctly received in | |
1796 | order to neighbor is assumed to be up. The option is ignored on wireless | |
1797 | type interfaces, where gradual cost degradation is used instead of sharp | |
1798 | limit. Default: 12. | |
937e75d8 | 1799 | |
cf3e3845 | 1800 | <tag><label id="babel-hello">hello interval <m/time/ s|ms</tag> |
b47eaefe | 1801 | Interval at which periodic Hello messages are sent on this interface, |
cf3e3845 | 1802 | with time units. Default: 4 seconds. |
937e75d8 | 1803 | |
cf3e3845 OZ |
1804 | <tag><label id="babel-update">update interval <m/time/ s|ms</tag> |
1805 | Interval at which periodic (full) updates are sent, with time | |
1806 | units. Default: 4 times the hello interval. | |
937e75d8 | 1807 | |
b9864aa8 | 1808 | <tag><label id="babel-port">port <m/number/</tag> |
937e75d8 OZ |
1809 | This option selects an UDP port to operate on. The default is to operate |
1810 | on port 6696 as specified in the Babel RFC. | |
1811 | ||
b9864aa8 | 1812 | <tag><label id="babel-tx-class">tx class|dscp|priority <m/number/</tag> |
937e75d8 | 1813 | These options specify the ToS/DiffServ/Traffic class/Priority of the |
b9864aa8 | 1814 | outgoing Babel packets. See <ref id="proto-tx-class" name="tx class"> common |
937e75d8 OZ |
1815 | option for detailed description. |
1816 | ||
b9864aa8 | 1817 | <tag><label id="babel-rx-buffer">rx buffer <m/number/</tag> |
937e75d8 OZ |
1818 | This option specifies the size of buffers used for packet processing. |
1819 | The buffer size should be bigger than maximal size of received packets. | |
1820 | The default value is the interface MTU, and the value will be clamped to a | |
1821 | minimum of 512 bytes + IP packet overhead. | |
1822 | ||
b9864aa8 | 1823 | <tag><label id="babel-tx-length">tx length <m/number/</tag> |
937e75d8 OZ |
1824 | This option specifies the maximum length of generated Babel packets. To |
1825 | avoid IP fragmentation, it should not exceed the interface MTU value. | |
1826 | The default value is the interface MTU value, and the value will be | |
1827 | clamped to a minimum of 512 bytes + IP packet overhead. | |
1828 | ||
b9864aa8 | 1829 | <tag><label id="babel-check-link">check link <m/switch/</tag> |
937e75d8 OZ |
1830 | If set, the hardware link state (as reported by OS) is taken into |
1831 | consideration. When the link disappears (e.g. an ethernet cable is | |
1832 | unplugged), neighbors are immediately considered unreachable and all | |
1833 | routes received from them are withdrawn. It is possible that some | |
1834 | hardware drivers or platforms do not implement this feature. Default: | |
1835 | yes. | |
300bd0eb OZ |
1836 | |
1837 | <tag><label id="babel-next-hop-ipv4">next hop ipv4 <m/address/</tag> | |
1838 | Set the next hop address advertised for IPv4 routes advertised on this | |
cf3e3845 | 1839 | interface. Default: the preferred IPv4 address of the interface. |
300bd0eb OZ |
1840 | |
1841 | <tag><label id="babel-next-hop-ipv6">next hop ipv6 <m/address/</tag> | |
1842 | Set the next hop address advertised for IPv6 routes advertised on this | |
1843 | interface. If not set, the same link-local address that is used as the | |
1844 | source for Babel packets will be used. In normal operation, it should not | |
1845 | be necessary to set this option. | |
937e75d8 OZ |
1846 | </descrip> |
1847 | ||
12640c14 | 1848 | <sect1>Attributes |
b9864aa8 | 1849 | <label id="babel-attr"> |
12640c14 OZ |
1850 | |
1851 | <p>Babel defines just one attribute: the internal babel metric of the route. It | |
1852 | is exposed as the <cf/babel_metric/ attribute and has range from 1 to infinity | |
1853 | (65535). | |
1854 | ||
1855 | <sect1>Example | |
b9864aa8 | 1856 | <label id="babel-exam"> |
12640c14 OZ |
1857 | |
1858 | <p><code> | |
1859 | protocol babel { | |
1860 | interface "eth*" { | |
1861 | type wired; | |
1862 | }; | |
1863 | interface "wlan0", "wlan1" { | |
1864 | type wireless; | |
1865 | hello interval 1; | |
1866 | rxcost 512; | |
1867 | }; | |
1868 | interface "tap0"; | |
1869 | ||
1870 | # This matches the default of babeld: redistribute all addresses | |
1871 | # configured on local interfaces, plus re-distribute all routes received | |
1872 | # from other babel peers. | |
1873 | ||
300bd0eb OZ |
1874 | ipv4 { |
1875 | export where (source = RTS_DEVICE) || (source = RTS_BABEL); | |
1876 | }; | |
1877 | ipv6 { | |
1878 | export where (source = RTS_DEVICE) || (source = RTS_BABEL); | |
1879 | }; | |
12640c14 OZ |
1880 | } |
1881 | </code> | |
1882 | ||
3e52d112 JMM |
1883 | <sect1>Known issues |
1884 | <label id="babel-issues"> | |
1885 | ||
cf3e3845 OZ |
1886 | <p>When retracting a route, Babel generates an unreachable route for a little |
1887 | while (according to RFC). The interaction of this behavior with other protocols | |
1888 | is not well tested and strange things may happen. | |
1889 | ||
937e75d8 | 1890 | |
5bf35a9a | 1891 | <sect>BFD |
b9864aa8 | 1892 | <label id="bfd"> |
1ec52253 OZ |
1893 | |
1894 | <sect1>Introduction | |
b9864aa8 | 1895 | <label id="bfd-intro"> |
1ec52253 OZ |
1896 | |
1897 | <p>Bidirectional Forwarding Detection (BFD) is not a routing protocol itself, it | |
1898 | is an independent tool providing liveness and failure detection. Routing | |
1899 | protocols like OSPF and BGP use integrated periodic "hello" messages to monitor | |
1900 | liveness of neighbors, but detection times of these mechanisms are high (e.g. 40 | |
1901 | seconds by default in OSPF, could be set down to several seconds). BFD offers | |
1902 | universal, fast and low-overhead mechanism for failure detection, which could be | |
1903 | attached to any routing protocol in an advisory role. | |
1904 | ||
1905 | <p>BFD consists of mostly independent BFD sessions. Each session monitors an | |
1906 | unicast bidirectional path between two BFD-enabled routers. This is done by | |
1907 | periodically sending control packets in both directions. BFD does not handle | |
1908 | neighbor discovery, BFD sessions are created on demand by request of other | |
1909 | protocols (like OSPF or BGP), which supply appropriate information like IP | |
1910 | addresses and associated interfaces. When a session changes its state, these | |
1911 | protocols are notified and act accordingly (e.g. break an OSPF adjacency when | |
1912 | the BFD session went down). | |
1913 | ||
7935b9d2 PT |
1914 | <p>BIRD implements basic BFD behavior as defined in <rfc id="5880"> (some |
1915 | advanced features like the echo mode or authentication are not implemented), IP | |
1916 | transport for BFD as defined in <rfc id="5881"> and <rfc id="5883"> and | |
1917 | interaction with client protocols as defined in <rfc id="5882">. | |
1ec52253 | 1918 | |
d96ec7f6 OZ |
1919 | <p>BFD packets are sent with a dynamic source port number. Linux systems use by |
1920 | default a bit different dynamic port range than the IANA approved one | |
1921 | (49152-65535). If you experience problems with compatibility, please adjust | |
8c703ecf | 1922 | <cf>/proc/sys/net/ipv4/ip_local_port_range</cf>. |
d96ec7f6 | 1923 | |
1ec52253 | 1924 | <sect1>Configuration |
b9864aa8 | 1925 | <label id="bfd-config"> |
1ec52253 OZ |
1926 | |
1927 | <p>BFD configuration consists mainly of multiple definitions of interfaces. | |
1928 | Most BFD config options are session specific. When a new session is requested | |
1929 | and dynamically created, it is configured from one of these definitions. For | |
1930 | sessions to directly connected neighbors, <cf/interface/ definitions are chosen | |
1931 | based on the interface associated with the session, while <cf/multihop/ | |
1932 | definition is used for multihop sessions. If no definition is relevant, the | |
1933 | session is just created with the default configuration. Therefore, an empty BFD | |
1934 | configuration is often sufficient. | |
1935 | ||
1936 | <p>Note that to use BFD for other protocols like OSPF or BGP, these protocols | |
1937 | also have to be configured to request BFD sessions, usually by <cf/bfd/ option. | |
1938 | ||
8c703ecf OZ |
1939 | <p>A BFD instance not associated with any VRF handles session requests from all |
1940 | other protocols, even ones associated with a VRF. Such setup would work for | |
1941 | single-hop BFD sessions if <cf/net.ipv4.udp_l3mdev_accept/ sysctl is enabled, | |
1942 | but does not currently work for multihop sessions. Another approach is to | |
1943 | configure multiple BFD instances, one for each VRF (including the default VRF). | |
1944 | Each BFD instance associated with a VRF (regular or default) only handles | |
1945 | session requests from protocols in the same VRF. | |
1946 | ||
1ec52253 OZ |
1947 | <p>Some of BFD session options require <m/time/ value, which has to be specified |
1948 | with the appropriate unit: <m/num/ <cf/s/|<cf/ms/|<cf/us/. Although microseconds | |
1949 | are allowed as units, practical minimum values are usually in order of tens of | |
1950 | milliseconds. | |
1951 | ||
1952 | <code> | |
1953 | protocol bfd [<name>] { | |
1954 | interface <interface pattern> { | |
1955 | interval <time>; | |
1956 | min rx interval <time>; | |
1957 | min tx interval <time>; | |
1958 | idle tx interval <time>; | |
1959 | multiplier <num>; | |
1960 | passive <switch>; | |
e03dc6a9 OZ |
1961 | authentication none; |
1962 | authentication simple; | |
1963 | authentication [meticulous] keyed md5|sha1; | |
1964 | password "<text>"; | |
1965 | password "<text>" { | |
1966 | id <num>; | |
1967 | generate from "<date>"; | |
1968 | generate to "<date>"; | |
1969 | accept from "<date>"; | |
1970 | accept to "<date>"; | |
1971 | from "<date>"; | |
1972 | to "<date>"; | |
1973 | }; | |
1ec52253 OZ |
1974 | }; |
1975 | multihop { | |
1976 | interval <time>; | |
1977 | min rx interval <time>; | |
1978 | min tx interval <time>; | |
1979 | idle tx interval <time>; | |
1980 | multiplier <num>; | |
1981 | passive <switch>; | |
1982 | }; | |
1983 | neighbor <ip> [dev "<interface>"] [local <ip>] [multihop <switch>]; | |
1984 | } | |
1985 | </code> | |
1986 | ||
1987 | <descrip> | |
9df52a98 | 1988 | <tag><label id="bfd-iface">interface <m/pattern/ [, <m/.../] { <m/options/ }</tag> |
1ec52253 OZ |
1989 | Interface definitions allow to specify options for sessions associated |
1990 | with such interfaces and also may contain interface specific options. | |
b9864aa8 | 1991 | See <ref id="proto-iface" name="interface"> common option for a detailed |
1ec52253 OZ |
1992 | description of interface patterns. Note that contrary to the behavior of |
1993 | <cf/interface/ definitions of other protocols, BFD protocol would accept | |
1994 | sessions (in default configuration) even on interfaces not covered by | |
1995 | such definitions. | |
1996 | ||
b9864aa8 | 1997 | <tag><label id="bfd-multihop">multihop { <m/options/ }</tag> |
1ec52253 OZ |
1998 | Multihop definitions allow to specify options for multihop BFD sessions, |
1999 | in the same manner as <cf/interface/ definitions are used for directly | |
2000 | connected sessions. Currently only one such definition (for all multihop | |
2001 | sessions) could be used. | |
2002 | ||
b9864aa8 | 2003 | <tag><label id="bfd-neighbor">neighbor <m/ip/ [dev "<m/interface/"] [local <m/ip/] [multihop <m/switch/]</tag> |
1ec52253 OZ |
2004 | BFD sessions are usually created on demand as requested by other |
2005 | protocols (like OSPF or BGP). This option allows to explicitly add | |
2006 | a BFD session to the specified neighbor regardless of such requests. | |
523f020b | 2007 | |
1ec52253 | 2008 | The session is identified by the IP address of the neighbor, with |
dad92c30 | 2009 | optional specification of used interface and local IP. By default |
fff7498d | 2010 | the neighbor must be directly connected, unless the session is |
1ec52253 OZ |
2011 | configured as multihop. Note that local IP must be specified for |
2012 | multihop sessions. | |
2013 | </descrip> | |
2014 | ||
2015 | <p>Session specific options (part of <cf/interface/ and <cf/multihop/ definitions): | |
2016 | ||
2017 | <descrip> | |
b9864aa8 | 2018 | <tag><label id="bfd-interval">interval <m/time/</tag> |
1ec52253 OZ |
2019 | BFD ensures availability of the forwarding path associated with the |
2020 | session by periodically sending BFD control packets in both | |
2021 | directions. The rate of such packets is controlled by two options, | |
2022 | <cf/min rx interval/ and <cf/min tx interval/ (see below). This option | |
2023 | is just a shorthand to set both of these options together. | |
2024 | ||
b9864aa8 | 2025 | <tag><label id="bfd-min-rx-interval">min rx interval <m/time/</tag> |
1ec52253 OZ |
2026 | This option specifies the minimum RX interval, which is announced to the |
2027 | neighbor and used there to limit the neighbor's rate of generated BFD | |
2028 | control packets. Default: 10 ms. | |
2029 | ||
b9864aa8 | 2030 | <tag><label id="bfd-min-tx-interval">min tx interval <m/time/</tag> |
1ec52253 OZ |
2031 | This option specifies the desired TX interval, which controls the rate |
2032 | of generated BFD control packets (together with <cf/min rx interval/ | |
2033 | announced by the neighbor). Note that this value is used only if the BFD | |
2034 | session is up, otherwise the value of <cf/idle tx interval/ is used | |
2035 | instead. Default: 100 ms. | |
2036 | ||
b9864aa8 | 2037 | <tag><label id="bfd-idle-tx-interval">idle tx interval <m/time/</tag> |
1ec52253 OZ |
2038 | In order to limit unnecessary traffic in cases where a neighbor is not |
2039 | available or not running BFD, the rate of generated BFD control packets | |
2040 | is lower when the BFD session is not up. This option specifies the | |
2041 | desired TX interval in such cases instead of <cf/min tx interval/. | |
2042 | Default: 1 s. | |
2043 | ||
b9864aa8 | 2044 | <tag><label id="bfd-multiplier">multiplier <m/num/</tag> |
1ec52253 OZ |
2045 | Failure detection time for BFD sessions is based on established rate of |
2046 | BFD control packets (<cf>min rx/tx interval</cf>) multiplied by this | |
2047 | multiplier, which is essentially (ignoring jitter) a number of missed | |
2048 | packets after which the session is declared down. Note that rates and | |
2049 | multipliers could be different in each direction of a BFD session. | |
2050 | Default: 5. | |
2051 | ||
b9864aa8 | 2052 | <tag><label id="bfd-passive">passive <m/switch/</tag> |
fff7498d | 2053 | Generally, both BFD session endpoints try to establish the session by |
1ec52253 OZ |
2054 | sending control packets to the other side. This option allows to enable |
2055 | passive mode, which means that the router does not send BFD packets | |
2056 | until it has received one from the other side. Default: disabled. | |
e03dc6a9 OZ |
2057 | |
2058 | <tag>authentication none</tag> | |
2059 | No passwords are sent in BFD packets. This is the default value. | |
2060 | ||
2061 | <tag>authentication simple</tag> | |
2062 | Every packet carries 16 bytes of password. Received packets lacking this | |
2063 | password are ignored. This authentication mechanism is very weak. | |
2064 | ||
2065 | <tag>authentication [meticulous] keyed md5|sha1</tag> | |
2066 | An authentication code is appended to each packet. The cryptographic | |
2067 | algorithm is keyed MD5 or keyed SHA-1. Note that the algorithm is common | |
2068 | for all keys (on one interface), in contrast to OSPF or RIP, where it | |
2069 | is a per-key option. Passwords (keys) are not sent open via network. | |
2070 | ||
2071 | The <cf/meticulous/ variant means that cryptographic sequence numbers | |
2072 | are increased for each sent packet, while in the basic variant they are | |
2073 | increased about once per second. Generally, the <cf/meticulous/ variant | |
2074 | offers better resistance to replay attacks but may require more | |
2075 | computation. | |
2076 | ||
2077 | <tag>password "<M>text</M>"</tag> | |
7e8d6116 | 2078 | Specifies a password used for authentication. See <ref id="proto-pass" |
e03dc6a9 OZ |
2079 | name="password"> common option for detailed description. Note that |
2080 | password option <cf/algorithm/ is not available in BFD protocol. The | |
2081 | algorithm is selected by <cf/authentication/ option for all passwords. | |
2082 | ||
1ec52253 OZ |
2083 | </descrip> |
2084 | ||
2085 | <sect1>Example | |
b9864aa8 | 2086 | <label id="bfd-exam"> |
1ec52253 OZ |
2087 | |
2088 | <p><code> | |
2089 | protocol bfd { | |
2090 | interface "eth*" { | |
2091 | min rx interval 20 ms; | |
2092 | min tx interval 50 ms; | |
2093 | idle tx interval 300 ms; | |
2094 | }; | |
2095 | interface "gre*" { | |
2096 | interval 200 ms; | |
2097 | multiplier 10; | |
2098 | passive; | |
2099 | }; | |
2100 | multihop { | |
2101 | interval 200 ms; | |
2102 | multiplier 10; | |
2103 | }; | |
2104 | ||
2105 | neighbor 192.168.1.10; | |
2106 | neighbor 192.168.2.2 dev "eth2"; | |
2107 | neighbor 192.168.10.1 local 192.168.1.1 multihop; | |
2108 | } | |
2109 | </code> | |
2110 | ||
dad92c30 | 2111 | |
371adba6 | 2112 | <sect>BGP |
b9864aa8 | 2113 | <label id="bgp"> |
1b55b1a3 | 2114 | |
dad92c30 OZ |
2115 | <p>The Border Gateway Protocol is the routing protocol used for backbone level |
2116 | routing in the today's Internet. Contrary to other protocols, its convergence | |
2117 | does not rely on all routers following the same rules for route selection, | |
2118 | making it possible to implement any routing policy at any router in the network, | |
2119 | the only restriction being that if a router advertises a route, it must accept | |
2120 | and forward packets according to it. | |
2121 | ||
2122 | <p>BGP works in terms of autonomous systems (often abbreviated as AS). Each AS | |
2123 | is a part of the network with common management and common routing policy. It is | |
2124 | identified by a unique 16-bit number (ASN). Routers within each AS usually | |
2125 | exchange AS-internal routing information with each other using an interior | |
2126 | gateway protocol (IGP, such as OSPF or RIP). Boundary routers at the border of | |
2127 | the AS communicate global (inter-AS) network reachability information with their | |
2128 | neighbors in the neighboring AS'es via exterior BGP (eBGP) and redistribute | |
2129 | received information to other routers in the AS via interior BGP (iBGP). | |
2130 | ||
2131 | <p>Each BGP router sends to its neighbors updates of the parts of its routing | |
2132 | table it wishes to export along with complete path information (a list of AS'es | |
2133 | the packet will travel through if it uses the particular route) in order to | |
2134 | avoid routing loops. | |
56ab03c7 | 2135 | |
71c51aa4 | 2136 | <sect1>Supported standards |
c49e4a65 OZ |
2137 | <label id="bgp-standards"> |
2138 | ||
71c51aa4 | 2139 | <p> |
c49e4a65 OZ |
2140 | <itemize> |
2141 | <item> <rfc id="4271"> - Border Gateway Protocol 4 (BGP) | |
2142 | <item> <rfc id="1997"> - BGP Communities Attribute | |
2143 | <item> <rfc id="2385"> - Protection of BGP Sessions via TCP MD5 Signature | |
2144 | <item> <rfc id="2545"> - Use of BGP Multiprotocol Extensions for IPv6 | |
2145 | <item> <rfc id="2918"> - Route Refresh Capability | |
2146 | <item> <rfc id="3107"> - Carrying Label Information in BGP | |
2147 | <item> <rfc id="4360"> - BGP Extended Communities Attribute | |
2148 | <item> <rfc id="4364"> - BGP/MPLS IPv4 Virtual Private Networks | |
2149 | <item> <rfc id="4456"> - BGP Route Reflection | |
2150 | <item> <rfc id="4486"> - Subcodes for BGP Cease Notification Message | |
2151 | <item> <rfc id="4659"> - BGP/MPLS IPv6 Virtual Private Networks | |
2152 | <item> <rfc id="4724"> - Graceful Restart Mechanism for BGP | |
2153 | <item> <rfc id="4760"> - Multiprotocol extensions for BGP | |
2154 | <item> <rfc id="4798"> - Connecting IPv6 Islands over IPv4 MPLS | |
2155 | <item> <rfc id="5065"> - AS confederations for BGP | |
2156 | <item> <rfc id="5082"> - Generalized TTL Security Mechanism | |
2157 | <item> <rfc id="5492"> - Capabilities Advertisement with BGP | |
2158 | <item> <rfc id="5549"> - Advertising IPv4 NLRI with an IPv6 Next Hop | |
2159 | <item> <rfc id="5575"> - Dissemination of Flow Specification Rules | |
2160 | <item> <rfc id="5668"> - 4-Octet AS Specific BGP Extended Community | |
2161 | <item> <rfc id="6286"> - AS-Wide Unique BGP Identifier | |
2162 | <item> <rfc id="6608"> - Subcodes for BGP Finite State Machine Error | |
2163 | <item> <rfc id="6793"> - BGP Support for 4-Octet AS Numbers | |
09ee846d | 2164 | <item> <rfc id="7311"> - Accumulated IGP Metric Attribute for BGP |
c49e4a65 OZ |
2165 | <item> <rfc id="7313"> - Enhanced Route Refresh Capability for BGP |
2166 | <item> <rfc id="7606"> - Revised Error Handling for BGP UPDATE Messages | |
2167 | <item> <rfc id="7911"> - Advertisement of Multiple Paths in BGP | |
2168 | <item> <rfc id="7947"> - Internet Exchange BGP Route Server | |
2169 | <item> <rfc id="8092"> - BGP Large Communities Attribute | |
7fc55925 | 2170 | <item> <rfc id="8203"> - BGP Administrative Shutdown Communication |
3831b619 | 2171 | <item> <rfc id="8212"> - Default EBGP Route Propagation Behavior without Policies |
c49e4a65 | 2172 | </itemize> |
5459fac6 | 2173 | |
371adba6 | 2174 | <sect1>Route selection rules |
b9864aa8 | 2175 | <label id="bgp-route-select-rules"> |
5459fac6 MM |
2176 | |
2177 | <p>BGP doesn't have any simple metric, so the rules for selection of an optimal | |
2178 | route among multiple BGP routes with the same preference are a bit more complex | |
dad92c30 OZ |
2179 | and they are implemented according to the following algorithm. It starts the |
2180 | first rule, if there are more "best" routes, then it uses the second rule to | |
2181 | choose among them and so on. | |
5459fac6 MM |
2182 | |
2183 | <itemize> | |
5a203dac | 2184 | <item>Prefer route with the highest Local Preference attribute. |
5459fac6 | 2185 | <item>Prefer route with the shortest AS path. |
b74f45f8 | 2186 | <item>Prefer IGP origin over EGP and EGP origin over incomplete. |
5459fac6 | 2187 | <item>Prefer the lowest value of the Multiple Exit Discriminator. |
b74f45f8 OZ |
2188 | <item>Prefer routes received via eBGP over ones received via iBGP. |
2189 | <item>Prefer routes with lower internal distance to a boundary router. | |
5a203dac | 2190 | <item>Prefer the route with the lowest value of router ID of the |
5459fac6 MM |
2191 | advertising router. |
2192 | </itemize> | |
56ab03c7 | 2193 | |
b74f45f8 | 2194 | <sect1>IGP routing table |
b9864aa8 | 2195 | <label id="bgp-igp-routing-table"> |
b74f45f8 | 2196 | |
dad92c30 OZ |
2197 | <p>BGP is mainly concerned with global network reachability and with routes to |
2198 | other autonomous systems. When such routes are redistributed to routers in the | |
2199 | AS via BGP, they contain IP addresses of a boundary routers (in route attribute | |
2200 | NEXT_HOP). BGP depends on existing IGP routing table with AS-internal routes to | |
2201 | determine immediate next hops for routes and to know their internal distances to | |
2202 | boundary routers for the purpose of BGP route selection. In BIRD, there is | |
2203 | usually one routing table used for both IGP routes and BGP routes. | |
b74f45f8 | 2204 | |
3e52d112 JMM |
2205 | <sect1>Protocol configuration |
2206 | <label id="bgp-proto-config"> | |
56ab03c7 | 2207 | |
dad92c30 OZ |
2208 | <p>Each instance of the BGP corresponds to one neighboring router. This allows |
2209 | to set routing policy and all the other parameters differently for each neighbor | |
2210 | using the following configuration parameters: | |
5459fac6 MM |
2211 | |
2212 | <descrip> | |
7a8ae228 | 2213 | <tag><label id="bgp-local">local [<m/ip/] [port <m/number/] [as <m/number/]</tag> |
dad92c30 OZ |
2214 | Define which AS we are part of. (Note that contrary to other IP routers, |
2215 | BIRD is able to act as a router located in multiple AS'es simultaneously, | |
2216 | but in such cases you need to tweak the BGP paths manually in the filters | |
2217 | to get consistent behavior.) Optional <cf/ip/ argument specifies a source | |
7a8ae228 | 2218 | address, equivalent to the <cf/source address/ option (see below). |
159d619c | 2219 | Optional <cf/port/ argument specifies the local BGP port instead of |
7a8ae228 OZ |
2220 | standard port 179. The parameter may be used multiple times with |
2221 | different sub-options (e.g., both <cf/local 10.0.0.1 as 65000;/ and | |
2222 | <cf/local 10.0.0.1; local as 65000;/ are valid). This parameter is | |
2223 | mandatory. | |
f3e59178 | 2224 | |
dbbe4a78 | 2225 | <tag><label id="bgp-neighbor">neighbor [<m/ip/ | range <m/prefix/] [port <m/number/] [as <m/number/] [internal|external]</tag> |
dad92c30 | 2226 | Define neighboring router this instance will be talking to and what AS |
a1beb8f3 | 2227 | it is located in. In case the neighbor is in the same AS as we are, we |
23ee6b1c | 2228 | automatically switch to IBGP. Alternatively, it is possible to specify |
96e4d096 | 2229 | just <cf/internal/ or <cf/external/ instead of AS number, in that case |
23ee6b1c OZ |
2230 | either local AS number, or any external AS number is accepted. |
2231 | Optionally, the remote port may also be specified. Like <cf/local/ | |
2232 | parameter, this parameter may also be used multiple times with different | |
2233 | sub-options. This parameter is mandatory. | |
a1beb8f3 | 2234 | |
dbbe4a78 OZ |
2235 | It is possible to specify network prefix (with <cf/range/ keyword) |
2236 | instead of explicit neighbor IP address. This enables dynamic BGP | |
2237 | behavior, where the BGP instance listens on BGP port, but new BGP | |
2238 | instances are spawned for incoming BGP connections (if source address | |
2239 | matches the network prefix). It is possible to mix regular BGP instances | |
2240 | with dynamic BGP instances and have multiple dynamic BGP instances with | |
2241 | different ranges. | |
2242 | ||
b9864aa8 | 2243 | <tag><label id="bgp-iface">interface <m/string/</tag> |
a1beb8f3 OZ |
2244 | Define interface we should use for link-local BGP IPv6 sessions. |
2245 | Interface can also be specified as a part of <cf/neighbor address/ | |
33b6c292 OZ |
2246 | (e.g., <cf/neighbor fe80::1234%eth0 as 65000;/). The option may also be |
2247 | used for non link-local sessions when it is necessary to explicitly | |
2248 | specify an interface, but only for direct (not multihop) sessions. | |
dad92c30 | 2249 | |
b9864aa8 | 2250 | <tag><label id="bgp-direct">direct</tag> |
dad92c30 OZ |
2251 | Specify that the neighbor is directly connected. The IP address of the |
2252 | neighbor must be from a directly reachable IP range (i.e. associated | |
2253 | with one of your router's interfaces), otherwise the BGP session | |
2254 | wouldn't start but it would wait for such interface to appear. The | |
2255 | alternative is the <cf/multihop/ option. Default: enabled for eBGP. | |
2256 | ||
b9864aa8 | 2257 | <tag><label id="bgp-multihop">multihop [<m/number/]</tag> |
dad92c30 OZ |
2258 | Configure multihop BGP session to a neighbor that isn't directly |
2259 | connected. Accurately, this option should be used if the configured | |
2260 | neighbor IP address does not match with any local network subnets. Such | |
2261 | IP address have to be reachable through system routing table. The | |
2262 | alternative is the <cf/direct/ option. For multihop BGP it is | |
2263 | recommended to explicitly configure the source address to have it | |
2264 | stable. Optional <cf/number/ argument can be used to specify the number | |
2265 | of hops (used for TTL). Note that the number of networks (edges) in a | |
2266 | path is counted; i.e., if two BGP speakers are separated by one router, | |
2267 | the number of hops is 2. Default: enabled for iBGP. | |
2268 | ||
b9864aa8 | 2269 | <tag><label id="bgp-source-address">source address <m/ip/</tag> |
1cab2b4a OZ |
2270 | Define local address we should use as a source address for the BGP |
2271 | session. Default: the address of the local end of the interface our | |
2272 | neighbor is connected to. | |
9be9a264 | 2273 | |
dbbe4a78 OZ |
2274 | <tag><label id="bgp-dynamic-name">dynamic name "<m/text/"</tag> |
2275 | Define common prefix of names used for new BGP instances spawned when | |
e840cb9c | 2276 | dynamic BGP behavior is active. Actual names also contain numeric |
dbbe4a78 OZ |
2277 | index to distinguish individual instances. Default: "dynbgp". |
2278 | ||
96e4d096 | 2279 | <tag><label id="bgp-dynamic-name-digits">dynamic name digits <m/number/</tag> |
dbbe4a78 OZ |
2280 | Define minimum number of digits for index in names of spawned dynamic |
2281 | BGP instances. E.g., if set to 2, then the first name would be | |
2282 | "dynbgp01". Default: 0. | |
2283 | ||
82f42ea0 OZ |
2284 | <tag><label id="bgp-strict-bind">strict bind <m/switch/</tag> |
2285 | Specify whether BGP listening socket should be bound to a specific local | |
2286 | address (the same as the <cf/source address/) and associated interface, | |
2287 | or to all addresses. Binding to a specific address could be useful in | |
2288 | cases like running multiple BIRD instances on a machine, each using its | |
2289 | IP address. Note that listening sockets bound to a specific address and | |
2290 | to all addresses collide, therefore either all BGP protocols (of the | |
2291 | same address family and using the same local port) should have set | |
2292 | <cf/strict bind/, or none of them. Default: disabled. | |
2293 | ||
b9864aa8 | 2294 | <tag><label id="bgp-check-link">check link <M>switch</M></tag> |
523f020b OZ |
2295 | BGP could use hardware link state into consideration. If enabled, |
2296 | BIRD tracks the link state of the associated interface and when link | |
2297 | disappears (e.g. an ethernet cable is unplugged), the BGP session is | |
2298 | immediately shut down. Note that this option cannot be used with | |
cf3e3845 | 2299 | multihop BGP. Default: enabled for direct BGP, disabled otherwise. |
523f020b | 2300 | |
5bd73431 | 2301 | <tag><label id="bgp-bfd">bfd <M>switch</M>|graceful</tag> |
1ec52253 OZ |
2302 | BGP could use BFD protocol as an advisory mechanism for neighbor |
2303 | liveness and failure detection. If enabled, BIRD setups a BFD session | |
2304 | for the BGP neighbor and tracks its liveness by it. This has an | |
2305 | advantage of an order of magnitude lower detection times in case of | |
5bd73431 OZ |
2306 | failure. When a neighbor failure is detected, the BGP session is |
2307 | restarted. Optionally, it can be configured (by <cf/graceful/ argument) | |
2308 | to trigger graceful restart instead of regular restart. Note that BFD | |
2309 | protocol also has to be configured, see <ref id="bfd" name="BFD"> | |
2310 | section for details. Default: disabled. | |
1ec52253 | 2311 | |
b9864aa8 | 2312 | <tag><label id="bgp-ttl-security">ttl security <m/switch/</tag> |
7935b9d2 PT |
2313 | Use GTSM (<rfc id="5082"> - the generalized TTL security mechanism). GTSM |
2314 | protects against spoofed packets by ignoring received packets with a | |
dad92c30 | 2315 | smaller than expected TTL. To work properly, GTSM have to be enabled on |
7935b9d2 PT |
2316 | both sides of a BGP session. If both <cf/ttl security/ and |
2317 | <cf/multihop/ options are enabled, <cf/multihop/ option should specify | |
2318 | proper hop value to compute expected TTL. Kernel support required: | |
2319 | Linux: 2.6.34+ (IPv4), 2.6.35+ (IPv6), BSD: since long ago, IPv4 only. | |
2320 | Note that full (ICMP protection, for example) <rfc id="5082"> support is | |
2321 | provided by Linux only. Default: disabled. | |
523f020b | 2322 | |
82f42ea0 | 2323 | <tag><label id="bgp-password">password <m/string/</tag> |
7935b9d2 PT |
2324 | Use this password for MD5 authentication of BGP sessions (<rfc id="2385">). When |
2325 | used on BSD systems, see also <cf/setkey/ option below. Default: no | |
2326 | authentication. | |
a7baa098 | 2327 | |
b9864aa8 | 2328 | <tag><label id="bgp-setkey">setkey <m/switch/</tag> |
a7baa098 OZ |
2329 | On BSD systems, keys for TCP MD5 authentication are stored in the global |
2330 | SA/SP database, which can be accessed by external utilities (e.g. | |
2331 | setkey(8)). BIRD configures security associations in the SA/SP database | |
2332 | automatically based on <cf/password/ options (see above), this option | |
2333 | allows to disable automatic updates by BIRD when manual configuration by | |
2334 | external utilities is preferred. Note that automatic SA/SP database | |
2335 | updates are currently implemented only for FreeBSD. Passwords have to be | |
2336 | set manually by an external utility on NetBSD and OpenBSD. Default: | |
2337 | enabled (ignored on non-FreeBSD). | |
dad92c30 | 2338 | |
b9864aa8 | 2339 | <tag><label id="bgp-passive">passive <m/switch/</tag> |
dad92c30 | 2340 | Standard BGP behavior is both initiating outgoing connections and |
7935b9d2 | 2341 | accepting incoming connections. In passive mode, outgoing connections |
dad92c30 OZ |
2342 | are not initiated. Default: off. |
2343 | ||
5509e17d OZ |
2344 | <tag><label id="bgp-confederation">confederation <m/number/</tag> |
2345 | BGP confederations (<rfc id="5065">) are collections of autonomous | |
2346 | systems that act as one entity to external systems, represented by one | |
2347 | confederation identifier (instead of AS numbers). This option allows to | |
2348 | enable BGP confederation behavior and to specify the local confederation | |
2349 | identifier. When BGP confederations are used, all BGP speakers that are | |
2350 | members of the BGP confederation should have the same confederation | |
2351 | identifier configured. Default: 0 (no confederation). | |
2352 | ||
2353 | <tag><label id="bgp-confederation-member">confederation member <m/switch/</tag> | |
2354 | When BGP confederations are used, this option allows to specify whether | |
2355 | the BGP neighbor is a member of the same confederation as the local BGP | |
2356 | speaker. The option is unnecessary (and ignored) for IBGP sessions, as | |
2357 | the same AS number implies the same confederation. Default: no. | |
2358 | ||
b9864aa8 | 2359 | <tag><label id="bgp-rr-client">rr client</tag> |
dad92c30 OZ |
2360 | Be a route reflector and treat the neighbor as a route reflection |
2361 | client. Default: disabled. | |
2362 | ||
b9864aa8 | 2363 | <tag><label id="bgp-rr-cluster-id">rr cluster id <m/IPv4 address/</tag> |
dad92c30 OZ |
2364 | Route reflectors use cluster id to avoid route reflection loops. When |
2365 | there is one route reflector in a cluster it usually uses its router id | |
2366 | as a cluster id, but when there are more route reflectors in a cluster, | |
2367 | these need to be configured (using this option) to use a common cluster | |
2368 | id. Clients in a cluster need not know their cluster id and this option | |
2369 | is not allowed for them. Default: the same as router id. | |
2370 | ||
b9864aa8 | 2371 | <tag><label id="bgp-rs-client">rs client</tag> |
dad92c30 OZ |
2372 | Be a route server and treat the neighbor as a route server client. |
2373 | A route server is used as a replacement for full mesh EBGP routing in | |
2374 | Internet exchange points in a similar way to route reflectors used in | |
7935b9d2 PT |
2375 | IBGP routing. BIRD does not implement obsoleted <rfc id="1863">, but |
2376 | uses ad-hoc implementation, which behaves like plain EBGP but reduces | |
dad92c30 | 2377 | modifications to advertised route attributes to be transparent (for |
7935b9d2 PT |
2378 | example does not prepend its AS number to AS PATH attribute and |
2379 | keeps MED attribute). Default: disabled. | |
dad92c30 | 2380 | |
1950a479 OZ |
2381 | <tag><label id="bgp-allow-local-pref">allow bgp_local_pref <m/switch/</tag> |
2382 | A standard BGP implementation do not send the Local Preference attribute | |
2383 | to eBGP neighbors and ignore this attribute if received from eBGP | |
2384 | neighbors, as per <rfc id="4271">. When this option is enabled on an | |
2385 | eBGP session, this attribute will be sent to and accepted from the peer, | |
2386 | which is useful for example if you have a setup like in <rfc id="7938">. | |
2387 | The option does not affect iBGP sessions. Default: off. | |
2388 | ||
b9864aa8 | 2389 | <tag><label id="bgp-allow-local-as">allow local as [<m/number/]</tag> |
dad92c30 OZ |
2390 | BGP prevents routing loops by rejecting received routes with the local |
2391 | AS number in the AS path. This option allows to loose or disable the | |
2392 | check. Optional <cf/number/ argument can be used to specify the maximum | |
2393 | number of local ASNs in the AS path that is allowed for received | |
2394 | routes. When the option is used without the argument, the check is | |
2395 | completely disabled and you should ensure loop-free behavior by some | |
2396 | other means. Default: 0 (no local AS number allowed). | |
2397 | ||
d54a69ac OZ |
2398 | <tag><label id="bgp-allow-as-sets">allow as sets [<m/switch/]</tag> |
2399 | AS path attribute received with BGP routes may contain not only | |
2400 | sequences of AS numbers, but also sets of AS numbers. These rarely used | |
2401 | artifacts are results of inter-AS route aggregation. AS sets are | |
2402 | deprecated (<rfc id="6472">), and likely to be rejected in the future, | |
2403 | as they complicate security features like RPKI validation. When this | |
2404 | option is disabled, then received AS paths with AS sets are rejected as | |
2405 | malformed and corresponding BGP updates are treated as withdraws. | |
becda563 | 2406 | Default: on. |
d54a69ac | 2407 | |
b9864aa8 | 2408 | <tag><label id="bgp-enable-route-refresh">enable route refresh <m/switch/</tag> |
9aed29e6 OZ |
2409 | After the initial route exchange, BGP protocol uses incremental updates |
2410 | to keep BGP speakers synchronized. Sometimes (e.g., if BGP speaker | |
2411 | changes its import filter, or if there is suspicion of inconsistency) it | |
2412 | is necessary to do a new complete route exchange. BGP protocol extension | |
7935b9d2 PT |
2413 | Route Refresh (<rfc id="2918">) allows BGP speaker to request |
2414 | re-advertisement of all routes from its neighbor. BGP protocol | |
2415 | extension Enhanced Route Refresh (<rfc id="7313">) specifies explicit | |
2416 | begin and end for such exchanges, therefore the receiver can remove | |
2417 | stale routes that were not advertised during the exchange. This option | |
2418 | specifies whether BIRD advertises these capabilities and supports | |
2419 | related procedures. Note that even when disabled, BIRD can send route | |
2420 | refresh requests. Default: on. | |
bf47fe4b | 2421 | |
7fc55925 OZ |
2422 | <tag><label id="bgp-graceful-restart">graceful restart <m/switch/|aware</tag> |
2423 | When a BGP speaker restarts or crashes, neighbors will discard all | |
2424 | received paths from the speaker, which disrupts packet forwarding even | |
2425 | when the forwarding plane of the speaker remains intact. <rfc id="4724"> | |
2426 | specifies an optional graceful restart mechanism to alleviate this | |
2427 | issue. This option controls the mechanism. It has three states: | |
2428 | Disabled, when no support is provided. Aware, when the graceful restart | |
2429 | support is announced and the support for restarting neighbors is | |
2430 | provided, but no local graceful restart is allowed (i.e. receiving-only | |
2431 | role). Enabled, when the full graceful restart support is provided | |
2432 | (i.e. both restarting and receiving role). Restarting role could be also | |
2433 | configured per-channel. Note that proper support for local graceful | |
2434 | restart requires also configuration of other protocols. Default: aware. | |
2435 | ||
b9864aa8 | 2436 | <tag><label id="bgp-graceful-restart-time">graceful restart time <m/number/</tag> |
6eda3f13 OZ |
2437 | The restart time is announced in the BGP graceful restart capability |
2438 | and specifies how long the neighbor would wait for the BGP session to | |
2439 | re-establish after a restart before deleting stale routes. Default: | |
2440 | 120 seconds. | |
2441 | ||
5bd73431 OZ |
2442 | <tag><label id="bgp-long-lived-graceful-restart">long lived graceful restart <m/switch/|aware</tag> |
2443 | The long-lived graceful restart is an extension of the traditional | |
2444 | <ref id="bgp-graceful-restart" name="BGP graceful restart">, where stale | |
2445 | routes are kept even after the <ref id="bgp-graceful-restart-time" | |
2446 | name="restart time"> expires for additional long-lived stale time, but | |
2447 | they are marked with the LLGR_STALE community, depreferenced, and | |
2448 | withdrawn from routers not supporting LLGR. Like traditional BGP | |
2449 | graceful restart, it has three states: disabled, aware (receiving-only), | |
2450 | and enabled. Note that long-lived graceful restart requires at least | |
2451 | aware level of traditional BGP graceful restart. Default: aware, unless | |
2452 | graceful restart is disabled. | |
2453 | ||
2454 | <tag><label id="bgp-long-lived-stale-time">long lived stale time <m/number/</tag> | |
2455 | The long-lived stale time is announced in the BGP long-lived graceful | |
2456 | restart capability and specifies how long the neighbor would keep stale | |
2457 | routes depreferenced during long-lived graceful restart until either the | |
2458 | session is re-stablished and synchronized or the stale time expires and | |
2459 | routes are removed. Default: 3600 seconds. | |
2460 | ||
b9864aa8 | 2461 | <tag><label id="bgp-interpret-communities">interpret communities <m/switch/</tag> |
7935b9d2 PT |
2462 | <rfc id="1997"> demands that BGP speaker should process well-known |
2463 | communities like no-export (65535, 65281) or no-advertise (65535, | |
2464 | 65282). For example, received route carrying a no-adverise community | |
2465 | should not be advertised to any of its neighbors. If this option is | |
2466 | enabled (which is by default), BIRD has such behavior automatically (it | |
2467 | is evaluated when a route is exported to the BGP protocol just before | |
2468 | the export filter). Otherwise, this integrated processing of | |
2469 | well-known communities is disabled. In that case, similar behavior can | |
2470 | be implemented in the export filter. Default: on. | |
dad92c30 | 2471 | |
b9864aa8 | 2472 | <tag><label id="bgp-enable-as4">enable as4 <m/switch/</tag> |
dad92c30 OZ |
2473 | BGP protocol was designed to use 2B AS numbers and was extended later to |
2474 | allow 4B AS number. BIRD supports 4B AS extension, but by disabling this | |
2475 | option it can be persuaded not to advertise it and to maintain old-style | |
2476 | sessions with its neighbors. This might be useful for circumventing bugs | |
2477 | in neighbor's implementation of 4B AS extension. Even when disabled | |
2478 | (off), BIRD behaves internally as AS4-aware BGP router. Default: on. | |
2479 | ||
b9864aa8 | 2480 | <tag><label id="bgp-enable-extended-messages">enable extended messages <m/switch/</tag> |
79a4f74a | 2481 | The BGP protocol uses maximum message length of 4096 bytes. This option |
be7c1aef OZ |
2482 | provides an extension (<rfc id="8654">) to allow extended messages with |
2483 | length up to 65535 bytes. Default: off. | |
79a4f74a | 2484 | |
b9864aa8 | 2485 | <tag><label id="bgp-capabilities">capabilities <m/switch/</tag> |
dad92c30 OZ |
2486 | Use capability advertisement to advertise optional capabilities. This is |
2487 | standard behavior for newer BGP implementations, but there might be some | |
2488 | older BGP implementations that reject such connection attempts. When | |
2489 | disabled (off), features that request it (4B AS support) are also | |
2490 | disabled. Default: on, with automatic fallback to off when received | |
2491 | capability-related error. | |
2492 | ||
b9864aa8 | 2493 | <tag><label id="bgp-advertise-ipv4">advertise ipv4 <m/switch/</tag> |
dad92c30 | 2494 | Advertise IPv4 multiprotocol capability. This is not a correct behavior |
7935b9d2 PT |
2495 | according to the strict interpretation of <rfc id="4760">, but it is |
2496 | widespread and required by some BGP implementations (Cisco and Quagga). | |
2497 | This option is relevant to IPv4 mode with enabled capability | |
2498 | advertisement only. Default: on. | |
dad92c30 | 2499 | |
b9864aa8 | 2500 | <tag><label id="bgp-disable-after-error">disable after error <m/switch/</tag> |
dad92c30 OZ |
2501 | When an error is encountered (either locally or by the other side), |
2502 | disable the instance automatically and wait for an administrator to fix | |
2503 | the problem manually. Default: off. | |
2504 | ||
c408d807 OZ |
2505 | <tag><label id="bgp-disable-after-cease">disable after cease <m/switch/|<m/set-of-flags/</tag> |
2506 | When a Cease notification is received, disable the instance | |
2507 | automatically and wait for an administrator to fix the problem manually. | |
2508 | When used with <m/switch/ argument, it means handle every Cease subtype | |
2509 | with the exception of <cf/connection collision/. Default: off. | |
2510 | ||
2511 | The <m/set-of-flags/ allows to narrow down relevant Cease subtypes. The | |
2512 | syntax is <cf>{<m/flag/ [, <m/.../] }</cf>, where flags are: <cf/cease/, | |
2513 | <cf/prefix limit hit/, <cf/administrative shutdown/, | |
2514 | <cf/peer deconfigured/, <cf/administrative reset/, | |
2515 | <cf/connection rejected/, <cf/configuration change/, | |
2516 | <cf/connection collision/, <cf/out of resources/. | |
2517 | ||
b9864aa8 | 2518 | <tag><label id="bgp-hold-time">hold time <m/number/</tag> |
dad92c30 OZ |
2519 | Time in seconds to wait for a Keepalive message from the other side |
2520 | before considering the connection stale. Default: depends on agreement | |
2521 | with the neighboring router, we prefer 240 seconds if the other side is | |
2522 | willing to accept it. | |
2523 | ||
b9864aa8 | 2524 | <tag><label id="bgp-startup-hold-time">startup hold time <m/number/</tag> |
dad92c30 OZ |
2525 | Value of the hold timer used before the routers have a chance to exchange |
2526 | open messages and agree on the real value. Default: 240 seconds. | |
2527 | ||
b9864aa8 | 2528 | <tag><label id="bgp-keepalive-time">keepalive time <m/number/</tag> |
dad92c30 OZ |
2529 | Delay in seconds between sending of two consecutive Keepalive messages. |
2530 | Default: One third of the hold time. | |
2531 | ||
b9864aa8 | 2532 | <tag><label id="bgp-connect-delay-time">connect delay time <m/number/</tag> |
6cf72d7a OZ |
2533 | Delay in seconds between protocol startup and the first attempt to |
2534 | connect. Default: 5 seconds. | |
2535 | ||
b9864aa8 | 2536 | <tag><label id="bgp-connect-retry-time">connect retry time <m/number/</tag> |
dad92c30 OZ |
2537 | Time in seconds to wait before retrying a failed attempt to connect. |
2538 | Default: 120 seconds. | |
2539 | ||
b9864aa8 | 2540 | <tag><label id="bgp-error-wait-time">error wait time <m/number/,<m/number/</tag> |
dad92c30 OZ |
2541 | Minimum and maximum delay in seconds between a protocol failure (either |
2542 | local or reported by the peer) and automatic restart. Doesn't apply | |
2543 | when <cf/disable after error/ is configured. If consecutive errors | |
2544 | happen, the delay is increased exponentially until it reaches the | |
2545 | maximum. Default: 60, 300. | |
2546 | ||
b9864aa8 | 2547 | <tag><label id="bgp-error-forget-time">error forget time <m/number/</tag> |
dad92c30 OZ |
2548 | Maximum time in seconds between two protocol failures to treat them as a |
2549 | error sequence which makes <cf/error wait time/ increase exponentially. | |
2550 | Default: 300 seconds. | |
2551 | ||
b9864aa8 | 2552 | <tag><label id="bgp-path-metric">path metric <m/switch/</tag> |
dad92c30 OZ |
2553 | Enable comparison of path lengths when deciding which BGP route is the |
2554 | best one. Default: on. | |
2555 | ||
b9864aa8 | 2556 | <tag><label id="bgp-med-metric">med metric <m/switch/</tag> |
dad92c30 OZ |
2557 | Enable comparison of MED attributes (during best route selection) even |
2558 | between routes received from different ASes. This may be useful if all | |
2559 | MED attributes contain some consistent metric, perhaps enforced in | |
2560 | import filters of AS boundary routers. If this option is disabled, MED | |
2561 | attributes are compared only if routes are received from the same AS | |
2562 | (which is the standard behavior). Default: off. | |
2563 | ||
3e52d112 JMM |
2564 | <tag><label id="bgp-deterministic-med">deterministic med <m/switch/</tag> |
2565 | BGP route selection algorithm is often viewed as a comparison between | |
2566 | individual routes (e.g. if a new route appears and is better than the | |
2567 | current best one, it is chosen as the new best one). But the proper | |
2568 | route selection, as specified by <rfc id="4271">, cannot be fully | |
2569 | implemented in that way. The problem is mainly in handling the MED | |
2570 | attribute. BIRD, by default, uses an simplification based on individual | |
2571 | route comparison, which in some cases may lead to temporally dependent | |
2572 | behavior (i.e. the selection is dependent on the order in which routes | |
2573 | appeared). This option enables a different (and slower) algorithm | |
2574 | implementing proper <rfc id="4271"> route selection, which is | |
2575 | deterministic. Alternative way how to get deterministic behavior is to | |
2576 | use <cf/med metric/ option. This option is incompatible with <ref | |
2577 | id="dsc-table-sorted" name="sorted tables">. Default: off. | |
2578 | ||
2579 | <tag><label id="bgp-igp-metric">igp metric <m/switch/</tag> | |
2580 | Enable comparison of internal distances to boundary routers during best | |
cf3e3845 | 2581 | route selection. Default: on. |
3e52d112 JMM |
2582 | |
2583 | <tag><label id="bgp-prefer-older">prefer older <m/switch/</tag> | |
2584 | Standard route selection algorithm breaks ties by comparing router IDs. | |
2585 | This changes the behavior to prefer older routes (when both are external | |
2586 | and from different peer). For details, see <rfc id="5004">. Default: off. | |
2587 | ||
2588 | <tag><label id="bgp-default-med">default bgp_med <m/number/</tag> | |
2589 | Value of the Multiple Exit Discriminator to be used during route | |
2590 | selection when the MED attribute is missing. Default: 0. | |
2591 | ||
2592 | <tag><label id="bgp-default-local-pref">default bgp_local_pref <m/number/</tag> | |
2593 | A default value for the Local Preference attribute. It is used when | |
2594 | a new Local Preference attribute is attached to a route by the BGP | |
2595 | protocol itself (for example, if a route is received through eBGP and | |
2596 | therefore does not have such attribute). Default: 100 (0 in pre-1.2.0 | |
2597 | versions of BIRD). | |
2598 | </descrip> | |
2599 | ||
2600 | <sect1>Channel configuration | |
2601 | <label id="bgp-channel-config"> | |
2602 | ||
2603 | <p>BGP supports several AFIs and SAFIs over one connection. Every AFI/SAFI | |
2604 | announced to the peer corresponds to one channel. The table of supported AFI/SAFIs | |
2605 | together with their appropriate channels follows. | |
2606 | ||
71c51aa4 | 2607 | <table loc="h"> |
3e52d112 JMM |
2608 | <tabular ca="l|l|l|r|r"> |
2609 | <bf/Channel name/ | <bf/Table nettype/ | <bf/IGP table allowed/ | <bf/AFI/ | <bf/SAFI/ | |
71c51aa4 | 2610 | @<hline> |
3e52d112 JMM |
2611 | <cf/ipv4/ | <cf/ipv4/ | <cf/ipv4/ and <cf/ipv6/ | 1 | 1 |
2612 | @ <cf/ipv6/ | <cf/ipv6/ | <cf/ipv4/ and <cf/ipv6/ | 2 | 1 | |
2613 | @ <cf/ipv4 multicast/ | <cf/ipv4/ | <cf/ipv4/ and <cf/ipv6/ | 1 | 2 | |
2614 | @ <cf/ipv6 multicast/ | <cf/ipv6/ | <cf/ipv4/ and <cf/ipv6/ | 2 | 2 | |
2615 | @ <cf/ipv4 mpls/ | <cf/ipv4/ | <cf/ipv4/ and <cf/ipv6/ | 1 | 4 | |
2616 | @ <cf/ipv6 mpls/ | <cf/ipv6/ | <cf/ipv4/ and <cf/ipv6/ | 2 | 4 | |
2617 | @ <cf/vpn4 mpls/ | <cf/vpn4/ | <cf/ipv4/ and <cf/ipv6/ | 1 | 128 | |
2618 | @ <cf/vpn6 mpls/ | <cf/vpn6/ | <cf/ipv4/ and <cf/ipv6/ | 2 | 128 | |
2619 | @ <cf/vpn4 multicast/ | <cf/vpn4/ | <cf/ipv4/ and <cf/ipv6/ | 1 | 129 | |
2620 | @ <cf/vpn6 multicast/ | <cf/vpn6/ | <cf/ipv4/ and <cf/ipv6/ | 2 | 129 | |
2621 | @ <cf/flow4/ | <cf/flow4/ | --- | 1 | 133 | |
2622 | @ <cf/flow6/ | <cf/flow6/ | --- | 2 | 133 | |
2623 | </tabular> | |
71c51aa4 | 2624 | </table> |
3e52d112 | 2625 | |
3831b619 OZ |
2626 | <p>Due to <rfc id="8212">, external BGP protocol requires explicit configuration |
2627 | of import and export policies (in contrast to other protocols, where default | |
2628 | policies of <cf/import all/ and <cf/export none/ are used in absence of explicit | |
2629 | configuration). Note that blanket policies like <cf/all/ or <cf/none/ can still | |
2630 | be used in explicit configuration. | |
2631 | ||
72163bd5 | 2632 | <p>BGP channels have additional config options (together with the common ones): |
3e52d112 JMM |
2633 | |
2634 | <descrip> | |
3c360581 OZ |
2635 | <tag><label id="bgp-mandatory">mandatory <m/switch/</tag> |
2636 | When local and neighbor sets of configured AFI/SAFI pairs differ, | |
2637 | capability negotiation ensures that a common subset is used. For | |
2638 | mandatory channels their associated AFI/SAFI must be negotiated | |
2639 | (i.e., also announced by the neighbor), otherwise BGP session | |
2640 | negotiation fails with <it/'Required capability missing'/ error. | |
2641 | Regardless, at least one AFI/SAFI must be negotiated in order to BGP | |
2642 | session be successfully established. Default: off. | |
2643 | ||
1cab2b4a OZ |
2644 | <tag><label id="bgp-next-hop-keep">next hop keep <m/switch/|ibgp|ebgp</tag> |
2645 | Do not modify the Next Hop attribute and advertise the current one | |
2646 | unchanged even in cases where our own local address should be used | |
2647 | instead. This is necessary when the BGP speaker does not forward network | |
2648 | traffic (route servers and some route reflectors) and also can be useful | |
2649 | in some other cases (e.g. multihop EBGP sessions). Can be enabled for | |
2650 | all routes, or just for routes received from IBGP / EBGP neighbors. | |
2651 | Default: disabled for regular BGP, enabled for route servers, | |
2652 | <cf/ibgp/ for route reflectors. | |
2653 | ||
2654 | <tag><label id="bgp-next-hop-self">next hop self <m/switch/|ibgp|ebgp</tag> | |
2655 | Always advertise our own local address as a next hop, even in cases | |
2656 | where the current Next Hop attribute should be used unchanged. This is | |
2657 | sometimes used for routes propagated from EBGP to IBGP when IGP routing | |
2658 | does not cover inter-AS links, therefore IP addreses of EBGP neighbors | |
2659 | are not resolvable through IGP. Can be enabled for all routes, or just | |
2660 | for routes received from IBGP / EBGP neighbors. Default: disabled. | |
3e52d112 JMM |
2661 | |
2662 | <tag><label id="bgp-next-hop-address">next hop address <m/ip/</tag> | |
1cab2b4a OZ |
2663 | Specify which address to use when our own local address should be |
2664 | announced in the Next Hop attribute. Default: the source address of the | |
2665 | BGP session (if acceptable), or the preferred address of an associated | |
2666 | interface. | |
3e52d112 JMM |
2667 | |
2668 | <tag><label id="bgp-missing-lladdr">missing lladdr self|drop|ignore</tag> | |
2669 | Next Hop attribute in BGP-IPv6 sometimes contains just the global IPv6 | |
2670 | address, but sometimes it has to contain both global and link-local IPv6 | |
2671 | addresses. This option specifies what to do if BIRD have to send both | |
2672 | addresses but does not know link-local address. This situation might | |
2673 | happen when routes from other protocols are exported to BGP, or when | |
2674 | improper updates are received from BGP peers. <cf/self/ means that BIRD | |
2675 | advertises its own local address instead. <cf/drop/ means that BIRD | |
2676 | skips that prefixes and logs error. <cf/ignore/ means that BIRD ignores | |
2677 | the problem and sends just the global address (and therefore forms | |
2678 | improper BGP update). Default: <cf/self/, unless BIRD is configured as a | |
2679 | route server (option <cf/rs client/), in that case default is <cf/ignore/, | |
2680 | because route servers usually do not forward packets themselves. | |
2681 | ||
2682 | <tag><label id="bgp-gateway">gateway direct|recursive</tag> | |
2683 | For received routes, their <cf/gw/ (immediate next hop) attribute is | |
2684 | computed from received <cf/bgp_next_hop/ attribute. This option | |
2685 | specifies how it is computed. Direct mode means that the IP address from | |
2686 | <cf/bgp_next_hop/ is used if it is directly reachable, otherwise the | |
2687 | neighbor IP address is used. Recursive mode means that the gateway is | |
2688 | computed by an IGP routing table lookup for the IP address from | |
2689 | <cf/bgp_next_hop/. Note that there is just one level of indirection in | |
2690 | recursive mode - the route obtained by the lookup must not be recursive | |
2691 | itself, to prevent mutually recursive routes. | |
2692 | ||
2693 | Recursive mode is the behavior specified by the BGP | |
2694 | standard. Direct mode is simpler, does not require any routes in a | |
2695 | routing table, and was used in older versions of BIRD, but does not | |
2696 | handle well nontrivial iBGP setups and multihop. Recursive mode is | |
2697 | incompatible with <ref id="dsc-table-sorted" name="sorted tables">. Default: | |
2698 | <cf/direct/ for direct sessions, <cf/recursive/ for multihop sessions. | |
be4cd99a | 2699 | |
3e52d112 JMM |
2700 | <tag><label id="bgp-igp-table">igp table <m/name/</tag> |
2701 | Specifies a table that is used as an IGP routing table. The type of this | |
2702 | table must be as allowed in the table above. This option is allowed once | |
2703 | for every allowed table type. Default: the same as the main table | |
2704 | the channel is connected to (if eligible). | |
dad92c30 | 2705 | |
9e92f357 | 2706 | <tag><label id="bgp-import-table">import table <m/switch/</tag> |
1cab2b4a | 2707 | A BGP import table contains all received routes from given BGP neighbor, |
9e92f357 OZ |
2708 | before application of import filters. It is also called <em/Adj-RIB-In/ |
2709 | in BGP terminology. BIRD BGP by default operates without import tables, | |
2710 | in which case received routes are just processed by import filters, | |
2711 | accepted ones are stored in the master table, and the rest is forgotten. | |
2712 | Enabling <cf/import table/ allows to store unprocessed routes, which can | |
2713 | be examined later by <cf/show route/, and can be used to reconfigure | |
2714 | import filters without full route refresh. Default: off. | |
2715 | ||
b7d7599c OZ |
2716 | <tag><label id="bgp-export-table">export table <m/switch/</tag> |
2717 | A BGP export table contains all routes sent to given BGP neighbor, after | |
2718 | application of export filters. It is also called <em/Adj-RIB-Out/ in BGP | |
2719 | terminology. BIRD BGP by default operates without export tables, in | |
2720 | which case routes from master table are just processed by export filters | |
2721 | and then announced by BGP. Enabling <cf/export table/ allows to store | |
2722 | routes after export filter processing, so they can be examined later by | |
2723 | <cf/show route/, and can be used to eliminate unnecessary updates or | |
2724 | withdraws. Default: off. | |
2725 | ||
3e52d112 JMM |
2726 | <tag><label id="bgp-secondary">secondary <m/switch/</tag> |
2727 | Usually, if an export filter rejects a selected route, no other route is | |
2728 | propagated for that network. This option allows to try the next route in | |
2729 | order until one that is accepted is found or all routes for that network | |
2730 | are rejected. This can be used for route servers that need to propagate | |
2731 | different tables to each client but do not want to have these tables | |
2732 | explicitly (to conserve memory). This option requires that the connected | |
2733 | routing table is <ref id="dsc-table-sorted" name="sorted">. Default: off. | |
dad92c30 | 2734 | |
a63d20aa OZ |
2735 | <tag><label id="bgp-extended-next-hop">extended next hop <m/switch/</tag> |
2736 | BGP expects that announced next hops have the same address family as | |
2737 | associated network prefixes. This option provides an extension to use | |
2738 | IPv4 next hops with IPv6 prefixes and vice versa. For IPv4 / VPNv4 | |
2739 | channels, the behavior is controlled by the Extended Next Hop Encoding | |
2740 | capability, as described in <rfc id="5549">. For IPv6 / VPNv6 channels, | |
2741 | just IPv4-mapped IPv6 addresses are used, as described in | |
2742 | <rfc id="4798"> and <rfc id="4659">. Default: off. | |
2743 | ||
3e52d112 JMM |
2744 | <tag><label id="bgp-add-paths">add paths <m/switch/|rx|tx</tag> |
2745 | Standard BGP can propagate only one path (route) per destination network | |
2746 | (usually the selected one). This option controls the add-path protocol | |
2747 | extension, which allows to advertise any number of paths to a | |
2748 | destination. Note that to be active, add-path has to be enabled on both | |
2749 | sides of the BGP session, but it could be enabled separately for RX and | |
2750 | TX direction. When active, all available routes accepted by the export | |
2751 | filter are advertised to the neighbor. Default: off. | |
dad92c30 | 2752 | |
09ee846d OZ |
2753 | <tag><label id="bgp-aigp">aigp <m/switch/|originate</tag> |
2754 | The BGP protocol does not use a common metric like other routing | |
2755 | protocols, instead it uses a set of criteria for route selection | |
2756 | consisting both overall AS path length and a distance to the nearest AS | |
2757 | boundary router. Assuming that metrics of different autonomous systems | |
2758 | are incomparable, once a route is propagated from an AS to a next one, | |
2759 | the distance in the old AS does not matter. | |
2760 | ||
2761 | The AIGP extension (<rfc id="7311">) allows to propagate accumulated | |
2762 | IGP metric (in the AIGP attribute) through both IBGP and EBGP links, | |
2763 | computing total distance through multiple autonomous systems (assuming | |
2764 | they use comparable IGP metric). The total AIGP metric is compared in | |
2765 | the route selection process just after Local Preference comparison (and | |
2766 | before AS path length comparison). | |
2767 | ||
2768 | This option controls whether AIGP attribute propagation is allowed on | |
2769 | the session. Optionally, it can be set to <cf/originate/, which not only | |
2770 | allows AIGP attribute propagation, but also new AIGP attributes are | |
2771 | automatically attached to non-BGP routes with valid IGP metric (e.g. | |
2772 | <cf/ospf_metric1/) as they are exported to the BGP session. Default: | |
2773 | enabled for IBGP (and intra-confederation EBGP), disabled for regular | |
2774 | EBGP. | |
2775 | ||
2776 | <tag><label id="bgp-cost">cost <m/number/</tag> | |
2777 | When BGP <ref id="bgp-gateway" name="gateway mode"> is <cf/recursive/ | |
2778 | (mainly multihop IBGP sessions), then the distance to BGP next hop is | |
2779 | based on underlying IGP metric. This option specifies the distance to | |
2780 | BGP next hop for BGP sessions in direct gateway mode (mainly direct | |
2781 | EBGP sessions). | |
2782 | ||
7fc55925 OZ |
2783 | <tag><label id="bgp-graceful-restart-c">graceful restart <m/switch/</tag> |
2784 | Although BGP graceful restart is configured mainly by protocol-wide | |
2785 | <ref id="bgp-graceful-restart" name="options">, it is possible to | |
2786 | configure restarting role per AFI/SAFI pair by this channel option. | |
2787 | The option is ignored if graceful restart is disabled by protocol-wide | |
2788 | option. Default: off in aware mode, on in full mode. | |
5bd73431 OZ |
2789 | |
2790 | <tag><label id="bgp-long-lived-graceful-restart-c">long lived graceful restart <m/switch/</tag> | |
2791 | BGP long-lived graceful restart is configured mainly by protocol-wide | |
2792 | <ref id="bgp-long-lived-graceful-restart" name="options">, but the | |
2793 | restarting role can be set per AFI/SAFI pair by this channel option. | |
2794 | The option is ignored if long-lived graceful restart is disabled by | |
2795 | protocol-wide option. Default: off in aware mode, on in full mode. | |
2796 | ||
2797 | <tag><label id="bgp-long-lived-stale-time-c">long lived stale time <m/number/</tag> | |
2798 | Like previous graceful restart channel options, this option allows to | |
2799 | set <ref id="bgp-long-lived-stale-time" name="long lived stale time"> | |
2800 | per AFI/SAFI pair instead of per protocol. Default: set by protocol-wide | |
2801 | option. | |
5459fac6 MM |
2802 | </descrip> |
2803 | ||
371adba6 | 2804 | <sect1>Attributes |
b9864aa8 | 2805 | <label id="bgp-attr"> |
56ab03c7 | 2806 | |
dad92c30 OZ |
2807 | <p>BGP defines several route attributes. Some of them (those marked with |
2808 | `<tt/I/' in the table below) are available on internal BGP connections only, | |
2809 | some of them (marked with `<tt/O/') are optional. | |
5459fac6 MM |
2810 | |
2811 | <descrip> | |
157f6c2a | 2812 | <tag><label id="rta-bgp-path">bgppath bgp_path</tag> |
dad92c30 OZ |
2813 | Sequence of AS numbers describing the AS path the packet will travel |
2814 | through when forwarded according to the particular route. In case of | |
2815 | internal BGP it doesn't contain the number of the local AS. | |
2816 | ||
157f6c2a | 2817 | <tag><label id="rta-bgp-local-pref">int bgp_local_pref [I]</tag> |
dad92c30 OZ |
2818 | Local preference value used for selection among multiple BGP routes (see |
2819 | the selection rules above). It's used as an additional metric which is | |
2820 | propagated through the whole local AS. | |
2821 | ||
157f6c2a | 2822 | <tag><label id="rta-bgp-med">int bgp_med [O]</tag> |
dad92c30 OZ |
2823 | The Multiple Exit Discriminator of the route is an optional attribute |
2824 | which is used on external (inter-AS) links to convey to an adjacent AS | |
2825 | the optimal entry point into the local AS. The received attribute is | |
2826 | also propagated over internal BGP links. The attribute value is zeroed | |
2827 | when a route is exported to an external BGP instance to ensure that the | |
2828 | attribute received from a neighboring AS is not propagated to other | |
2829 | neighboring ASes. A new value might be set in the export filter of an | |
7935b9d2 PT |
2830 | external BGP instance. See <rfc id="4451"> for further discussion of |
2831 | BGP MED attribute. | |
5a203dac | 2832 | |
157f6c2a | 2833 | <tag><label id="rta-bgp-origin">enum bgp_origin</tag> |
dad92c30 OZ |
2834 | Origin of the route: either <cf/ORIGIN_IGP/ if the route has originated |
2835 | in an interior routing protocol or <cf/ORIGIN_EGP/ if it's been imported | |
2836 | from the <tt>EGP</tt> protocol (nowadays it seems to be obsolete) or | |
2837 | <cf/ORIGIN_INCOMPLETE/ if the origin is unknown. | |
5a203dac | 2838 | |
157f6c2a | 2839 | <tag><label id="rta-bgp-next-hop">ip bgp_next_hop</tag> |
dad92c30 OZ |
2840 | Next hop to be used for forwarding of packets to this destination. On |
2841 | internal BGP connections, it's an address of the originating router if | |
2842 | it's inside the local AS or a boundary router the packet will leave the | |
2843 | AS through if it's an exterior route, so each BGP speaker within the AS | |
2844 | has a chance to use the shortest interior path possible to this point. | |
5a203dac | 2845 | |
157f6c2a | 2846 | <tag><label id="rta-bgp-atomic-aggr">void bgp_atomic_aggr [O]</tag> |
dad92c30 OZ |
2847 | This is an optional attribute which carries no value, but the sole |
2848 | presence of which indicates that the route has been aggregated from | |
2849 | multiple routes by some router on the path from the originator. | |
5a203dac | 2850 | |
09ee846d OZ |
2851 | <tag><label id="rta-bgp-aggregator">void bgp_aggregator [O]</tag> |
2852 | This is an optional attribute specifying AS number and IP address of the | |
2853 | BGP router that created the route by aggregating multiple BGP routes. | |
2854 | Currently, the attribute is not accessible from filters. | |
2855 | ||
157f6c2a | 2856 | <tag><label id="rta-bgp-community">clist bgp_community [O]</tag> |
dad92c30 OZ |
2857 | List of community values associated with the route. Each such value is a |
2858 | pair (represented as a <cf/pair/ data type inside the filters) of 16-bit | |
2859 | integers, the first of them containing the number of the AS which | |
2860 | defines the community and the second one being a per-AS identifier. | |
2861 | There are lots of uses of the community mechanism, but generally they | |
2862 | are used to carry policy information like "don't export to USA peers". | |
2863 | As each AS can define its own routing policy, it also has a complete | |
2864 | freedom about which community attributes it defines and what will their | |
2865 | semantics be. | |
2866 | ||
157f6c2a | 2867 | <tag><label id="rta-bgp-ext-community">eclist bgp_ext_community [O]</tag> |
dad92c30 OZ |
2868 | List of extended community values associated with the route. Extended |
2869 | communities have similar usage as plain communities, but they have an | |
2870 | extended range (to allow 4B ASNs) and a nontrivial structure with a type | |
2871 | field. Individual community values are represented using an <cf/ec/ data | |
2872 | type inside the filters. | |
2873 | ||
157f6c2a | 2874 | <tag><label id="rta-bgp-large-community">lclist bgp_large_community [O]</tag> |
cec4a73c OZ |
2875 | List of large community values associated with the route. Large BGP |
2876 | communities is another variant of communities, but contrary to extended | |
2877 | communities they behave very much the same way as regular communities, | |
2878 | just larger -- they are uniform untyped triplets of 32bit numbers. | |
2879 | Individual community values are represented using an <cf/lc/ data type | |
2880 | inside the filters. | |
2881 | ||
157f6c2a | 2882 | <tag><label id="rta-bgp-originator-id">quad bgp_originator_id [I, O]</tag> |
dad92c30 OZ |
2883 | This attribute is created by the route reflector when reflecting the |
2884 | route and contains the router ID of the originator of the route in the | |
2885 | local AS. | |
2886 | ||
157f6c2a | 2887 | <tag><label id="rta-bgp-cluster-list">clist bgp_cluster_list [I, O]</tag> |
dad92c30 OZ |
2888 | This attribute contains a list of cluster IDs of route reflectors. Each |
2889 | route reflector prepends its cluster ID when reflecting the route. | |
09ee846d OZ |
2890 | |
2891 | <tag><label id="rta-bgp-aigp">void bgp_aigp [O]</tag> | |
2892 | This attribute contains accumulated IGP metric, which is a total | |
2893 | distance to the destination through multiple autonomous systems. | |
2894 | Currently, the attribute is not accessible from filters. | |
5459fac6 MM |
2895 | </descrip> |
2896 | ||
371adba6 | 2897 | <sect1>Example |
b9864aa8 | 2898 | <label id="bgp-exam"> |
56ab03c7 | 2899 | |
5459fac6 MM |
2900 | <p><code> |
2901 | protocol bgp { | |
cf3e3845 | 2902 | local 198.51.100.14 as 65000; # Use a private AS number |
9491f9f5 | 2903 | neighbor 198.51.100.130 as 64496; # Our neighbor ... |
6bcef225 | 2904 | multihop; # ... which is connected indirectly |
3e52d112 JMM |
2905 | ipv4 { |
2906 | export filter { # We use non-trivial export rules | |
2907 | if source = RTS_STATIC then { # Export only static routes | |
2908 | # Assign our community | |
2909 | bgp_community.add((65000,64501)); | |
2910 | # Artificially increase path length | |
2911 | # by advertising local AS number twice | |
2912 | if bgp_path ~ [= 65000 =] then | |
2913 | bgp_path.prepend(65000); | |
2914 | accept; | |
2915 | } | |
2916 | reject; | |
2917 | }; | |
2918 | import all; | |
2919 | next hop self; # advertise this router as next hop | |
2920 | igp table myigptable4; # IGP table for routes with IPv4 nexthops | |
2921 | igp table myigptable6; # IGP table for routes with IPv6 nexthops | |
2922 | }; | |
2923 | ipv6 { | |
2924 | export filter mylargefilter; # We use a named filter | |
2925 | import all; | |
2926 | missing lladdr self; | |
2927 | igp table myigptable4; # IGP table for routes with IPv4 nexthops | |
2928 | igp table myigptable6; # IGP table for routes with IPv6 nexthops | |
2929 | }; | |
2930 | ipv4 multicast { | |
2931 | import all; | |
2932 | export filter someotherfilter; | |
2933 | table mymulticasttable4; # Another IPv4 table, dedicated for multicast | |
2934 | igp table myigptable4; | |
2935 | }; | |
5459fac6 MM |
2936 | } |
2937 | </code> | |
2938 | ||
dad92c30 | 2939 | |
371adba6 | 2940 | <sect>Device |
b9864aa8 | 2941 | <label id="device"> |
1b55b1a3 | 2942 | |
dad92c30 OZ |
2943 | <p>The Device protocol is not a real routing protocol. It doesn't generate any |
2944 | routes and it only serves as a module for getting information about network | |
3e52d112 | 2945 | interfaces from the kernel. This protocol supports no channel. |
79a2b697 | 2946 | |
dad92c30 OZ |
2947 | <p>Except for very unusual circumstances, you probably should include this |
2948 | protocol in the configuration since almost all other protocols require network | |
2949 | interfaces to be defined for them to work with. | |
79a2b697 | 2950 | |
6f5603ba | 2951 | <sect1>Configuration |
b9864aa8 | 2952 | <label id="device-config"> |
79a2b697 MM |
2953 | |
2954 | <p><descrip> | |
b9864aa8 | 2955 | <tag><label id="device-scan-time">scan time <m/number/</tag> |
dad92c30 OZ |
2956 | Time in seconds between two scans of the network interface list. On |
2957 | systems where we are notified about interface status changes | |
2958 | asynchronously (such as newer versions of Linux), we need to scan the | |
2959 | list only in order to avoid confusion by lost notification messages, | |
2960 | so the default time is set to a large value. | |
2961 | ||
cf3e3845 | 2962 | <tag><label id="device-iface">interface <m/pattern/ [, <m/.../]</tag> |
cf3e3845 OZ |
2963 | By default, the Device protocol handles all interfaces without any |
2964 | configuration. Interface definitions allow to specify optional | |
2965 | parameters for specific interfaces. See <ref id="proto-iface" | |
2966 | name="interface"> common option for detailed description. Currently only | |
2967 | one interface option is available: | |
2968 | ||
2969 | <tag><label id="device-preferred">preferred <m/ip/</tag> | |
2970 | If a network interface has more than one IP address, BIRD chooses one of | |
2971 | them as a preferred one. Preferred IP address is used as source address | |
2972 | for packets or announced next hop by routing protocols. Precisely, BIRD | |
2973 | chooses one preferred IPv4 address, one preferred IPv6 address and one | |
2974 | preferred link-local IPv6 address. By default, BIRD chooses the first | |
2975 | found IP address as the preferred one. | |
2976 | ||
2977 | This option allows to specify which IP address should be preferred. May | |
2978 | be used multiple times for different address classes (IPv4, IPv6, IPv6 | |
2979 | link-local). In all cases, an address marked by operating system as | |
2980 | secondary cannot be chosen as the primary one. | |
79a2b697 MM |
2981 | </descrip> |
2982 | ||
79a2b697 | 2983 | <p>As the Device protocol doesn't generate any routes, it cannot have |
6f5603ba | 2984 | any attributes. Example configuration looks like this: |
79a2b697 MM |
2985 | |
2986 | <p><code> | |
2987 | protocol device { | |
2988 | scan time 10; # Scan the interfaces often | |
cf3e3845 OZ |
2989 | interface "eth0" { |
2990 | preferred 192.168.1.1; | |
2991 | preferred 2001:db8:1:10::1; | |
2992 | }; | |
79a2b697 MM |
2993 | } |
2994 | </code> | |
2995 | ||
cf3e3845 | 2996 | |
371adba6 | 2997 | <sect>Direct |
b9864aa8 | 2998 | <label id="direct"> |
1b55b1a3 | 2999 | |
79a2b697 | 3000 | <p>The Direct protocol is a simple generator of device routes for all the |
dad92c30 | 3001 | directly connected networks according to the list of interfaces provided by the |
cf3e3845 | 3002 | kernel via the Device protocol. The Direct protocol supports both IPv4 and IPv6 |
159d619c OZ |
3003 | channels; both can be configured simultaneously. It can also be configured with |
3004 | <ref id="ip-sadr-routes" name="IPv6 SADR"> channel instead of regular IPv6 | |
3005 | channel in order to be used together with SADR-enabled Babel protocol. | |
dad92c30 OZ |
3006 | |
3007 | <p>The question is whether it is a good idea to have such device routes in BIRD | |
3008 | routing table. OS kernel usually handles device routes for directly connected | |
3009 | networks by itself so we don't need (and don't want) to export these routes to | |
3010 | the kernel protocol. OSPF protocol creates device routes for its interfaces | |
159d619c OZ |
3011 | itself and BGP protocol is usually used for exporting aggregate routes. But the |
3012 | Direct protocol is necessary for distance-vector protocols like RIP or Babel to | |
3013 | announce local networks. | |
79a2b697 | 3014 | |
e90dd656 | 3015 | <p>There are just few configuration options for the Direct protocol: |
79a2b697 MM |
3016 | |
3017 | <p><descrip> | |
9df52a98 | 3018 | <tag><label id="direct-iface">interface <m/pattern/ [, <m/.../]</tag> |
dad92c30 OZ |
3019 | By default, the Direct protocol will generate device routes for all the |
3020 | interfaces available. If you want to restrict it to some subset of | |
d7c06285 OZ |
3021 | interfaces or addresses (e.g. if you're using multiple routing tables |
3022 | for policy routing and some of the policy domains don't contain all | |
b9864aa8 | 3023 | interfaces), just use this clause. See <ref id="proto-iface" name="interface"> |
d7c06285 OZ |
3024 | common option for detailed description. The Direct protocol uses |
3025 | extended interface clauses. | |
e90dd656 | 3026 | |
b9864aa8 | 3027 | <tag><label id="direct-check-link">check link <m/switch/</tag> |
e90dd656 OZ |
3028 | If enabled, a hardware link state (reported by OS) is taken into |
3029 | consideration. Routes for directly connected networks are generated only | |
3030 | if link up is reported and they are withdrawn when link disappears | |
3031 | (e.g., an ethernet cable is unplugged). Default value is no. | |
79a2b697 MM |
3032 | </descrip> |
3033 | ||
79a2b697 MM |
3034 | <p>Direct device routes don't contain any specific attributes. |
3035 | ||
4f88ac47 | 3036 | <p>Example config might look like this: |
79a2b697 MM |
3037 | |
3038 | <p><code> | |
3039 | protocol direct { | |
3e52d112 | 3040 | ipv4; |
3e52d112 | 3041 | ipv6; |
cf3e3845 | 3042 | interface "-arc*", "*"; # Exclude the ARCnets |
79a2b697 MM |
3043 | } |
3044 | </code> | |
3045 | ||
cf3e3845 | 3046 | |
371adba6 | 3047 | <sect>Kernel |
b9864aa8 | 3048 | <label id="krt"> |
1b55b1a3 | 3049 | |
0e4789c2 | 3050 | <p>The Kernel protocol is not a real routing protocol. Instead of communicating |
c429d4a4 | 3051 | with other routers in the network, it performs synchronization of BIRD's routing |
dad92c30 OZ |
3052 | tables with the OS kernel. Basically, it sends all routing table updates to the |
3053 | kernel and from time to time it scans the kernel tables to see whether some | |
3054 | routes have disappeared (for example due to unnoticed up/down transition of an | |
3055 | interface) or whether an `alien' route has been added by someone else (depending | |
3056 | on the <cf/learn/ switch, such routes are either ignored or accepted to our | |
f8e2d916 | 3057 | table). |
0e4789c2 | 3058 | |
d33cf3f4 OZ |
3059 | <p>Note that routes created by OS kernel itself, namely direct routes |
3060 | representing IP subnets of associated interfaces, are not imported even with | |
3061 | <cf/learn/ enabled. You can use <ref id="direct" name="Direct protocol"> to | |
3062 | generate these direct routes. | |
c429d4a4 | 3063 | |
dad92c30 OZ |
3064 | <p>If your OS supports only a single routing table, you can configure only one |
3065 | instance of the Kernel protocol. If it supports multiple tables (in order to | |
3066 | allow policy routing; such an OS is for example Linux), you can run as many | |
3067 | instances as you want, but each of them must be connected to a different BIRD | |
3068 | routing table and to a different kernel table. | |
0e4789c2 | 3069 | |
dad92c30 OZ |
3070 | <p>Because the kernel protocol is partially integrated with the connected |
3071 | routing table, there are two limitations - it is not possible to connect more | |
3072 | kernel protocols to the same routing table and changing route destination | |
3073 | (gateway) in an export filter of a kernel protocol does not work. Both | |
3074 | limitations can be overcome using another routing table and the pipe protocol. | |
cf3e3845 | 3075 | |
159d619c OZ |
3076 | <p>The Kernel protocol supports both IPv4 and IPv6 channels; only one channel |
3077 | can be configured in each protocol instance. On Linux, it also supports <ref | |
3078 | id="ip-sadr-routes" name="IPv6 SADR"> and <ref id="mpls-routes" name="MPLS"> | |
3079 | channels. | |
71ca7716 | 3080 | |
371adba6 | 3081 | <sect1>Configuration |
b9864aa8 | 3082 | <label id="krt-config"> |
0e4789c2 MM |
3083 | |
3084 | <p><descrip> | |
b9864aa8 | 3085 | <tag><label id="krt-persist">persist <m/switch/</tag> |
6eda3f13 OZ |
3086 | Tell BIRD to leave all its routes in the routing tables when it exits |
3087 | (instead of cleaning them up). | |
3088 | ||
b9864aa8 | 3089 | <tag><label id="krt-scan-time">scan time <m/number/</tag> |
6eda3f13 OZ |
3090 | Time in seconds between two consecutive scans of the kernel routing |
3091 | table. | |
3092 | ||
b9864aa8 | 3093 | <tag><label id="krt-learn">learn <m/switch/</tag> |
6eda3f13 OZ |
3094 | Enable learning of routes added to the kernel routing tables by other |
3095 | routing daemons or by the system administrator. This is possible only on | |
3096 | systems which support identification of route authorship. | |
3097 | ||
b9864aa8 | 3098 | <tag><label id="krt-kernel-table">kernel table <m/number/</tag> |
6eda3f13 OZ |
3099 | Select which kernel table should this particular instance of the Kernel |
3100 | protocol work with. Available only on systems supporting multiple | |
3101 | routing tables. | |
3102 | ||
b9864aa8 | 3103 | <tag><label id="krt-metric">metric <m/number/</tag> (Linux) |
4adcb9df OZ |
3104 | Use specified value as a kernel metric (priority) for all routes sent to |
3105 | the kernel. When multiple routes for the same network are in the kernel | |
3106 | routing table, the Linux kernel chooses one with lower metric. Also, | |
3107 | routes with different metrics do not clash with each other, therefore | |
3108 | using dedicated metric value is a reliable way to avoid overwriting | |
3109 | routes from other sources (e.g. kernel device routes). Metric 0 has a | |
3110 | special meaning of undefined metric, in which either OS default is used, | |
3111 | or per-route metric can be set using <cf/krt_metric/ attribute. Default: | |
bff21441 | 3112 | 32. |
4adcb9df | 3113 | |
b9864aa8 | 3114 | <tag><label id="krt-graceful-restart">graceful restart <m/switch/</tag> |
6eda3f13 OZ |
3115 | Participate in graceful restart recovery. If this option is enabled and |
3116 | a graceful restart recovery is active, the Kernel protocol will defer | |
3117 | synchronization of routing tables until the end of the recovery. Note | |
3118 | that import of kernel routes to BIRD is not affected. | |
8d9eef17 | 3119 | |
b9864aa8 | 3120 | <tag><label id="krt-merge-paths">merge paths <M>switch</M> [limit <M>number</M>]</tag> |
8d9eef17 OZ |
3121 | Usually, only best routes are exported to the kernel protocol. With path |
3122 | merging enabled, both best routes and equivalent non-best routes are | |
3123 | merged during export to generate one ECMP (equal-cost multipath) route | |
3124 | for each network. This is useful e.g. for BGP multipath. Note that best | |
3125 | routes are still pivotal for route export (responsible for most | |
3126 | properties of resulting ECMP routes), while exported non-best routes are | |
3127 | responsible just for additional multipath next hops. This option also | |
3128 | allows to specify a limit on maximal number of nexthops in one route. By | |
3129 | default, multipath merging is disabled. If enabled, default value of the | |
3130 | limit is 16. | |
0e4789c2 MM |
3131 | </descrip> |
3132 | ||
71ca7716 | 3133 | <sect1>Attributes |
b9864aa8 | 3134 | <label id="krt-attr"> |
71ca7716 | 3135 | |
dad92c30 OZ |
3136 | <p>The Kernel protocol defines several attributes. These attributes are |
3137 | translated to appropriate system (and OS-specific) route attributes. We support | |
3138 | these attributes: | |
71ca7716 OZ |
3139 | |
3140 | <descrip> | |
157f6c2a | 3141 | <tag><label id="rta-krt-source">int krt_source</tag> |
dad92c30 OZ |
3142 | The original source of the imported kernel route. The value is |
3143 | system-dependent. On Linux, it is a value of the protocol field of the | |
3144 | route. See /etc/iproute2/rt_protos for common values. On BSD, it is | |
72aed1a0 OZ |
3145 | based on STATIC and PROTOx flags. The attribute is read-only. |
3146 | ||
157f6c2a | 3147 | <tag><label id="rta-krt-metric">int krt_metric</tag> (Linux) |
dad92c30 OZ |
3148 | The kernel metric of the route. When multiple same routes are in a |
3149 | kernel routing table, the Linux kernel chooses one with lower metric. | |
4adcb9df OZ |
3150 | Note that preferred way to set kernel metric is to use protocol option |
3151 | <cf/metric/, unless per-route metric values are needed. | |
9ba2798c | 3152 | |
157f6c2a | 3153 | <tag><label id="rta-krt-prefsrc">ip krt_prefsrc</tag> (Linux) |
dad92c30 | 3154 | The preferred source address. Used in source address selection for |
79a4f74a | 3155 | outgoing packets. Has to be one of the IP addresses of the router. |
71ca7716 | 3156 | |
157f6c2a | 3157 | <tag><label id="rta-krt-realm">int krt_realm</tag> (Linux) |
dad92c30 | 3158 | The realm of the route. Can be used for traffic classification. |
6e75d0d2 | 3159 | |
157f6c2a | 3160 | <tag><label id="rta-krt-scope">int krt_scope</tag> (Linux IPv4) |
6e75d0d2 OZ |
3161 | The scope of the route. Valid values are 0-254, although Linux kernel |
3162 | may reject some values depending on route type and nexthop. It is | |
3163 | supposed to represent `indirectness' of the route, where nexthops of | |
3164 | routes are resolved through routes with a higher scope, but in current | |
3165 | kernels anything below <it/link/ (253) is treated as <it/global/ (0). | |
3166 | When not present, global scope is implied for all routes except device | |
3167 | routes, where link scope is used by default. | |
71ca7716 OZ |
3168 | </descrip> |
3169 | ||
6683d42d OZ |
3170 | <p>In Linux, there is also a plenty of obscure route attributes mostly focused |
3171 | on tuning TCP performance of local connections. BIRD supports most of these | |
3172 | attributes, see Linux or iproute2 documentation for their meaning. Attributes | |
3173 | <cf/krt_lock_*/ and <cf/krt_feature_*/ have type bool, others have type int. | |
3174 | Supported attributes are: | |
3175 | ||
3176 | <cf/krt_mtu/, <cf/krt_lock_mtu/, <cf/krt_window/, <cf/krt_lock_window/, | |
3177 | <cf/krt_rtt/, <cf/krt_lock_rtt/, <cf/krt_rttvar/, <cf/krt_lock_rttvar/, | |
3178 | <cf/krt_sstresh/, <cf/krt_lock_sstresh/, <cf/krt_cwnd/, <cf/krt_lock_cwnd/, | |
3179 | <cf/krt_advmss/, <cf/krt_lock_advmss/, <cf/krt_reordering/, <cf/krt_lock_reordering/, | |
3180 | <cf/krt_hoplimit/, <cf/krt_lock_hoplimit/, <cf/krt_rto_min/, <cf/krt_lock_rto_min/, | |
3181 | <cf/krt_initcwnd/, <cf/krt_initrwnd/, <cf/krt_quickack/, | |
3182 | <cf/krt_feature_ecn/, <cf/krt_feature_allfrag/ | |
3183 | ||
71ca7716 | 3184 | <sect1>Example |
b9864aa8 | 3185 | <label id="krt-exam"> |
71ca7716 | 3186 | |
326e33f5 | 3187 | <p>A simple configuration can look this way: |
0e4789c2 MM |
3188 | |
3189 | <p><code> | |
3190 | protocol kernel { | |
0e4789c2 MM |
3191 | export all; |
3192 | } | |
3193 | </code> | |
3194 | ||
3195 | <p>Or for a system with two routing tables: | |
3196 | ||
3197 | <p><code> | |
3198 | protocol kernel { # Primary routing table | |
3199 | learn; # Learn alien routes from the kernel | |
3200 | persist; # Don't remove routes on bird shutdown | |
3201 | scan time 10; # Scan kernel routing table every 10 seconds | |
3e52d112 JMM |
3202 | ipv4 { |
3203 | import all; | |
3204 | export all; | |
3205 | }; | |
0e4789c2 MM |
3206 | } |
3207 | ||
3208 | protocol kernel { # Secondary routing table | |
0e4789c2 | 3209 | kernel table 100; |
3e52d112 JMM |
3210 | ipv4 { |
3211 | table auxtable; | |
3212 | export all; | |
3213 | }; | |
a2a3ced8 | 3214 | } |
0e4789c2 MM |
3215 | </code> |
3216 | ||
dad92c30 | 3217 | |
fc1b9333 OZ |
3218 | <sect>MRT |
3219 | <label id="mrt"> | |
3220 | ||
3221 | <sect1>Introduction | |
3222 | <label id="mrt-intro"> | |
3223 | ||
3224 | <p>The MRT protocol is a component responsible for handling the Multi-Threaded | |
3225 | Routing Toolkit (MRT) routing information export format, which is mainly used | |
3226 | for collecting and analyzing of routing information from BGP routers. The MRT | |
3227 | protocol can be configured to do periodic dumps of routing tables, created MRT | |
3228 | files can be analyzed later by other tools. Independent MRT table dumps can also | |
3229 | be requested from BIRD client. There is also a feature to save incoming BGP | |
3230 | messages in MRT files, but it is controlled by <ref id="proto-mrtdump" | |
3231 | name="mrtdump"> options independently of MRT protocol, although that might | |
3232 | change in the future. | |
3233 | ||
3234 | BIRD implements the main MRT format specification as defined in <rfc id="6396"> | |
3235 | and the ADD_PATH extension (<rfc id="8050">). | |
3236 | ||
3237 | <sect1>Configuration | |
3238 | <label id="mrt-config"> | |
3239 | ||
3240 | <p>MRT configuration consists of several statements describing routing table | |
3241 | dumps. Multiple independent periodic dumps can be done as multiple MRT protocol | |
3242 | instances. The MRT protocol does not use channels. There are two mandatory | |
3243 | statements: <cf/filename/ and <cf/period/. | |
3244 | ||
3245 | The behavior can be modified by following configuration parameters: | |
3246 | ||
3247 | <descrip> | |
3248 | <tag><label id="mrt-table">table <m/name/ | "<m/pattern/"</tag> | |
3249 | Specify a routing table (or a set of routing tables described by a | |
3250 | wildcard pattern) that are to be dumped by the MRT protocol instance. | |
3251 | Default: the master table. | |
3252 | ||
3253 | <tag><label id="mrt-filter">filter { <m/filter commands/ }</tag> | |
3254 | The MRT protocol allows to specify a filter that is applied to routes as | |
3255 | they are dumped. Rejected routes are ignored and not saved to the MRT | |
3256 | dump file. Default: no filter. | |
3257 | ||
3258 | <tag><label id="mrt-where">where <m/filter expression/</tag> | |
3259 | An alternative way to specify a filter for the MRT protocol. | |
3260 | ||
3261 | <tag><label id="mrt-filename">filename "<m/filename/"</tag> | |
3262 | Specify a filename for MRT dump files. The filename may contain time | |
3263 | format sequences with <it/strftime(3)/ notation (see <it/man strftime/ | |
3264 | for details), there is also a sequence "%N" that is expanded to the name | |
3265 | of dumped table. Therefore, each periodic dump of each table can be | |
3266 | saved to a different file. Mandatory, see example below. | |
3267 | ||
3268 | <tag><label id="mrt-period">period <m/number/</tag> | |
3269 | Specify the time interval (in seconds) between periodic dumps. | |
3270 | Mandatory. | |
3271 | ||
3272 | <tag><label id="mrt-always-add-path">always add path <m/switch/</tag> | |
3273 | The MRT format uses special records (specified in <rfc id="8050">) for | |
3274 | routes received using BGP ADD_PATH extension to keep Path ID, while | |
3275 | other routes use regular records. This has advantage of better | |
3276 | compatibility with tools that do not know special records, but it loses | |
3277 | information about which route is the best route. When this option is | |
3278 | enabled, both ADD_PATH and non-ADD_PATH routes are stored in ADD_PATH | |
3279 | records and order of routes for network is preserved. Default: disabled. | |
3280 | </descrip> | |
3281 | ||
3282 | <sect1>Example | |
3283 | <label id="mrt-exam"> | |
3284 | ||
3285 | <p><code> | |
3286 | protocol mrt { | |
3287 | table "tab*"; | |
3288 | where source = RTS_BGP; | |
3289 | filename "/var/log/bird/%N_%F_%T.mrt"; | |
3290 | period 300; | |
3291 | } | |
3292 | </code> | |
3293 | ||
3294 | ||
371adba6 | 3295 | <sect>OSPF |
b9864aa8 | 3296 | <label id="ospf"> |
1b55b1a3 | 3297 | |
8fd12e6b | 3298 | <sect1>Introduction |
b9864aa8 | 3299 | <label id="ospf-intro"> |
8fd12e6b | 3300 | |
3ca3e999 | 3301 | <p>Open Shortest Path First (OSPF) is a quite complex interior gateway |
7935b9d2 PT |
3302 | protocol. The current IPv4 version (OSPFv2) is defined in <rfc id="2328"> and |
3303 | the current IPv6 version (OSPFv3) is defined in <rfc id="5340"> It's a link | |
3304 | state (a.k.a. shortest path first) protocol -- each router maintains a database | |
3305 | describing the autonomous system's topology. Each participating router has an | |
3306 | identical copy of the database and all routers run the same algorithm | |
3307 | calculating a shortest path tree with themselves as a root. OSPF chooses the | |
3308 | least cost path as the best path. | |
dad92c30 OZ |
3309 | |
3310 | <p>In OSPF, the autonomous system can be split to several areas in order to | |
3311 | reduce the amount of resources consumed for exchanging the routing information | |
3312 | and to protect the other areas from incorrect routing data. Topology of the area | |
3313 | is hidden to the rest of the autonomous system. | |
3314 | ||
3315 | <p>Another very important feature of OSPF is that it can keep routing information | |
3316 | from other protocols (like Static or BGP) in its link state database as external | |
3317 | routes. Each external route can be tagged by the advertising router, making it | |
3318 | possible to pass additional information between routers on the boundary of the | |
3319 | autonomous system. | |
3320 | ||
3321 | <p>OSPF quickly detects topological changes in the autonomous system (such as | |
3322 | router interface failures) and calculates new loop-free routes after a short | |
3323 | period of convergence. Only a minimal amount of routing traffic is involved. | |
8fd12e6b | 3324 | |
3ca3e999 | 3325 | <p>Each router participating in OSPF routing periodically sends Hello messages |
dad92c30 OZ |
3326 | to all its interfaces. This allows neighbors to be discovered dynamically. Then |
3327 | the neighbors exchange theirs parts of the link state database and keep it | |
3328 | identical by flooding updates. The flooding process is reliable and ensures that | |
3329 | each router detects all changes. | |
8fd12e6b OF |
3330 | |
3331 | <sect1>Configuration | |
b9864aa8 | 3332 | <label id="ospf-config"> |
8fd12e6b | 3333 | |
da3cf9ea OZ |
3334 | <p>First, the desired OSPF version can be specified by using <cf/ospf v2/ or |
3335 | <cf/ospf v3/ as a protocol type. By default, OSPFv2 is used. In the main part of | |
3336 | configuration, there can be multiple definitions of OSPF areas, each with a | |
3337 | different id. These definitions includes many other switches and multiple | |
3338 | definitions of interfaces. Definition of interface may contain many switches and | |
3339 | constant definitions and list of neighbors on nonbroadcast networks. | |
8fd12e6b | 3340 | |
cf3e3845 OZ |
3341 | <p>OSPFv2 needs one IPv4 channel. OSPFv3 needs either one IPv6 channel, or one |
3342 | IPv4 channel (<rfc id="5838">). Therefore, it is possible to use OSPFv3 for both | |
3343 | IPv4 and Pv6 routing, but it is necessary to have two protocol instances anyway. | |
3344 | If no channel is configured, appropriate channel is defined with default | |
3345 | parameters. | |
3e52d112 | 3346 | |
8fd12e6b | 3347 | <code> |
da3cf9ea | 3348 | protocol ospf [v2|v3] <name> { |
1632f1fe | 3349 | rfc1583compat <switch>; |
2d7fb19c | 3350 | rfc5838 <switch>; |
178a197a | 3351 | instance id <num>; |
f623ab98 | 3352 | stub router <switch>; |
62eee823 | 3353 | tick <num>; |
e91f6960 | 3354 | ecmp <switch> [limit <num>]; |
145368f5 | 3355 | merge external <switch>; |
6c0f85d5 OZ |
3356 | graceful restart <switch>|aware; |
3357 | graceful restart time <num>; | |
088bc8ad | 3358 | area <id> { |
2918e610 OZ |
3359 | stub; |
3360 | nssa; | |
bde872bb | 3361 | summary <switch>; |
2918e610 OZ |
3362 | default nssa <switch>; |
3363 | default cost <num>; | |
3364 | default cost2 <num>; | |
bde872bb OZ |
3365 | translator <switch>; |
3366 | translator stability <num>; | |
3367 | ||
16319aeb OF |
3368 | networks { |
3369 | <prefix>; | |
3370 | <prefix> hidden; | |
3371 | } | |
bde872bb OZ |
3372 | external { |
3373 | <prefix>; | |
3374 | <prefix> hidden; | |
3375 | <prefix> tag <num>; | |
3376 | } | |
38675202 OZ |
3377 | stubnet <prefix>; |
3378 | stubnet <prefix> { | |
3379 | hidden <switch>; | |
3380 | summary <switch>; | |
3381 | cost <num>; | |
3382 | } | |
0ec031f7 | 3383 | interface <interface pattern> [instance <num>] { |
088bc8ad | 3384 | cost <num>; |
e3bc10fd | 3385 | stub <switch>; |
088bc8ad | 3386 | hello <num>; |
a190e720 | 3387 | poll <num>; |
088bc8ad OF |
3388 | retransmit <num>; |
3389 | priority <num>; | |
3390 | wait <num>; | |
3391 | dead count <num>; | |
d8c7d9e8 | 3392 | dead <num>; |
48e5f32d | 3393 | secondary <switch>; |
94c42054 | 3394 | rx buffer [normal|large|<num>]; |
48e5f32d | 3395 | tx length <num>; |
919f5411 OZ |
3396 | type [broadcast|bcast|pointopoint|ptp| |
3397 | nonbroadcast|nbma|pointomultipoint|ptmp]; | |
70945cb6 | 3398 | link lsa suppression <switch>; |
a190e720 | 3399 | strict nonbroadcast <switch>; |
95127cbb | 3400 | real broadcast <switch>; |
8df02847 | 3401 | ptp netmask <switch>; |
e91f6960 | 3402 | check link <switch>; |
1ec52253 | 3403 | bfd <switch>; |
e91f6960 | 3404 | ecmp weight <num>; |
6ac4f87a OZ |
3405 | ttl security [<switch>; | tx only] |
3406 | tx class|dscp <num>; | |
3407 | tx priority <num>; | |
64385aee | 3408 | authentication none|simple|cryptographic; |
088bc8ad | 3409 | password "<text>"; |
b21f68b4 OZ |
3410 | password "<text>" { |
3411 | id <num>; | |
3412 | generate from "<date>"; | |
3413 | generate to "<date>"; | |
3414 | accept from "<date>"; | |
3415 | accept to "<date>"; | |
64385aee PT |
3416 | from "<date>"; |
3417 | to "<date>"; | |
3418 | algorithm ( keyed md5 | keyed sha1 | hmac sha1 | hmac sha256 | hmac sha384 | hmac sha512 ); | |
ea357b8b | 3419 | }; |
8fd12e6b | 3420 | neighbors { |
088bc8ad | 3421 | <ip>; |
a190e720 | 3422 | <ip> eligible; |
8fd12e6b OF |
3423 | }; |
3424 | }; | |
0ec031f7 | 3425 | virtual link <id> [instance <num>] { |
98ac6176 | 3426 | hello <num>; |
98ac6176 OF |
3427 | retransmit <num>; |
3428 | wait <num>; | |
3429 | dead count <num>; | |
d8c7d9e8 | 3430 | dead <num>; |
64385aee | 3431 | authentication none|simple|cryptographic; |
98ac6176 | 3432 | password "<text>"; |
64385aee PT |
3433 | password "<text>" { |
3434 | id <num>; | |
3435 | generate from "<date>"; | |
3436 | generate to "<date>"; | |
3437 | accept from "<date>"; | |
3438 | accept to "<date>"; | |
3439 | from "<date>"; | |
3440 | to "<date>"; | |
3441 | algorithm ( keyed md5 | keyed sha1 | hmac sha1 | hmac sha256 | hmac sha384 | hmac sha512 ); | |
3442 | }; | |
98ac6176 | 3443 | }; |
8fd12e6b OF |
3444 | }; |
3445 | } | |
3446 | </code> | |
3447 | ||
3448 | <descrip> | |
b9864aa8 | 3449 | <tag><label id="ospf-rfc1583compat">rfc1583compat <M>switch</M></tag> |
dad92c30 | 3450 | This option controls compatibility of routing table calculation with |
7935b9d2 | 3451 | <rfc id="1583">. Default value is no. |
e91f6960 | 3452 | |
2d7fb19c OZ |
3453 | <tag><label id="ospf-rfc5838">rfc5838 <m/switch/</tag> |
3454 | Basic OSPFv3 is limited to IPv6 unicast routing. The <rfc id="5838"> | |
3455 | extension defines support for more address families (IPv4, IPv6, both | |
3456 | unicast and multicast). The extension is enabled by default, but can be | |
3457 | disabled if necessary, as it restricts the range of available instance | |
3458 | IDs. Default value is yes. | |
3459 | ||
b9864aa8 | 3460 | <tag><label id="ospf-instance-id">instance id <m/num/</tag> |
178a197a OZ |
3461 | When multiple OSPF protocol instances are active on the same links, they |
3462 | should use different instance IDs to distinguish their packets. Although | |
3463 | it could be done on per-interface basis, it is often preferred to set | |
3464 | one instance ID to whole OSPF domain/topology (e.g., when multiple | |
3465 | instances are used to represent separate logical topologies on the same | |
2d7fb19c OZ |
3466 | physical network). This option specifies the instance ID for all |
3467 | interfaces of the OSPF instance, but can be overridden by | |
3468 | <cf/interface/ option. Default value is 0 unless OSPFv3-AF extended | |
3469 | address families are used, see <rfc id="5838"> for that case. | |
178a197a | 3470 | |
b9864aa8 | 3471 | <tag><label id="ospf-stub-router">stub router <M>switch</M></tag> |
dad92c30 OZ |
3472 | This option configures the router to be a stub router, i.e., a router |
3473 | that participates in the OSPF topology but does not allow transit | |
3474 | traffic. In OSPFv2, this is implemented by advertising maximum metric | |
178a197a | 3475 | for outgoing links. In OSPFv3, the stub router behavior is announced by |
7935b9d2 PT |
3476 | clearing the R-bit in the router LSA. See <rfc id="6987"> for details. |
3477 | Default value is no. | |
f623ab98 | 3478 | |
b9864aa8 | 3479 | <tag><label id="ospf-tick">tick <M>num</M></tag> |
dad92c30 OZ |
3480 | The routing table calculation and clean-up of areas' databases is not |
3481 | performed when a single link state change arrives. To lower the CPU | |
3482 | utilization, it's processed later at periodical intervals of <m/num/ | |
3483 | seconds. The default value is 1. | |
e91f6960 | 3484 | |
b9864aa8 | 3485 | <tag><label id="ospf-ecmp">ecmp <M>switch</M> [limit <M>number</M>]</tag> |
dad92c30 OZ |
3486 | This option specifies whether OSPF is allowed to generate ECMP |
3487 | (equal-cost multipath) routes. Such routes are used when there are | |
3488 | several directions to the destination, each with the same (computed) | |
8465dccb | 3489 | cost. This option also allows to specify a limit on maximum number of |
cf3e3845 OZ |
3490 | nexthops in one route. By default, ECMP is enabled if supported by |
3491 | Kernel. Default value of the limit is 16. | |
e91f6960 | 3492 | |
b9864aa8 | 3493 | <tag><label id="ospf-merge-external">merge external <M>switch</M></tag> |
145368f5 OZ |
3494 | This option specifies whether OSPF should merge external routes from |
3495 | different routers/LSAs for the same destination. When enabled together | |
3496 | with <cf/ecmp/, equal-cost external routes will be combined to multipath | |
3497 | routes in the same way as regular routes. When disabled, external routes | |
3498 | from different LSAs are treated as separate even if they represents the | |
3499 | same destination. Default value is no. | |
3500 | ||
6c0f85d5 OZ |
3501 | <tag><label id="ospf-graceful-restart">graceful restart <m/switch/|aware</tag> |
3502 | When an OSPF instance is restarted, neighbors break adjacencies and | |
3503 | recalculate their routing tables, which disrupts packet forwarding even | |
3504 | when the forwarding plane of the restarting router remains intact. | |
3505 | <rfc id="3623"> specifies a graceful restart mechanism to alleviate this | |
3506 | issue. For OSPF graceful restart, restarting router originates | |
3507 | Grace-LSAs, announcing intent to do graceful restart. Neighbors | |
3508 | receiving these LSAs enter helper mode, in which they ignore breakdown | |
3509 | of adjacencies, behave as if nothing is happening and keep old routes. | |
3510 | When adjacencies are reestablished, the restarting router flushes | |
3511 | Grace-LSAs and graceful restart is ended. | |
3512 | ||
3513 | This option controls the graceful restart mechanism. It has three | |
3514 | states: Disabled, when no support is provided. Aware, when graceful | |
3515 | restart helper mode is supported, but no local graceful restart is | |
3516 | allowed (i.e. helper-only role). Enabled, when the full graceful restart | |
3517 | support is provided (i.e. both restarting and helper role). Note that | |
3518 | proper support for local graceful restart requires also configuration of | |
3519 | other protocols. Default: aware. | |
3520 | ||
3521 | <tag><label id="ospf-graceful-restart-time">graceful restart time <m/num/</tag> | |
3522 | The restart time is announced in the Grace-LSA and specifies how long | |
3523 | neighbors should wait for proper end of the graceful restart before | |
3524 | exiting helper mode prematurely. Default: 120 seconds. | |
3525 | ||
b9864aa8 | 3526 | <tag><label id="ospf-area">area <M>id</M></tag> |
dad92c30 OZ |
3527 | This defines an OSPF area with given area ID (an integer or an IPv4 |
3528 | address, similarly to a router ID). The most important area is the | |
3529 | backbone (ID 0) to which every other area must be connected. | |
8fd12e6b | 3530 | |
b9864aa8 | 3531 | <tag><label id="ospf-stub">stub</tag> |
dad92c30 OZ |
3532 | This option configures the area to be a stub area. External routes are |
3533 | not flooded into stub areas. Also summary LSAs can be limited in stub | |
3534 | areas (see option <cf/summary/). By default, the area is not a stub | |
3535 | area. | |
bde872bb | 3536 | |
b9864aa8 | 3537 | <tag><label id="ospf-nssa">nssa</tag> |
dad92c30 OZ |
3538 | This option configures the area to be a NSSA (Not-So-Stubby Area). NSSA |
3539 | is a variant of a stub area which allows a limited way of external route | |
3540 | propagation. Global external routes are not propagated into a NSSA, but | |
3541 | an external route can be imported into NSSA as a (area-wide) NSSA-LSA | |
3542 | (and possibly translated and/or aggregated on area boundary). By | |
3543 | default, the area is not NSSA. | |
bde872bb | 3544 | |
b9864aa8 | 3545 | <tag><label id="ospf-summary">summary <M>switch</M></tag> |
dad92c30 OZ |
3546 | This option controls propagation of summary LSAs into stub or NSSA |
3547 | areas. If enabled, summary LSAs are propagated as usual, otherwise just | |
3548 | the default summary route (0.0.0.0/0) is propagated (this is sometimes | |
3549 | called totally stubby area). If a stub area has more area boundary | |
3550 | routers, propagating summary LSAs could lead to more efficient routing | |
3551 | at the cost of larger link state database. Default value is no. | |
bde872bb | 3552 | |
b9864aa8 | 3553 | <tag><label id="ospf-default-nssa">default nssa <M>switch</M></tag> |
dad92c30 OZ |
3554 | When <cf/summary/ option is enabled, default summary route is no longer |
3555 | propagated to the NSSA. In that case, this option allows to originate | |
3556 | default route as NSSA-LSA to the NSSA. Default value is no. | |
2918e610 | 3557 | |
b9864aa8 | 3558 | <tag><label id="ospf-default-cost">default cost <M>num</M></tag> |
dad92c30 OZ |
3559 | This option controls the cost of a default route propagated to stub and |
3560 | NSSA areas. Default value is 1000. | |
bde872bb | 3561 | |
b9864aa8 | 3562 | <tag><label id="ospf-default-cost2">default cost2 <M>num</M></tag> |
dad92c30 OZ |
3563 | When a default route is originated as NSSA-LSA, its cost can use either |
3564 | type 1 or type 2 metric. This option allows to specify the cost of a | |
3565 | default route in type 2 metric. By default, type 1 metric (option | |
3566 | <cf/default cost/) is used. | |
2918e610 | 3567 | |
b9864aa8 | 3568 | <tag><label id="ospf-translator">translator <M>switch</M></tag> |
dad92c30 OZ |
3569 | This option controls translation of NSSA-LSAs into external LSAs. By |
3570 | default, one translator per NSSA is automatically elected from area | |
3571 | boundary routers. If enabled, this area boundary router would | |
3572 | unconditionally translate all NSSA-LSAs regardless of translator | |
3573 | election. Default value is no. | |
bde872bb | 3574 | |
b9864aa8 | 3575 | <tag><label id="ospf-translator-stability">translator stability <M>num</M></tag> |
dad92c30 OZ |
3576 | This option controls the translator stability interval (in seconds). |
3577 | When the new translator is elected, the old one keeps translating until | |
3578 | the interval is over. Default value is 40. | |
8fd12e6b | 3579 | |
b9864aa8 | 3580 | <tag><label id="ospf-networks">networks { <m/set/ }</tag> |
dad92c30 OZ |
3581 | Definition of area IP ranges. This is used in summary LSA origination. |
3582 | Hidden networks are not propagated into other areas. | |
16319aeb | 3583 | |
b9864aa8 | 3584 | <tag><label id="ospf-external">external { <m/set/ }</tag> |
dad92c30 OZ |
3585 | Definition of external area IP ranges for NSSAs. This is used for |
3586 | NSSA-LSA translation. Hidden networks are not translated into external | |
3587 | LSAs. Networks can have configured route tag. | |
bde872bb | 3588 | |
b9864aa8 | 3589 | <tag><label id="ospf-stubnet">stubnet <m/prefix/ { <m/options/ }</tag> |
dad92c30 OZ |
3590 | Stub networks are networks that are not transit networks between OSPF |
3591 | routers. They are also propagated through an OSPF area as a part of a | |
3592 | link state database. By default, BIRD generates a stub network record | |
3593 | for each primary network address on each OSPF interface that does not | |
3594 | have any OSPF neighbors, and also for each non-primary network address | |
3595 | on each OSPF interface. This option allows to alter a set of stub | |
3596 | networks propagated by this router. | |
3597 | ||
3598 | Each instance of this option adds a stub network with given network | |
3599 | prefix to the set of propagated stub network, unless option <cf/hidden/ | |
3600 | is used. It also suppresses default stub networks for given network | |
3601 | prefix. When option <cf/summary/ is used, also default stub networks | |
3602 | that are subnetworks of given stub network are suppressed. This might be | |
3603 | used, for example, to aggregate generated stub networks. | |
178a197a | 3604 | |
b9864aa8 | 3605 | <tag><label id="ospf-iface">interface <M>pattern</M> [instance <m/num/]</tag> |
dad92c30 | 3606 | Defines that the specified interfaces belong to the area being defined. |
b9864aa8 | 3607 | See <ref id="proto-iface" name="interface"> common option for detailed |
d7c06285 | 3608 | description. In OSPFv2, extended interface clauses are used, because |
178a197a OZ |
3609 | each network prefix is handled as a separate virtual interface. |
3610 | ||
3611 | You can specify alternative instance ID for the interface definition, | |
3612 | therefore it is possible to have several instances of that interface | |
7935b9d2 PT |
3613 | with different options or even in different areas. For OSPFv2, instance |
3614 | ID support is an extension (<rfc id="6549">) and is supposed to be set | |
3615 | per-protocol. For OSPFv3, it is an integral feature. | |
0ec031f7 | 3616 | |
b9864aa8 | 3617 | <tag><label id="ospf-virtual-link">virtual link <M>id</M> [instance <m/num/]</tag> |
dad92c30 OZ |
3618 | Virtual link to router with the router id. Virtual link acts as a |
3619 | point-to-point interface belonging to backbone. The actual area is used | |
178a197a OZ |
3620 | as a transport area. This item cannot be in the backbone. Like with |
3621 | <cf/interface/ option, you could also use several virtual links to one | |
3622 | destination with different instance IDs. | |
98ac6176 | 3623 | |
b9864aa8 | 3624 | <tag><label id="ospf-cost">cost <M>num</M></tag> |
dad92c30 | 3625 | Specifies output cost (metric) of an interface. Default value is 10. |
8fd12e6b | 3626 | |
b9864aa8 | 3627 | <tag><label id="ospf-stub-iface">stub <M>switch</M></tag> |
dad92c30 OZ |
3628 | If set to interface it does not listen to any packet and does not send |
3629 | any hello. Default value is no. | |
e3bc10fd | 3630 | |
b9864aa8 | 3631 | <tag><label id="ospf-hello">hello <M>num</M></tag> |
dad92c30 OZ |
3632 | Specifies interval in seconds between sending of Hello messages. Beware, |
3633 | all routers on the same network need to have the same hello interval. | |
3634 | Default value is 10. | |
8fd12e6b | 3635 | |
b9864aa8 | 3636 | <tag><label id="ospf-poll">poll <M>num</M></tag> |
dad92c30 OZ |
3637 | Specifies interval in seconds between sending of Hello messages for some |
3638 | neighbors on NBMA network. Default value is 20. | |
a190e720 | 3639 | |
b9864aa8 | 3640 | <tag><label id="ospf-retransmit">retransmit <M>num</M></tag> |
dad92c30 OZ |
3641 | Specifies interval in seconds between retransmissions of unacknowledged |
3642 | updates. Default value is 5. | |
8fd12e6b | 3643 | |
ee95f281 OZ |
3644 | <tag><label id="ospf-transmit-delay">transmit delay <M>num</M></tag> |
3645 | Specifies estimated transmission delay of link state updates send over | |
3646 | the interface. The value is added to LSA age of LSAs propagated through | |
3647 | it. Default value is 1. | |
3648 | ||
b9864aa8 | 3649 | <tag><label id="ospf-priority">priority <M>num</M></tag> |
0a505706 OZ |
3650 | On every multiple access network (e.g., the Ethernet) Designated Router |
3651 | and Backup Designated router are elected. These routers have some special | |
dad92c30 OZ |
3652 | functions in the flooding process. Higher priority increases preferences |
3653 | in this election. Routers with priority 0 are not eligible. Default | |
3654 | value is 1. | |
8fd12e6b | 3655 | |
b9864aa8 | 3656 | <tag><label id="ospf-wait">wait <M>num</M></tag> |
dad92c30 | 3657 | After start, router waits for the specified number of seconds between |
178a197a OZ |
3658 | starting election and building adjacency. Default value is 4*<m/hello/. |
3659 | ||
b9864aa8 | 3660 | <tag><label id="ospf-dead-count">dead count <M>num</M></tag> |
dad92c30 OZ |
3661 | When the router does not receive any messages from a neighbor in |
3662 | <m/dead count/*<m/hello/ seconds, it will consider the neighbor down. | |
8fd12e6b | 3663 | |
b9864aa8 | 3664 | <tag><label id="ospf-dead">dead <M>num</M></tag> |
dad92c30 OZ |
3665 | When the router does not receive any messages from a neighbor in |
3666 | <m/dead/ seconds, it will consider the neighbor down. If both directives | |
fff7498d | 3667 | <cf/dead count/ and <cf/dead/ are used, <cf/dead/ has precedence. |
48e5f32d | 3668 | |
b9864aa8 | 3669 | <tag><label id="ospf-rx-buffer">rx buffer <M>num</M></tag> |
48e5f32d OZ |
3670 | This option allows to specify the size of buffers used for packet |
3671 | processing. The buffer size should be bigger than maximal size of any | |
3672 | packets. By default, buffers are dynamically resized as needed, but a | |
3673 | fixed value could be specified. Value <cf/large/ means maximal allowed | |
3674 | packet size - 65535. | |
3675 | ||
b9864aa8 | 3676 | <tag><label id="ospf-tx-length">tx length <M>num</M></tag> |
48e5f32d OZ |
3677 | Transmitted OSPF messages that contain large amount of information are |
3678 | segmented to separate OSPF packets to avoid IP fragmentation. This | |
3679 | option specifies the soft ceiling for the length of generated OSPF | |
3680 | packets. Default value is the MTU of the network interface. Note that | |
3681 | larger OSPF packets may still be generated if underlying OSPF messages | |
3682 | cannot be splitted (e.g. when one large LSA is propagated). | |
94c42054 | 3683 | |
b9864aa8 | 3684 | <tag><label id="ospf-type-bcast">type broadcast|bcast</tag> |
dad92c30 OZ |
3685 | BIRD detects a type of a connected network automatically, but sometimes |
3686 | it's convenient to force use of a different type manually. On broadcast | |
3687 | networks (like ethernet), flooding and Hello messages are sent using | |
3688 | multicasts (a single packet for all the neighbors). A designated router | |
3689 | is elected and it is responsible for synchronizing the link-state | |
3690 | databases and originating network LSAs. This network type cannot be used | |
3691 | on physically NBMA networks and on unnumbered networks (networks without | |
3692 | proper IP prefix). | |
919f5411 | 3693 | |
b9864aa8 | 3694 | <tag><label id="ospf-type-ptp">type pointopoint|ptp</tag> |
dad92c30 OZ |
3695 | Point-to-point networks connect just 2 routers together. No election is |
3696 | performed and no network LSA is originated, which makes it simpler and | |
3697 | faster to establish. This network type is useful not only for physically | |
3698 | PtP ifaces (like PPP or tunnels), but also for broadcast networks used | |
3699 | as PtP links. This network type cannot be used on physically NBMA | |
3700 | networks. | |
919f5411 | 3701 | |
b9864aa8 | 3702 | <tag><label id="ospf-type-nbma">type nonbroadcast|nbma</tag> |
dad92c30 OZ |
3703 | On NBMA networks, the packets are sent to each neighbor separately |
3704 | because of lack of multicast capabilities. Like on broadcast networks, | |
3705 | a designated router is elected, which plays a central role in propagation | |
3706 | of LSAs. This network type cannot be used on unnumbered networks. | |
919f5411 | 3707 | |
b9864aa8 | 3708 | <tag><label id="ospf-type-ptmp">type pointomultipoint|ptmp</tag> |
dad92c30 OZ |
3709 | This is another network type designed to handle NBMA networks. In this |
3710 | case the NBMA network is treated as a collection of PtP links. This is | |
3711 | useful if not every pair of routers on the NBMA network has direct | |
3712 | communication, or if the NBMA network is used as an (possibly | |
3713 | unnumbered) PtP link. | |
8fd12e6b | 3714 | |
b9864aa8 | 3715 | <tag><label id="ospf-link-lsa-suppression">link lsa suppression <m/switch/</tag> |
70945cb6 OZ |
3716 | In OSPFv3, link LSAs are generated for each link, announcing link-local |
3717 | IPv6 address of the router to its local neighbors. These are useless on | |
3718 | PtP or PtMP networks and this option allows to suppress the link LSA | |
3719 | origination for such interfaces. The option is ignored on other than PtP | |
3720 | or PtMP interfaces. Default value is no. | |
3721 | ||
b9864aa8 | 3722 | <tag><label id="ospf-strict-nonbroadcast">strict nonbroadcast <m/switch/</tag> |
dad92c30 | 3723 | If set, don't send hello to any undefined neighbor. This switch is |
70945cb6 | 3724 | ignored on other than NBMA or PtMP interfaces. Default value is no. |
8fd12e6b | 3725 | |
b9864aa8 | 3726 | <tag><label id="ospf-real-broadcast">real broadcast <m/switch/</tag> |
dad92c30 OZ |
3727 | In <cf/type broadcast/ or <cf/type ptp/ network configuration, OSPF |
3728 | packets are sent as IP multicast packets. This option changes the | |
3729 | behavior to using old-fashioned IP broadcast packets. This may be useful | |
3730 | as a workaround if IP multicast for some reason does not work or does | |
3731 | not work reliably. This is a non-standard option and probably is not | |
3732 | interoperable with other OSPF implementations. Default value is no. | |
95127cbb | 3733 | |
b9864aa8 | 3734 | <tag><label id="ospf-ptp-netmask">ptp netmask <m/switch/</tag> |
dad92c30 OZ |
3735 | In <cf/type ptp/ network configurations, OSPFv2 implementations should |
3736 | ignore received netmask field in hello packets and should send hello | |
3737 | packets with zero netmask field on unnumbered PtP links. But some OSPFv2 | |
3738 | implementations perform netmask checking even for PtP links. This option | |
3739 | specifies whether real netmask will be used in hello packets on <cf/type | |
3740 | ptp/ interfaces. You should ignore this option unless you meet some | |
3741 | compatibility problems related to this issue. Default value is no for | |
3742 | unnumbered PtP links, yes otherwise. | |
8df02847 | 3743 | |
b9864aa8 | 3744 | <tag><label id="ospf-check-link">check link <M>switch</M></tag> |
dad92c30 OZ |
3745 | If set, a hardware link state (reported by OS) is taken into consideration. |
3746 | When a link disappears (e.g. an ethernet cable is unplugged), neighbors | |
3747 | are immediately considered unreachable and only the address of the iface | |
3748 | (instead of whole network prefix) is propagated. It is possible that | |
3749 | some hardware drivers or platforms do not implement this feature. | |
cf3e3845 | 3750 | Default value is yes. |
e91f6960 | 3751 | |
b9864aa8 | 3752 | <tag><label id="ospf-bfd">bfd <M>switch</M></tag> |
1ec52253 OZ |
3753 | OSPF could use BFD protocol as an advisory mechanism for neighbor |
3754 | liveness and failure detection. If enabled, BIRD setups a BFD session | |
3755 | for each OSPF neighbor and tracks its liveness by it. This has an | |
3756 | advantage of an order of magnitude lower detection times in case of | |
3757 | failure. Note that BFD protocol also has to be configured, see | |
b9864aa8 | 3758 | <ref id="bfd" name="BFD"> section for details. Default value is no. |
1ec52253 | 3759 | |
b9864aa8 | 3760 | <tag><label id="ospf-ttl-security">ttl security [<m/switch/ | tx only]</tag> |
dad92c30 OZ |
3761 | TTL security is a feature that protects routing protocols from remote |
3762 | spoofed packets by using TTL 255 instead of TTL 1 for protocol packets | |
3763 | destined to neighbors. Because TTL is decremented when packets are | |
3764 | forwarded, it is non-trivial to spoof packets with TTL 255 from remote | |
3765 | locations. Note that this option would interfere with OSPF virtual | |
3766 | links. | |
3767 | ||
3768 | If this option is enabled, the router will send OSPF packets with TTL | |
3769 | 255 and drop received packets with TTL less than 255. If this option si | |
3770 | set to <cf/tx only/, TTL 255 is used for sent packets, but is not | |
3771 | checked for received packets. Default value is no. | |
6ac4f87a | 3772 | |
b9864aa8 | 3773 | <tag><label id="ospf-tx-class">tx class|dscp|priority <m/num/</tag> |
dad92c30 | 3774 | These options specify the ToS/DiffServ/Traffic class/Priority of the |
b9864aa8 | 3775 | outgoing OSPF packets. See <ref id="proto-tx-class" name="tx class"> common |
dad92c30 | 3776 | option for detailed description. |
ef4a50be | 3777 | |
b9864aa8 | 3778 | <tag><label id="ospf-ecmp-weight">ecmp weight <M>num</M></tag> |
dad92c30 OZ |
3779 | When ECMP (multipath) routes are allowed, this value specifies a |
3780 | relative weight used for nexthops going through the iface. Allowed | |
3781 | values are 1-256. Default value is 1. | |
391931d4 | 3782 | |
b9864aa8 | 3783 | <tag><label id="ospf-auth-none">authentication none</tag> |
dad92c30 | 3784 | No passwords are sent in OSPF packets. This is the default value. |
8fd12e6b | 3785 | |
b9864aa8 | 3786 | <tag><label id="ospf-auth-simple">authentication simple</tag> |
dad92c30 OZ |
3787 | Every packet carries 8 bytes of password. Received packets lacking this |
3788 | password are ignored. This authentication mechanism is very weak. | |
64385aee | 3789 | This option is not available in OSPFv3. |
8fd12e6b | 3790 | |
b9864aa8 | 3791 | <tag><label id="ospf-auth-cryptographic">authentication cryptographic</tag> |
64385aee PT |
3792 | An authentication code is appended to every packet. The specific |
3793 | cryptographic algorithm is selected by option <cf/algorithm/ for each | |
3794 | key. The default cryptographic algorithm for OSPFv2 keys is Keyed-MD5 | |
3795 | and for OSPFv3 keys is HMAC-SHA-256. Passwords are not sent open via | |
3796 | network, so this mechanism is quite secure. Packets can still be read by | |
3797 | an attacker. | |
ea357b8b | 3798 | |
b9864aa8 | 3799 | <tag><label id="ospf-pass">password "<M>text</M>"</tag> |
64385aee | 3800 | Specifies a password used for authentication. See |
b9864aa8 | 3801 | <ref id="proto-pass" name="password"> common option for detailed |
dad92c30 | 3802 | description. |
8fd12e6b | 3803 | |
b9864aa8 | 3804 | <tag><label id="ospf-neighbors">neighbors { <m/set/ } </tag> |
dad92c30 OZ |
3805 | A set of neighbors to which Hello messages on NBMA or PtMP networks are |
3806 | to be sent. For NBMA networks, some of them could be marked as eligible. | |
3807 | In OSPFv3, link-local addresses should be used, using global ones is | |
3808 | possible, but it is nonstandard and might be problematic. And definitely, | |
3809 | link-local and global addresses should not be mixed. | |
8fd12e6b OF |
3810 | </descrip> |
3811 | ||
3812 | <sect1>Attributes | |
b9864aa8 | 3813 | <label id="ospf-attr"> |
8fd12e6b | 3814 | |
c27b2449 | 3815 | <p>OSPF defines four route attributes. Each internal route has a <cf/metric/. |
8fd12e6b | 3816 | |
dad92c30 OZ |
3817 | <p>Metric is ranging from 1 to infinity (65535). External routes use |
3818 | <cf/metric type 1/ or <cf/metric type 2/. A <cf/metric of type 1/ is comparable | |
3819 | with internal <cf/metric/, a <cf/metric of type 2/ is always longer than any | |
3820 | <cf/metric of type 1/ or any <cf/internal metric/. <cf/Internal metric/ or | |
3821 | <cf/metric of type 1/ is stored in attribute <cf/ospf_metric1/, <cf/metric type | |
feae132e OZ |
3822 | 2/ is stored in attribute <cf/ospf_metric2/. |
3823 | ||
3824 | When both metrics are specified then <cf/metric of type 2/ is used. This is | |
3825 | relevant e.g. when a type 2 external route is propagated from one OSPF domain to | |
3826 | another and <cf/ospf_metric1/ is an internal distance to the original ASBR, | |
3827 | while <cf/ospf_metric2/ stores the type 2 metric. Note that in such cases if | |
3828 | <cf/ospf_metric1/ is non-zero then <cf/ospf_metric2/ is increased by one to | |
3829 | ensure monotonicity of metric, as internal distance is reset to zero when an | |
3830 | external route is announced. | |
dad92c30 OZ |
3831 | |
3832 | <p>Each external route can also carry attribute <cf/ospf_tag/ which is a 32-bit | |
3833 | integer which is used when exporting routes to other protocols; otherwise, it | |
3834 | doesn't affect routing inside the OSPF domain at all. The fourth attribute | |
3835 | <cf/ospf_router_id/ is a router ID of the router advertising that route / | |
3836 | network. This attribute is read-only. Default is <cf/ospf_metric2 = 10000/ and | |
3837 | <cf/ospf_tag = 0/. | |
8fd12e6b | 3838 | |
dad92c30 | 3839 | <sect1>Example |
b9864aa8 | 3840 | <label id="ospf-exam"> |
8fd12e6b | 3841 | |
9637c7c0 | 3842 | <p><code> |
8fd12e6b | 3843 | protocol ospf MyOSPF { |
3e52d112 JMM |
3844 | ipv4 { |
3845 | export filter { | |
3846 | if source = RTS_BGP then { | |
3847 | ospf_metric1 = 100; | |
3848 | accept; | |
3849 | } | |
3850 | reject; | |
3851 | }; | |
f434d191 | 3852 | }; |
8fd12e6b | 3853 | area 0.0.0.0 { |
8fd12e6b OF |
3854 | interface "eth*" { |
3855 | cost 11; | |
3856 | hello 15; | |
3857 | priority 100; | |
3858 | retransmit 7; | |
3859 | authentication simple; | |
3860 | password "aaa"; | |
3861 | }; | |
3862 | interface "ppp*" { | |
3863 | cost 100; | |
3b16080c | 3864 | authentication cryptographic; |
f434d191 OZ |
3865 | password "abc" { |
3866 | id 1; | |
3867 | generate to "22-04-2003 11:00:06"; | |
3868 | accept from "17-01-2001 12:01:05"; | |
64385aee | 3869 | algorithm hmac sha384; |
f434d191 OZ |
3870 | }; |
3871 | password "def" { | |
3872 | id 2; | |
3873 | generate to "22-07-2005 17:03:21"; | |
3874 | accept from "22-02-2001 11:34:06"; | |
64385aee | 3875 | algorithm hmac sha512; |
3b16080c | 3876 | }; |
8fd12e6b | 3877 | }; |
e3bc10fd OF |
3878 | interface "arc0" { |
3879 | cost 10; | |
3880 | stub yes; | |
3881 | }; | |
3b16080c | 3882 | interface "arc1"; |
8fd12e6b OF |
3883 | }; |
3884 | area 120 { | |
3885 | stub yes; | |
98ac6176 OF |
3886 | networks { |
3887 | 172.16.1.0/24; | |
3888 | 172.16.2.0/24 hidden; | |
3889 | } | |
8fd12e6b OF |
3890 | interface "-arc0" , "arc*" { |
3891 | type nonbroadcast; | |
3892 | authentication none; | |
e3bc10fd | 3893 | strict nonbroadcast yes; |
a190e720 OF |
3894 | wait 120; |
3895 | poll 40; | |
3896 | dead count 8; | |
8fd12e6b | 3897 | neighbors { |
a190e720 | 3898 | 192.168.120.1 eligible; |
8fd12e6b OF |
3899 | 192.168.120.2; |
3900 | 192.168.120.10; | |
3901 | }; | |
3902 | }; | |
3903 | }; | |
3904 | } | |
3905 | </code> | |
3906 | ||
82b74253 MM |
3907 | <sect>Perf |
3908 | <label id="perf"> | |
3909 | ||
3910 | <sect1>Introduction | |
3911 | <label id="perf-intro"> | |
3912 | ||
3913 | <p>The Perf protocol is a generator of fake routes together with a time measurement | |
3914 | framework. Its purpose is to check BIRD performance and to benchmark filters. | |
3915 | ||
3916 | <p>Import mode of this protocol runs in several steps. In each step, it generates 2^x routes, | |
3917 | imports them into the appropriate table and withdraws them. The exponent x is configurable. | |
3918 | It runs the benchmark several times for the same x, then it increases x by one | |
3919 | until it gets too high, then it stops. | |
3920 | ||
3921 | <p>Export mode of this protocol repeats route refresh from table and measures how long it takes. | |
3922 | ||
3923 | <p>Output data is logged on info level. There is a Perl script <cf>proto/perf/parse.pl</cf> | |
3924 | which may be handy to parse the data and draw some plots. | |
3925 | ||
3926 | <p>Implementation of this protocol is experimental. Use with caution and do not keep | |
3927 | any instance of Perf in production configs for long time. The config interface is also unstable | |
3928 | and may change in future versions without warning. | |
3929 | ||
3930 | <sect1>Configuration | |
3931 | <label id="perf-config"> | |
3932 | ||
3933 | <p><descrip> | |
3934 | <tag><label id="perf-mode">mode import|export</tag> | |
3935 | Set perf mode. Default: import | |
3936 | ||
3937 | <tag><label id="perf-repeat">repeat <m/number/</tag> | |
3938 | Run this amount of iterations of the benchmark for every amount step. Default: 4 | |
3939 | ||
3940 | <tag><label id="perf-from">exp from <m/number/</tag> | |
3941 | Begin benchmarking on this exponent for number of generated routes in one step. | |
3942 | Default: 10 | |
3943 | ||
3944 | <tag><label id="perf-to">exp to <m/number/</tag> | |
3945 | Stop benchmarking on this exponent. Default: 20 | |
3946 | ||
3947 | <tag><label id="perf-threshold-min">threshold min <m/time/</tag> | |
3948 | If a run for the given exponent took less than this time for route import, | |
3949 | increase the exponent immediately. Default: 1 ms | |
3950 | ||
3951 | <tag><label id="perf-threshold-max">threshold max <m/time/</tag> | |
3952 | If every run for the given exponent took at least this time for route import, | |
3953 | stop benchmarking. Default: 500 ms | |
3954 | </descrip> | |
dad92c30 | 3955 | |
371adba6 | 3956 | <sect>Pipe |
b9864aa8 | 3957 | <label id="pipe"> |
1b55b1a3 | 3958 | |
371adba6 | 3959 | <sect1>Introduction |
b9864aa8 | 3960 | <label id="pipe-intro"> |
a2a3ced8 | 3961 | |
dad92c30 OZ |
3962 | <p>The Pipe protocol serves as a link between two routing tables, allowing |
3963 | routes to be passed from a table declared as primary (i.e., the one the pipe is | |
3964 | connected to using the <cf/table/ configuration keyword) to the secondary one | |
3965 | (declared using <cf/peer table/) and vice versa, depending on what's allowed by | |
3966 | the filters. Export filters control export of routes from the primary table to | |
3e52d112 JMM |
3967 | the secondary one, import filters control the opposite direction. Both tables |
3968 | must be of the same nettype. | |
dad92c30 | 3969 | |
765f400f OZ |
3970 | <p>The Pipe protocol retransmits all routes from one table to the other table, |
3971 | retaining their original source and attributes. If import and export filters | |
3972 | are set to accept, then both tables would have the same content. | |
f98e2915 | 3973 | |
dad92c30 OZ |
3974 | <p>The primary use of multiple routing tables and the Pipe protocol is for |
3975 | policy routing, where handling of a single packet doesn't depend only on its | |
3976 | destination address, but also on its source address, source interface, protocol | |
3977 | type and other similar parameters. In many systems (Linux being a good example), | |
3978 | the kernel allows to enforce routing policies by defining routing rules which | |
3979 | choose one of several routing tables to be used for a packet according to its | |
3980 | parameters. Setting of these rules is outside the scope of BIRD's work (on | |
3981 | Linux, you can use the <tt/ip/ command), but you can create several routing | |
3982 | tables in BIRD, connect them to the kernel ones, use filters to control which | |
3983 | routes appear in which tables and also you can employ the Pipe protocol for | |
3984 | exporting a selected subset of one table to another one. | |
a2a3ced8 | 3985 | |
371adba6 | 3986 | <sect1>Configuration |
b9864aa8 | 3987 | <label id="pipe-config"> |
a2a3ced8 | 3988 | |
cf3e3845 OZ |
3989 | <p>Essentially, the Pipe protocol is just a channel connected to a table on both |
3990 | sides. Therefore, the configuration block for <cf/protocol pipe/ shall directly | |
3991 | include standard channel config options; see the example below. | |
3e52d112 | 3992 | |
a2a3ced8 | 3993 | <p><descrip> |
b9864aa8 | 3994 | <tag><label id="pipe-peer-table">peer table <m/table/</tag> |
dad92c30 OZ |
3995 | Defines secondary routing table to connect to. The primary one is |
3996 | selected by the <cf/table/ keyword. | |
a2a3ced8 MM |
3997 | </descrip> |
3998 | ||
371adba6 | 3999 | <sect1>Attributes |
b9864aa8 | 4000 | <label id="pipe-attr"> |
a2a3ced8 MM |
4001 | |
4002 | <p>The Pipe protocol doesn't define any route attributes. | |
4003 | ||
371adba6 | 4004 | <sect1>Example |
b9864aa8 | 4005 | <label id="pipe-exam"> |
a2a3ced8 | 4006 | |
dad92c30 OZ |
4007 | <p>Let's consider a router which serves as a boundary router of two different |
4008 | autonomous systems, each of them connected to a subset of interfaces of the | |
4009 | router, having its own exterior connectivity and wishing to use the other AS as | |
4010 | a backup connectivity in case of outage of its own exterior line. | |
4011 | ||
4012 | <p>Probably the simplest solution to this situation is to use two routing tables | |
4013 | (we'll call them <cf/as1/ and <cf/as2/) and set up kernel routing rules, so that | |
4014 | packets having arrived from interfaces belonging to the first AS will be routed | |
4015 | according to <cf/as1/ and similarly for the second AS. Thus we have split our | |
4016 | router to two logical routers, each one acting on its own routing table, having | |
4017 | its own routing protocols on its own interfaces. In order to use the other AS's | |
4018 | routes for backup purposes, we can pass the routes between the tables through a | |
4019 | Pipe protocol while decreasing their preferences and correcting their BGP paths | |
4020 | to reflect the AS boundary crossing. | |
a2a3ced8 MM |
4021 | |
4022 | <code> | |
cf3e3845 OZ |
4023 | ipv4 table as1; # Define the tables |
4024 | ipv4 table as2; | |
a2a3ced8 MM |
4025 | |
4026 | protocol kernel kern1 { # Synchronize them with the kernel | |
cf3e3845 | 4027 | ipv4 { table as1; export all; }; |
a2a3ced8 MM |
4028 | kernel table 1; |
4029 | } | |
4030 | ||
4031 | protocol kernel kern2 { | |
cf3e3845 | 4032 | ipv4 { table as2; export all; }; |
a2a3ced8 MM |
4033 | kernel table 2; |
4034 | } | |
4035 | ||
4036 | protocol bgp bgp1 { # The outside connections | |
3831b619 | 4037 | ipv4 { table as1; import all; export all; }; |
a2a3ced8 MM |
4038 | local as 1; |
4039 | neighbor 192.168.0.1 as 1001; | |
a2a3ced8 MM |
4040 | } |
4041 | ||
4042 | protocol bgp bgp2 { | |
3831b619 | 4043 | ipv4 { table as2; import all; export all; }; |
a2a3ced8 MM |
4044 | local as 2; |
4045 | neighbor 10.0.0.1 as 1002; | |
a2a3ced8 MM |
4046 | } |
4047 | ||
4048 | protocol pipe { # The Pipe | |
4049 | table as1; | |
4050 | peer table as2; | |
4051 | export filter { | |
4052 | if net ~ [ 1.0.0.0/8+] then { # Only AS1 networks | |
4053 | if preference>10 then preference = preference-10; | |
4054 | if source=RTS_BGP then bgp_path.prepend(1); | |
4055 | accept; | |
4056 | } | |
4057 | reject; | |
4058 | }; | |
4059 | import filter { | |
4060 | if net ~ [ 2.0.0.0/8+] then { # Only AS2 networks | |
4061 | if preference>10 then preference = preference-10; | |
4062 | if source=RTS_BGP then bgp_path.prepend(2); | |
4063 | accept; | |
4064 | } | |
4065 | reject; | |
4066 | }; | |
4067 | } | |
4068 | </code> | |
4069 | ||
dad92c30 | 4070 | |
6bcef225 | 4071 | <sect>RAdv |
b9864aa8 | 4072 | <label id="radv"> |
6bcef225 OZ |
4073 | |
4074 | <sect1>Introduction | |
b9864aa8 | 4075 | <label id="radv-intro"> |
6bcef225 | 4076 | |
dad92c30 OZ |
4077 | <p>The RAdv protocol is an implementation of Router Advertisements, which are |
4078 | used in the IPv6 stateless autoconfiguration. IPv6 routers send (in irregular | |
4079 | time intervals or as an answer to a request) advertisement packets to connected | |
4080 | networks. These packets contain basic information about a local network (e.g. a | |
4081 | list of network prefixes), which allows network hosts to autoconfigure network | |
4082 | addresses and choose a default route. BIRD implements router behavior as defined | |
18352188 MV |
4083 | in <rfc id="4861">, router preferences and specific routes (<rfc id="4191">), |
4084 | and DNS extensions (<rfc id="6106">). | |
6bcef225 | 4085 | |
cf3e3845 | 4086 | <p>The RAdv protocols supports just IPv6 channel. |
3e52d112 | 4087 | |
6bcef225 | 4088 | <sect1>Configuration |
b9864aa8 | 4089 | <label id="radv-config"> |
6bcef225 | 4090 | |
dad92c30 OZ |
4091 | <p>There are several classes of definitions in RAdv configuration -- interface |
4092 | definitions, prefix definitions and DNS definitions: | |
6bcef225 OZ |
4093 | |
4094 | <descrip> | |
9df52a98 | 4095 | <tag><label id="radv-iface">interface <m/pattern/ [, <m/.../] { <m/options/ }</tag> |
6bcef225 OZ |
4096 | Interface definitions specify a set of interfaces on which the |
4097 | protocol is activated and contain interface specific options. | |
b9864aa8 | 4098 | See <ref id="proto-iface" name="interface"> common options for |
6bcef225 OZ |
4099 | detailed description. |
4100 | ||
b9864aa8 | 4101 | <tag><label id="radv-prefix">prefix <m/prefix/ { <m/options/ }</tag> |
dad92c30 OZ |
4102 | Prefix definitions allow to modify a list of advertised prefixes. By |
4103 | default, the advertised prefixes are the same as the network prefixes | |
4104 | assigned to the interface. For each network prefix, the matching prefix | |
4105 | definition is found and its options are used. If no matching prefix | |
4106 | definition is found, the prefix is used with default options. | |
4107 | ||
4108 | Prefix definitions can be either global or interface-specific. The | |
4109 | second ones are part of interface options. The prefix definition | |
4110 | matching is done in the first-match style, when interface-specific | |
4111 | definitions are processed before global definitions. As expected, the | |
4112 | prefix definition is matching if the network prefix is a subnet of the | |
4113 | prefix in prefix definition. | |
0e224d59 | 4114 | |
b9864aa8 | 4115 | <tag><label id="radv-rdnss">rdnss { <m/options/ }</tag> |
dad92c30 OZ |
4116 | RDNSS definitions allow to specify a list of advertised recursive DNS |
4117 | servers together with their options. As options are seldom necessary, | |
4118 | there is also a short variant <cf>rdnss <m/address/</cf> that just | |
4119 | specifies one DNS server. Multiple definitions are cumulative. RDNSS | |
4120 | definitions may also be interface-specific when used inside interface | |
4121 | options. By default, interface uses both global and interface-specific | |
0e224d59 | 4122 | options, but that can be changed by <cf/rdnss local/ option. |
18352188 | 4123 | |
b9864aa8 | 4124 | <tag><label id="radv-dnssl">dnssl { <m/options/ }</tag> |
dad92c30 OZ |
4125 | DNSSL definitions allow to specify a list of advertised DNS search |
4126 | domains together with their options. Like <cf/rdnss/ above, multiple | |
4127 | definitions are cumulative, they can be used also as interface-specific | |
4128 | options and there is a short variant <cf>dnssl <m/domain/</cf> that just | |
4129 | specifies one DNS search domain. | |
36da2857 | 4130 | |
b9864aa8 | 4131 | <tag><label id="radv-trigger">trigger <m/prefix/</tag> |
dad92c30 OZ |
4132 | RAdv protocol could be configured to change its behavior based on |
4133 | availability of routes. When this option is used, the protocol waits in | |
4134 | suppressed state until a <it/trigger route/ (for the specified network) | |
df092aa1 | 4135 | is exported to the protocol, the protocol also returns to suppressed |
dad92c30 OZ |
4136 | state if the <it/trigger route/ disappears. Note that route export |
4137 | depends on specified export filter, as usual. This option could be used, | |
4138 | e.g., for handling failover in multihoming scenarios. | |
4139 | ||
4140 | During suppressed state, router advertisements are generated, but with | |
4141 | some fields zeroed. Exact behavior depends on which fields are zeroed, | |
4142 | this can be configured by <cf/sensitive/ option for appropriate | |
4143 | fields. By default, just <cf/default lifetime/ (also called <cf/router | |
4144 | lifetime/) is zeroed, which means hosts cannot use the router as a | |
4145 | default router. <cf/preferred lifetime/ and <cf/valid lifetime/ could | |
4146 | also be configured as <cf/sensitive/ for a prefix, which would cause | |
4147 | autoconfigured IPs to be deprecated or even removed. | |
18352188 MV |
4148 | |
4149 | <tag><label id="radv-propagate-routes">propagate routes <m/switch/</tag> | |
4150 | This option controls propagation of more specific routes, as defined in | |
4151 | <rfc id="4191">. If enabled, all routes exported to the RAdv protocol, | |
4152 | with the exception of the trigger prefix, are added to advertisments as | |
4153 | additional options. The lifetime and preference of advertised routes can | |
4154 | be set individually by <cf/ra_lifetime/ and <cf/ra_preference/ route | |
4155 | attributes, or per interface by <cf/route lifetime/ and | |
4156 | <cf/route preference/ options. Default: disabled. | |
4157 | ||
4158 | Note that the RFC discourages from sending more than 17 routes and | |
4159 | recommends the routes to be configured manually. | |
6bcef225 OZ |
4160 | </descrip> |
4161 | ||
4162 | <p>Interface specific options: | |
4163 | ||
4164 | <descrip> | |
b9864aa8 | 4165 | <tag><label id="radv-iface-max-ra-interval">max ra interval <m/expr/</tag> |
dad92c30 OZ |
4166 | Unsolicited router advertisements are sent in irregular time intervals. |
4167 | This option specifies the maximum length of these intervals, in seconds. | |
4168 | Valid values are 4-1800. Default: 600 | |
6bcef225 | 4169 | |
b9864aa8 | 4170 | <tag><label id="radv-iface-min-ra-interval">min ra interval <m/expr/</tag> |
dad92c30 OZ |
4171 | This option specifies the minimum length of that intervals, in seconds. |
4172 | Must be at least 3 and at most 3/4 * <cf/max ra interval/. Default: | |
4173 | about 1/3 * <cf/max ra interval/. | |
6bcef225 | 4174 | |
b9864aa8 | 4175 | <tag><label id="radv-iface-min-delay">min delay <m/expr/</tag> |
dad92c30 OZ |
4176 | The minimum delay between two consecutive router advertisements, in |
4177 | seconds. Default: 3 | |
6bcef225 | 4178 | |
70a4320b OZ |
4179 | <tag><label id="radv-solicited-ra-unicast">solicited ra unicast <m/switch/</tag> |
4180 | Solicited router advertisements are usually sent to all-nodes multicast | |
4181 | group like unsolicited ones, but the router can be configured to send | |
4182 | them as unicast directly to soliciting nodes instead. This is especially | |
4183 | useful on wireless networks (see <rfc id="7772">). Default: no | |
4184 | ||
b9864aa8 | 4185 | <tag><label id="radv-iface-managed">managed <m/switch/</tag> |
dad92c30 OZ |
4186 | This option specifies whether hosts should use DHCPv6 for IP address |
4187 | configuration. Default: no | |
6bcef225 | 4188 | |
b9864aa8 | 4189 | <tag><label id="radv-iface-other-config">other config <m/switch/</tag> |
dad92c30 OZ |
4190 | This option specifies whether hosts should use DHCPv6 to receive other |
4191 | configuration information. Default: no | |
6bcef225 | 4192 | |
b9864aa8 | 4193 | <tag><label id="radv-iface-link-mtu">link mtu <m/expr/</tag> |
dad92c30 OZ |
4194 | This option specifies which value of MTU should be used by hosts. 0 |
4195 | means unspecified. Default: 0 | |
6bcef225 | 4196 | |
b9864aa8 | 4197 | <tag><label id="radv-iface-reachable-time">reachable time <m/expr/</tag> |
dad92c30 OZ |
4198 | This option specifies the time (in milliseconds) how long hosts should |
4199 | assume a neighbor is reachable (from the last confirmation). Maximum is | |
4200 | 3600000, 0 means unspecified. Default 0. | |
6bcef225 | 4201 | |
b9864aa8 | 4202 | <tag><label id="radv-iface-retrans-timer">retrans timer <m/expr/</tag> |
dad92c30 OZ |
4203 | This option specifies the time (in milliseconds) how long hosts should |
4204 | wait before retransmitting Neighbor Solicitation messages. 0 means | |
4205 | unspecified. Default 0. | |
6bcef225 | 4206 | |
b9864aa8 | 4207 | <tag><label id="radv-iface-current-hop-limit">current hop limit <m/expr/</tag> |
dad92c30 OZ |
4208 | This option specifies which value of Hop Limit should be used by |
4209 | hosts. Valid values are 0-255, 0 means unspecified. Default: 64 | |
6bcef225 | 4210 | |
b9864aa8 | 4211 | <tag><label id="radv-iface-default-lifetime">default lifetime <m/expr/ [sensitive <m/switch/]</tag> |
18352188 | 4212 | This option specifies the time (in seconds) how long (since the receipt |
dad92c30 | 4213 | of RA) hosts may use the router as a default router. 0 means do not use |
b9864aa8 | 4214 | as a default router. For <cf/sensitive/ option, see <ref id="radv-trigger" name="trigger">. |
dad92c30 | 4215 | Default: 3 * <cf/max ra interval/, <cf/sensitive/ yes. |
0e224d59 | 4216 | |
18352188 | 4217 | <tag><label id="radv-iface-default-preference">default preference low|medium|high</tag> |
75148289 OZ |
4218 | This option specifies the Default Router Preference value to advertise |
4219 | to hosts. Default: medium. | |
4220 | ||
18352188 MV |
4221 | <tag><label id="radv-iface-route-lifetime">route lifetime <m/expr/ [sensitive <m/switch/]</tag> |
4222 | This option specifies the default value of advertised lifetime for | |
4223 | specific routes; i.e., the time (in seconds) for how long (since the | |
4224 | receipt of RA) hosts should consider these routes valid. A special value | |
4225 | 0xffffffff represents infinity. The lifetime can be overriden on a per | |
4226 | route basis by the <ref id="rta-ra-lifetime" name="ra_lifetime"> route | |
4227 | attribute. Default: 3 * <cf/max ra interval/, <cf/sensitive/ no. | |
4228 | ||
4229 | For the <cf/sensitive/ option, see <ref id="radv-trigger" name="trigger">. | |
4230 | If <cf/sensitive/ is enabled, even the routes with the <cf/ra_lifetime/ | |
4231 | attribute become sensitive to the trigger. | |
4232 | ||
4233 | <tag><label id="radv-iface-route-preference">route preference low|medium|high</tag> | |
4234 | This option specifies the default value of advertised route preference | |
4235 | for specific routes. The value can be overriden on a per route basis by | |
4236 | the <ref id="rta-ra-preference" name="ra_preference"> route attribute. | |
4237 | Default: medium. | |
4238 | ||
4239 | <tag><label id="radv-prefix-linger-time">prefix linger time <m/expr/</tag> | |
4240 | When a prefix or a route disappears, it is advertised for some time with | |
4241 | zero lifetime, to inform clients it is no longer valid. This option | |
4242 | specifies the time (in seconds) for how long prefixes are advertised | |
4243 | that way. Default: 3 * <cf/max ra interval/. | |
4244 | ||
4245 | <tag><label id="radv-route-linger-time">route linger time <m/expr/</tag> | |
4246 | When a prefix or a route disappears, it is advertised for some time with | |
4247 | zero lifetime, to inform clients it is no longer valid. This option | |
4248 | specifies the time (in seconds) for how long routes are advertised | |
4249 | that way. Default: 3 * <cf/max ra interval/. | |
4250 | ||
b9864aa8 | 4251 | <tag><label id="radv-iface-rdnss-local">rdnss local <m/switch/</tag> |
0e224d59 | 4252 | Use only local (interface-specific) RDNSS definitions for this |
dad92c30 OZ |
4253 | interface. Otherwise, both global and local definitions are used. Could |
4254 | also be used to disable RDNSS for given interface if no local definitons | |
4255 | are specified. Default: no. | |
0e224d59 | 4256 | |
b9864aa8 | 4257 | <tag><label id="radv-iface-dnssl-local">dnssl local <m/switch/</tag> |
dad92c30 OZ |
4258 | Use only local DNSSL definitions for this interface. See <cf/rdnss local/ |
4259 | option above. Default: no. | |
6bcef225 OZ |
4260 | </descrip> |
4261 | ||
b9864aa8 | 4262 | <p>Prefix specific options |
6bcef225 OZ |
4263 | |
4264 | <descrip> | |
b9864aa8 | 4265 | <tag><label id="radv-prefix-skip">skip <m/switch/</tag> |
d214ae4f | 4266 | This option allows to specify that given prefix should not be |
dad92c30 OZ |
4267 | advertised. This is useful for making exceptions from a default policy |
4268 | of advertising all prefixes. Note that for withdrawing an already | |
4269 | advertised prefix it is more useful to advertise it with zero valid | |
4270 | lifetime. Default: no | |
d214ae4f | 4271 | |
b9864aa8 | 4272 | <tag><label id="radv-prefix-onlink">onlink <m/switch/</tag> |
dad92c30 OZ |
4273 | This option specifies whether hosts may use the advertised prefix for |
4274 | onlink determination. Default: yes | |
6bcef225 | 4275 | |
b9864aa8 | 4276 | <tag><label id="radv-prefix-autonomous">autonomous <m/switch/</tag> |
dad92c30 OZ |
4277 | This option specifies whether hosts may use the advertised prefix for |
4278 | stateless autoconfiguration. Default: yes | |
6bcef225 | 4279 | |
b9864aa8 | 4280 | <tag><label id="radv-prefix-valid-lifetime">valid lifetime <m/expr/ [sensitive <m/switch/]</tag> |
dad92c30 OZ |
4281 | This option specifies the time (in seconds) how long (after the |
4282 | receipt of RA) the prefix information is valid, i.e., autoconfigured | |
4283 | IP addresses can be assigned and hosts with that IP addresses are | |
4284 | considered directly reachable. 0 means the prefix is no longer | |
b9864aa8 | 4285 | valid. For <cf/sensitive/ option, see <ref id="radv-trigger" name="trigger">. |
dad92c30 | 4286 | Default: 86400 (1 day), <cf/sensitive/ no. |
6bcef225 | 4287 | |
b9864aa8 | 4288 | <tag><label id="radv-prefix-preferred-lifetime">preferred lifetime <m/expr/ [sensitive <m/switch/]</tag> |
dad92c30 OZ |
4289 | This option specifies the time (in seconds) how long (after the |
4290 | receipt of RA) IP addresses generated from the prefix using stateless | |
4291 | autoconfiguration remain preferred. For <cf/sensitive/ option, | |
b9864aa8 | 4292 | see <ref id="radv-trigger" name="trigger">. Default: 14400 (4 hours), |
dad92c30 | 4293 | <cf/sensitive/ no. |
6bcef225 OZ |
4294 | </descrip> |
4295 | ||
0e224d59 OZ |
4296 | <p>RDNSS specific options: |
4297 | ||
4298 | <descrip> | |
b9864aa8 | 4299 | <tag><label id="radv-rdnss-ns">ns <m/address/</tag> |
dad92c30 OZ |
4300 | This option specifies one recursive DNS server. Can be used multiple |
4301 | times for multiple servers. It is mandatory to have at least one | |
4302 | <cf/ns/ option in <cf/rdnss/ definition. | |
0e224d59 | 4303 | |
b9864aa8 | 4304 | <tag><label id="radv-rdnss-lifetime">lifetime [mult] <m/expr/</tag> |
dad92c30 OZ |
4305 | This option specifies the time how long the RDNSS information may be |
4306 | used by clients after the receipt of RA. It is expressed either in | |
4307 | seconds or (when <cf/mult/ is used) in multiples of <cf/max ra | |
4308 | interval/. Note that RDNSS information is also invalidated when | |
4309 | <cf/default lifetime/ expires. 0 means these addresses are no longer | |
4310 | valid DNS servers. Default: 3 * <cf/max ra interval/. | |
0e224d59 OZ |
4311 | </descrip> |
4312 | ||
0e224d59 OZ |
4313 | <p>DNSSL specific options: |
4314 | ||
4315 | <descrip> | |
b9864aa8 | 4316 | <tag><label id="radv-dnssl-domain">domain <m/address/</tag> |
dad92c30 OZ |
4317 | This option specifies one DNS search domain. Can be used multiple times |
4318 | for multiple domains. It is mandatory to have at least one <cf/domain/ | |
4319 | option in <cf/dnssl/ definition. | |
0e224d59 | 4320 | |
b9864aa8 | 4321 | <tag><label id="radv-dnssl-lifetime">lifetime [mult] <m/expr/</tag> |
dad92c30 OZ |
4322 | This option specifies the time how long the DNSSL information may be |
4323 | used by clients after the receipt of RA. Details are the same as for | |
4324 | RDNSS <cf/lifetime/ option above. Default: 3 * <cf/max ra interval/. | |
0e224d59 OZ |
4325 | </descrip> |
4326 | ||
18352188 MV |
4327 | <sect1>Attributes |
4328 | <label id="radv-attr"> | |
4329 | ||
4330 | <p>RAdv defines two route attributes: | |
4331 | ||
4332 | <descrip> | |
157f6c2a | 4333 | <tag><label id="rta-ra-preference">enum ra_preference</tag> |
18352188 MV |
4334 | The preference of the route. The value can be <it/RA_PREF_LOW/, |
4335 | <it/RA_PREF_MEDIUM/ or <it/RA_PREF_HIGH/. If the attribute is not set, | |
4336 | the <ref id="radv-iface-route-preference" name="route preference"> | |
4337 | option is used. | |
4338 | ||
157f6c2a | 4339 | <tag><label id="rta-ra-lifetime">int ra_lifetime</tag> |
18352188 MV |
4340 | The advertised lifetime of the route, in seconds. The special value of |
4341 | 0xffffffff represents infinity. If the attribute is not set, the | |
4342 | <ref id="radv-iface-route-lifetime" name="route lifetime"> | |
4343 | option is used. | |
4344 | </descrip> | |
0e224d59 | 4345 | |
6bcef225 | 4346 | <sect1>Example |
b9864aa8 | 4347 | <label id="radv-exam"> |
6bcef225 OZ |
4348 | |
4349 | <p><code> | |
cf3e3845 | 4350 | ipv6 table radv_routes; # Manually configured routes go here |
18352188 MV |
4351 | |
4352 | protocol static { | |
cf3e3845 | 4353 | ipv6 { table radv_routes; }; |
18352188 MV |
4354 | |
4355 | route 2001:0DB8:4000::/48 unreachable; | |
4356 | route 2001:0DB8:4010::/48 unreachable; | |
4357 | ||
4358 | route 2001:0DB8:4020::/48 unreachable { | |
4359 | ra_preference = RA_PREF_HIGH; | |
4360 | ra_lifetime = 3600; | |
4361 | }; | |
4362 | } | |
4363 | ||
6bcef225 | 4364 | protocol radv { |
18352188 | 4365 | propagate routes yes; # Propagate the routes from the radv_routes table |
cf3e3845 | 4366 | ipv6 { table radv_routes; export all; }; |
18352188 | 4367 | |
6bcef225 OZ |
4368 | interface "eth2" { |
4369 | max ra interval 5; # Fast failover with more routers | |
4370 | managed yes; # Using DHCPv6 on eth2 | |
4371 | prefix ::/0 { | |
4372 | autonomous off; # So do not autoconfigure any IP | |
4373 | }; | |
4374 | }; | |
4375 | ||
4376 | interface "eth*"; # No need for any other options | |
4377 | ||
4378 | prefix 2001:0DB8:1234::/48 { | |
4379 | preferred lifetime 0; # Deprecated address range | |
4380 | }; | |
4381 | ||
4382 | prefix 2001:0DB8:2000::/48 { | |
4383 | autonomous off; # Do not autoconfigure | |
4384 | }; | |
fc06fb62 OZ |
4385 | |
4386 | rdnss 2001:0DB8:1234::10; # Short form of RDNSS | |
4387 | ||
4388 | rdnss { | |
4389 | lifetime mult 10; | |
4390 | ns 2001:0DB8:1234::11; | |
4391 | ns 2001:0DB8:1234::12; | |
4392 | }; | |
4393 | ||
4394 | dnssl { | |
4395 | lifetime 3600; | |
4396 | domain "abc.com"; | |
4397 | domain "xyz.com"; | |
4398 | }; | |
6bcef225 OZ |
4399 | } |
4400 | </code> | |
4401 | ||
cf3e3845 | 4402 | |
1532a244 | 4403 | <sect>RIP |
b9864aa8 | 4404 | <label id="rip"> |
d37f899b | 4405 | |
371adba6 | 4406 | <sect1>Introduction |
b9864aa8 | 4407 | <label id="rip-intro"> |
d37f899b | 4408 | |
dad92c30 OZ |
4409 | <p>The RIP protocol (also sometimes called Rest In Pieces) is a simple protocol, |
4410 | where each router broadcasts (to all its neighbors) distances to all networks it | |
4411 | can reach. When a router hears distance to another network, it increments it and | |
4412 | broadcasts it back. Broadcasts are done in regular intervals. Therefore, if some | |
4413 | network goes unreachable, routers keep telling each other that its distance is | |
4414 | the original distance plus 1 (actually, plus interface metric, which is usually | |
4415 | one). After some time, the distance reaches infinity (that's 15 in RIP) and all | |
4416 | routers know that network is unreachable. RIP tries to minimize situations where | |
4417 | counting to infinity is necessary, because it is slow. Due to infinity being 16, | |
4418 | you can't use RIP on networks where maximal distance is higher than 15 | |
8465dccb OZ |
4419 | hosts. |
4420 | ||
7935b9d2 | 4421 | <p>BIRD supports RIPv1 (<rfc id="1058">), RIPv2 (<rfc id="2453">), RIPng (<rfc |
64385aee | 4422 | id="2080">), and RIP cryptographic authentication (<rfc id="4822">). |
440439e3 | 4423 | |
1532a244 | 4424 | <p>RIP is a very simple protocol, and it has a lot of shortcomings. Slow |
dad92c30 OZ |
4425 | convergence, big network load and inability to handle larger networks makes it |
4426 | pretty much obsolete. It is still usable on very small networks. | |
d37f899b | 4427 | |
371adba6 | 4428 | <sect1>Configuration |
b9864aa8 | 4429 | <label id="rip-config"> |
d37f899b | 4430 | |
8465dccb | 4431 | <p>RIP configuration consists mainly of common protocol options and interface |
da3cf9ea OZ |
4432 | definitions, most RIP options are interface specific. RIPng (RIP for IPv6) |
4433 | protocol instance can be configured by using <cf/rip ng/ instead of just | |
4434 | <cf/rip/ as a protocol type. | |
8465dccb | 4435 | |
cf3e3845 OZ |
4436 | <p>RIP needs one IPv4 channel. RIPng needs one IPv6 channel. If no channel is |
4437 | configured, appropriate channel is defined with default parameters. | |
4438 | ||
8465dccb | 4439 | <code> |
da3cf9ea | 4440 | protocol rip [ng] [<name>] { |
8465dccb OZ |
4441 | infinity <number>; |
4442 | ecmp <switch> [limit <number>]; | |
4443 | interface <interface pattern> { | |
4444 | metric <number>; | |
4445 | mode multicast|broadcast; | |
4446 | passive <switch>; | |
4447 | address <ip>; | |
4448 | port <number>; | |
4449 | version 1|2; | |
4450 | split horizon <switch>; | |
4451 | poison reverse <switch>; | |
4452 | check zero <switch>; | |
4453 | update time <number>; | |
4454 | timeout time <number>; | |
4455 | garbage time <number>; | |
4456 | ecmp weight <number>; | |
4457 | ttl security <switch>; | tx only; | |
4458 | tx class|dscp <number>; | |
4459 | tx priority <number>; | |
4460 | rx buffer <number>; | |
4461 | tx length <number>; | |
4462 | check link <switch>; | |
4463 | authentication none|plaintext|cryptographic; | |
4464 | password "<text>"; | |
4465 | password "<text>" { | |
4466 | id <num>; | |
4467 | generate from "<date>"; | |
4468 | generate to "<date>"; | |
4469 | accept from "<date>"; | |
4470 | accept to "<date>"; | |
64385aee PT |
4471 | from "<date>"; |
4472 | to "<date>"; | |
4473 | algorithm ( keyed md5 | keyed sha1 | hmac sha1 | hmac sha256 | hmac sha384 | hmac sha512 ); | |
8465dccb OZ |
4474 | }; |
4475 | }; | |
4476 | } | |
4477 | </code> | |
d37f899b PM |
4478 | |
4479 | <descrip> | |
b9864aa8 | 4480 | <tag><label id="rip-infinity">infinity <M>number</M></tag> |
8465dccb OZ |
4481 | Selects the distance of infinity. Bigger values will make |
4482 | protocol convergence even slower. The default value is 16. | |
dad92c30 | 4483 | |
b9864aa8 | 4484 | <tag><label id="rip-ecmp">ecmp <M>switch</M> [limit <M>number</M>]</tag> |
8465dccb OZ |
4485 | This option specifies whether RIP is allowed to generate ECMP |
4486 | (equal-cost multipath) routes. Such routes are used when there are | |
4487 | several directions to the destination, each with the same (computed) | |
4488 | cost. This option also allows to specify a limit on maximum number of | |
cf3e3845 OZ |
4489 | nexthops in one route. By default, ECMP is enabled if supported by |
4490 | Kernel. Default value of the limit is 16. | |
8465dccb | 4491 | |
9df52a98 | 4492 | <tag><label id="rip-iface">interface <m/pattern/ [, <m/.../] { <m/options/ }</tag> |
8465dccb OZ |
4493 | Interface definitions specify a set of interfaces on which the |
4494 | protocol is activated and contain interface specific options. | |
b9864aa8 | 4495 | See <ref id="proto-iface" name="interface"> common options for |
8465dccb | 4496 | detailed description. |
d37f899b PM |
4497 | </descrip> |
4498 | ||
8465dccb | 4499 | <p>Interface specific options: |
ef4a50be OZ |
4500 | |
4501 | <descrip> | |
b9864aa8 | 4502 | <tag><label id="rip-iface-metric">metric <m/num/</tag> |
8465dccb OZ |
4503 | This option specifies the metric of the interface. When a route is |
4504 | received from the interface, its metric is increased by this value | |
4505 | before further processing. Valid values are 1-255, but values higher | |
4506 | than infinity has no further meaning. Default: 1. | |
4507 | ||
b9864aa8 | 4508 | <tag><label id="rip-iface-mode">mode multicast|broadcast</tag> |
8465dccb OZ |
4509 | This option selects the mode for RIP to use on the interface. The |
4510 | default is multicast mode for RIPv2 and broadcast mode for RIPv1. | |
4511 | RIPng always uses the multicast mode. | |
4512 | ||
b9864aa8 | 4513 | <tag><label id="rip-iface-passive">passive <m/switch/</tag> |
8465dccb OZ |
4514 | Passive interfaces receive routing updates but do not transmit any |
4515 | messages. Default: no. | |
4516 | ||
b9864aa8 | 4517 | <tag><label id="rip-iface-address">address <m/ip/</tag> |
8465dccb OZ |
4518 | This option specifies a destination address used for multicast or |
4519 | broadcast messages, the default is the official RIP (224.0.0.9) or RIPng | |
4520 | (ff02::9) multicast address, or an appropriate broadcast address in the | |
4521 | broadcast mode. | |
4522 | ||
b9864aa8 | 4523 | <tag><label id="rip-iface-port">port <m/number/</tag> |
8465dccb OZ |
4524 | This option selects an UDP port to operate on, the default is the |
4525 | official RIP (520) or RIPng (521) port. | |
4526 | ||
b9864aa8 | 4527 | <tag><label id="rip-iface-version">version 1|2</tag> |
8465dccb OZ |
4528 | This option selects the version of RIP used on the interface. For RIPv1, |
4529 | automatic subnet aggregation is not implemented, only classful network | |
4530 | routes and host routes are propagated. Note that BIRD allows RIPv1 to be | |
4531 | configured with features that are defined for RIPv2 only, like | |
4532 | authentication or using multicast sockets. The default is RIPv2 for IPv4 | |
4533 | RIP, the option is not supported for RIPng, as no further versions are | |
4534 | defined. | |
4535 | ||
b9864aa8 | 4536 | <tag><label id="rip-iface-version-only">version only <m/switch/</tag> |
43fc6bb0 OZ |
4537 | Regardless of RIP version configured for the interface, BIRD accepts |
4538 | incoming packets of any RIP version. This option restrict accepted | |
4539 | packets to the configured version. Default: no. | |
4540 | ||
b9864aa8 | 4541 | <tag><label id="rip-iface-split-horizon">split horizon <m/switch/</tag> |
8465dccb OZ |
4542 | Split horizon is a scheme for preventing routing loops. When split |
4543 | horizon is active, routes are not regularly propagated back to the | |
4544 | interface from which they were received. They are either not propagated | |
4545 | back at all (plain split horizon) or propagated back with an infinity | |
4546 | metric (split horizon with poisoned reverse). Therefore, other routers | |
4547 | on the interface will not consider the router as a part of an | |
4548 | independent path to the destination of the route. Default: yes. | |
4549 | ||
b9864aa8 | 4550 | <tag><label id="rip-iface-poison-reverse">poison reverse <m/switch/</tag> |
8465dccb OZ |
4551 | When split horizon is active, this option specifies whether the poisoned |
4552 | reverse variant (propagating routes back with an infinity metric) is | |
4553 | used. The poisoned reverse has some advantages in faster convergence, | |
4554 | but uses more network traffic. Default: yes. | |
4555 | ||
b9864aa8 | 4556 | <tag><label id="rip-iface-check-zero">check zero <m/switch/</tag> |
8465dccb OZ |
4557 | Received RIPv1 packets with non-zero values in reserved fields should |
4558 | be discarded. This option specifies whether the check is performed or | |
4559 | such packets are just processed as usual. Default: yes. | |
4560 | ||
b9864aa8 | 4561 | <tag><label id="rip-iface-update-time">update time <m/number/</tag> |
8465dccb OZ |
4562 | Specifies the number of seconds between periodic updates. A lower number |
4563 | will mean faster convergence but bigger network load. Default: 30. | |
4564 | ||
b9864aa8 | 4565 | <tag><label id="rip-iface-timeout-time">timeout time <m/number/</tag> |
8465dccb OZ |
4566 | Specifies the time interval (in seconds) between the last received route |
4567 | announcement and the route expiration. After that, the network is | |
4568 | considered unreachable, but still is propagated with infinity distance. | |
4569 | Default: 180. | |
4570 | ||
b9864aa8 | 4571 | <tag><label id="rip-iface-garbage-time">garbage time <m/number/</tag> |
8465dccb OZ |
4572 | Specifies the time interval (in seconds) between the route expiration |
4573 | and the removal of the unreachable network entry. The garbage interval, | |
4574 | when a route with infinity metric is propagated, is used for both | |
4575 | internal (after expiration) and external (after withdrawal) routes. | |
4576 | Default: 120. | |
4577 | ||
b9864aa8 | 4578 | <tag><label id="rip-iface-ecmp-weight">ecmp weight <m/number/</tag> |
8465dccb OZ |
4579 | When ECMP (multipath) routes are allowed, this value specifies a |
4580 | relative weight used for nexthops going through the iface. Valid | |
4581 | values are 1-256. Default value is 1. | |
ef4a50be | 4582 | |
b9864aa8 | 4583 | <tag><label id="rip-iface-auth">authentication none|plaintext|cryptographic</tag> |
8465dccb OZ |
4584 | Selects authentication method to be used. <cf/none/ means that packets |
4585 | are not authenticated at all, <cf/plaintext/ means that a plaintext | |
4586 | password is embedded into each packet, and <cf/cryptographic/ means that | |
64385aee PT |
4587 | packets are authenticated using some cryptographic hash function |
4588 | selected by option <cf/algorithm/ for each key. The default | |
4589 | cryptographic algorithm for RIP keys is Keyed-MD5. If you set | |
8465dccb OZ |
4590 | authentication to not-none, it is a good idea to add <cf>password</cf> |
4591 | section. Default: none. | |
4592 | ||
b9864aa8 PT |
4593 | <tag><label id="rip-iface-pass">password "<m/text/"</tag> |
4594 | Specifies a password used for authentication. See <ref id="proto-pass" | |
8465dccb | 4595 | name="password"> common option for detailed description. |
ef4a50be | 4596 | |
b9864aa8 | 4597 | <tag><label id="rip-iface-ttl-security">ttl security [<m/switch/ | tx only]</tag> |
dad92c30 OZ |
4598 | TTL security is a feature that protects routing protocols from remote |
4599 | spoofed packets by using TTL 255 instead of TTL 1 for protocol packets | |
4600 | destined to neighbors. Because TTL is decremented when packets are | |
4601 | forwarded, it is non-trivial to spoof packets with TTL 255 from remote | |
4602 | locations. | |
4603 | ||
4604 | If this option is enabled, the router will send RIP packets with TTL 255 | |
4605 | and drop received packets with TTL less than 255. If this option si set | |
4606 | to <cf/tx only/, TTL 255 is used for sent packets, but is not checked | |
4607 | for received packets. Such setting does not offer protection, but offers | |
4608 | compatibility with neighbors regardless of whether they use ttl | |
4609 | security. | |
4610 | ||
7935b9d2 PT |
4611 | For RIPng, TTL security is a standard behavior (required by <rfc |
4612 | id="2080">) and therefore default value is yes. For IPv4 RIP, default | |
4613 | value is no. | |
6ac4f87a | 4614 | |
b9864aa8 | 4615 | <tag><label id="rip-iface-tx-class">tx class|dscp|priority <m/number/</tag> |
dad92c30 | 4616 | These options specify the ToS/DiffServ/Traffic class/Priority of the |
b9864aa8 | 4617 | outgoing RIP packets. See <ref id="proto-tx-class" name="tx class"> common |
dad92c30 | 4618 | option for detailed description. |
d37f899b | 4619 | |
b9864aa8 | 4620 | <tag><label id="rip-iface-rx-buffer">rx buffer <m/number/</tag> |
8465dccb OZ |
4621 | This option specifies the size of buffers used for packet processing. |
4622 | The buffer size should be bigger than maximal size of received packets. | |
4623 | The default value is 532 for IPv4 RIP and interface MTU value for RIPng. | |
4624 | ||
b9864aa8 | 4625 | <tag><label id="rip-iface-tx-length">tx length <m/number/</tag> |
8465dccb OZ |
4626 | This option specifies the maximum length of generated RIP packets. To |
4627 | avoid IP fragmentation, it should not exceed the interface MTU value. | |
4628 | The default value is 532 for IPv4 RIP and interface MTU value for RIPng. | |
4629 | ||
b9864aa8 | 4630 | <tag><label id="rip-iface-check-link">check link <m/switch/</tag> |
8465dccb OZ |
4631 | If set, the hardware link state (as reported by OS) is taken into |
4632 | consideration. When the link disappears (e.g. an ethernet cable is | |
4633 | unplugged), neighbors are immediately considered unreachable and all | |
4634 | routes received from them are withdrawn. It is possible that some | |
64385aee | 4635 | hardware drivers or platforms do not implement this feature. |
cf3e3845 | 4636 | Default: yes. |
d37f899b PM |
4637 | </descrip> |
4638 | ||
371adba6 | 4639 | <sect1>Attributes |
b9864aa8 | 4640 | <label id="rip-attr"> |
d37f899b | 4641 | |
1b55b1a3 MM |
4642 | <p>RIP defines two route attributes: |
4643 | ||
4644 | <descrip> | |
157f6c2a | 4645 | <tag><label id="rta-rip-metric">int rip_metric</tag> |
65d2a88d | 4646 | RIP metric of the route (ranging from 0 to <cf/infinity/). When routes |
dad92c30 | 4647 | from different RIP instances are available and all of them have the same |
8465dccb OZ |
4648 | preference, BIRD prefers the route with lowest <cf/rip_metric/. When a |
4649 | non-RIP route is exported to RIP, the default metric is 1. | |
dad92c30 | 4650 | |
157f6c2a | 4651 | <tag><label id="rta-rip-tag">int rip_tag</tag> |
dad92c30 OZ |
4652 | RIP route tag: a 16-bit number which can be used to carry additional |
4653 | information with the route (for example, an originating AS number in | |
8465dccb OZ |
4654 | case of external routes). When a non-RIP route is exported to RIP, the |
4655 | default tag is 0. | |
1b55b1a3 MM |
4656 | </descrip> |
4657 | ||
371adba6 | 4658 | <sect1>Example |
b9864aa8 | 4659 | <label id="rip-exam"> |
1b55b1a3 MM |
4660 | |
4661 | <p><code> | |
8465dccb | 4662 | protocol rip { |
cf3e3845 OZ |
4663 | ipv4 { |
4664 | import all; | |
4665 | export all; | |
4666 | }; | |
9be12a7d OZ |
4667 | interface "eth*" { |
4668 | metric 2; | |
4669 | port 1520; | |
4670 | mode multicast; | |
4671 | update time 12; | |
4672 | timeout time 60; | |
4673 | authentication cryptographic; | |
4674 | password "secret" { algorithm hmac sha256; }; | |
4675 | }; | |
d37f899b | 4676 | } |
a0dd1c74 | 4677 | </code> |
d37f899b | 4678 | |
cf3e3845 | 4679 | |
65d2a88d | 4680 | <sect>RPKI |
159d619c | 4681 | <label id="rpki"> |
65d2a88d PT |
4682 | |
4683 | <sect1>Introduction | |
4684 | ||
4685 | <p>The Resource Public Key Infrastructure (RPKI) is mechanism for origin | |
4686 | validation of BGP routes (RFC 6480). BIRD supports only so-called RPKI-based | |
4687 | origin validation. There is implemented RPKI to Router (RPKI-RTR) protocol (RFC | |
cf3e3845 | 4688 | 6810). It uses some of the RPKI data to allow a router to verify that the |
65d2a88d PT |
4689 | autonomous system announcing an IP address prefix is in fact authorized to do |
4690 | so. This is not crypto checked so can be violated. But it should prevent the | |
4691 | vast majority of accidental hijackings on the Internet today, e.g. the famous | |
4692 | Pakastani accidental announcement of YouTube's address space. | |
4693 | ||
4694 | <p>The RPKI-RTR protocol receives and maintains a set of ROAs from a cache | |
4695 | server (also called validator). You can validate routes (RFC 6483) using | |
4696 | function <cf/roa_check()/ in filter and set it as import filter at the BGP | |
4697 | protocol. BIRD should re-validate all of affected routes after RPKI update by | |
4698 | RFC 6811, but we don't support it yet! You can use a BIRD's client command | |
4699 | <cf>reload in <m/bgp_protocol_name/</cf> for manual call of revalidation of all | |
4700 | routes. | |
4701 | ||
4702 | <sect1>Supported transports | |
71c51aa4 | 4703 | <p> |
65d2a88d PT |
4704 | <itemize> |
4705 | <item>Unprotected transport over TCP uses a port 323. The cache server | |
4706 | and BIRD router should be on the same trusted and controlled network | |
4707 | for security reasons. | |
4708 | <item>SSHv2 encrypted transport connection uses the normal SSH port | |
4709 | 22. | |
4710 | </itemize> | |
4711 | ||
4712 | <sect1>Configuration | |
4713 | ||
4714 | <p>We currently support just one cache server per protocol. However you can | |
4715 | define more RPKI protocols generally. | |
4716 | ||
4717 | <code> | |
4718 | protocol rpki [<name>] { | |
4719 | roa4 { table <tab>; }; | |
4720 | roa6 { table <tab>; }; | |
4721 | remote <ip> | "<domain>" [port <num>]; | |
4722 | port <num>; | |
4723 | refresh [keep] <num>; | |
4724 | retry [keep] <num>; | |
4725 | expire [keep] <num>; | |
4726 | transport tcp; | |
4727 | transport ssh { | |
4728 | bird private key "</path/to/id_rsa>"; | |
4729 | remote public key "</path/to/known_host>"; | |
4730 | user "<name>"; | |
4731 | }; | |
4732 | } | |
4733 | </code> | |
4734 | ||
cf3e3845 OZ |
4735 | <p>Alse note that you have to specify the ROA channel. If you want to import |
4736 | only IPv4 prefixes you have to specify only roa4 channel. Similarly with IPv6 | |
4737 | prefixes only. If you want to fetch both IPv4 and even IPv6 ROAs you have to | |
4738 | specify both channels. | |
65d2a88d PT |
4739 | |
4740 | <sect2>RPKI protocol options | |
71c51aa4 | 4741 | <p> |
65d2a88d PT |
4742 | <descrip> |
4743 | <tag>remote <m/ip/ | "<m/hostname/" [port <m/num/]</tag> Specifies | |
4744 | a destination address of the cache server. Can be specified by an IP | |
4745 | address or by full domain name string. Only one cache can be specified | |
4746 | per protocol. This option is required. | |
4747 | ||
4748 | <tag>port <m/num/</tag> Specifies the port number. The default port | |
4749 | number is 323 for transport without any encryption and 22 for transport | |
4750 | with SSH encryption. | |
4751 | ||
4752 | <tag>refresh [keep] <m/num/</tag> Time period in seconds. Tells how | |
4753 | long to wait before next attempting to poll the cache using a Serial | |
4754 | Query or a Reset Query packet. Must be lower than 86400 seconds (one | |
4755 | day). Too low value can caused a false positive detection of | |
4756 | network connection problems. A keyword <cf/keep/ suppresses updating | |
4757 | this value by a cache server. | |
4758 | Default: 3600 seconds | |
4759 | ||
4760 | <tag>retry [keep] <m/num/</tag> Time period in seconds between a failed | |
4761 | Serial/Reset Query and a next attempt. Maximum allowed value is 7200 | |
4762 | seconds (two hours). Too low value can caused a false positive | |
4763 | detection of network connection problems. A keyword <cf/keep/ | |
4764 | suppresses updating this value by a cache server. | |
4765 | Default: 600 seconds | |
4766 | ||
4767 | <tag>expire [keep] <m/num/</tag> Time period in seconds. Received | |
4768 | records are deleted if the client was unable to successfully refresh | |
4769 | data for this time period. Must be in range from 600 seconds (ten | |
4770 | minutes) to 172800 seconds (two days). A keyword <cf/keep/ | |
4771 | suppresses updating this value by a cache server. | |
4772 | Default: 7200 seconds | |
4773 | ||
4774 | <tag>transport tcp</tag> Unprotected transport over TCP. It's a default | |
4775 | transport. Should be used only on secure private networks. | |
4776 | Default: tcp | |
4777 | ||
4778 | <tag>transport ssh { <m/SSH transport options.../ }</tag> It enables a | |
4779 | SSHv2 transport encryption. Cannot be combined with a TCP transport. | |
4780 | Default: off | |
4781 | </descrip> | |
4782 | ||
4783 | <sect3>SSH transport options | |
71c51aa4 | 4784 | <p> |
65d2a88d PT |
4785 | <descrip> |
4786 | <tag>bird private key "<m>/path/to/id_rsa</m>"</tag> | |
4787 | A path to the BIRD's private SSH key for authentication. | |
4788 | It can be a <cf><m>id_rsa</m></cf> file. | |
4789 | ||
4790 | <tag>remote public key "<m>/path/to/known_host</m>"</tag> | |
4791 | A path to the cache's public SSH key for verification identity | |
4792 | of the cache server. It could be a path to <cf><m>known_host</m></cf> file. | |
4793 | ||
4794 | <tag>user "<m/name/"</tag> | |
4795 | A SSH user name for authentication. This option is a required. | |
4796 | </descrip> | |
4797 | ||
4798 | <sect1>Examples | |
4799 | <sect2>BGP origin validation | |
4800 | <p>Policy: Don't import <cf/ROA_INVALID/ routes. | |
4801 | <code> | |
4802 | roa4 table r4; | |
4803 | roa6 table r6; | |
4804 | ||
4805 | protocol rpki { | |
4806 | debug all; | |
cf3e3845 | 4807 | |
65d2a88d PT |
4808 | roa4 { table r4; }; |
4809 | roa6 { table r6; }; | |
4810 | ||
4811 | # Please, do not use rpki-validator.realmv6.org in production | |
4812 | remote "rpki-validator.realmv6.org" port 8282; | |
cf3e3845 | 4813 | |
65d2a88d PT |
4814 | retry keep 5; |
4815 | refresh keep 30; | |
4816 | expire 600; | |
4817 | } | |
4818 | ||
cf3e3845 OZ |
4819 | filter peer_in_v4 { |
4820 | if (roa_check(r4, net, bgp_path.last) = ROA_INVALID) then | |
65d2a88d | 4821 | { |
eeb2c616 | 4822 | print "Ignore RPKI invalid ", net, " for ASN ", bgp_path.last; |
65d2a88d PT |
4823 | reject; |
4824 | } | |
4825 | accept; | |
4826 | } | |
4827 | ||
4828 | protocol bgp { | |
4829 | debug all; | |
4830 | local as 65000; | |
4831 | neighbor 192.168.2.1 as 65001; | |
3831b619 OZ |
4832 | ipv4 { |
4833 | import filter peer_in_v4; | |
4834 | export none; | |
4835 | }; | |
65d2a88d PT |
4836 | } |
4837 | </code> | |
4838 | ||
4839 | <sect2>SSHv2 transport encryption | |
71c51aa4 | 4840 | <p> |
65d2a88d PT |
4841 | <code> |
4842 | roa4 table r4; | |
4843 | roa6 table r6; | |
4844 | ||
4845 | protocol rpki { | |
4846 | debug all; | |
cf3e3845 | 4847 | |
65d2a88d PT |
4848 | roa4 { table r4; }; |
4849 | roa6 { table r6; }; | |
cf3e3845 | 4850 | |
65d2a88d PT |
4851 | remote 127.0.0.1 port 2345; |
4852 | transport ssh { | |
4853 | bird private key "/home/birdgeek/.ssh/id_rsa"; | |
4854 | remote public key "/home/birdgeek/.ssh/known_hosts"; | |
4855 | user "birdgeek"; | |
4856 | }; | |
cf3e3845 | 4857 | |
65d2a88d PT |
4858 | # Default interval values |
4859 | } | |
4860 | </code> | |
4861 | ||
4862 | ||
371adba6 | 4863 | <sect>Static |
b9864aa8 | 4864 | <label id="static"> |
1b55b1a3 | 4865 | |
0e4789c2 | 4866 | <p>The Static protocol doesn't communicate with other routers in the network, |
f8e2d916 | 4867 | but instead it allows you to define routes manually. This is often used for |
79a2b697 | 4868 | specifying how to forward packets to parts of the network which don't use |
dad92c30 OZ |
4869 | dynamic routing at all and also for defining sink routes (i.e., those telling to |
4870 | return packets as undeliverable if they are in your IP block, you don't have any | |
4871 | specific destination for them and you don't want to send them out through the | |
4872 | default route to prevent routing loops). | |
4873 | ||
43fc6bb0 OZ |
4874 | <p>There are three classes of definitions in Static protocol configuration -- |
4875 | global options, static route definitions, and per-route options. Usually, the | |
4876 | definition of the protocol contains mainly a list of static routes. | |
3e52d112 | 4877 | Static routes have no specific attributes. |
43fc6bb0 OZ |
4878 | |
4879 | <p>Global options: | |
4880 | ||
4881 | <descrip> | |
b9864aa8 | 4882 | <tag><label id="static-check-link">check link <m/switch/</tag> |
43fc6bb0 OZ |
4883 | If set, hardware link states of network interfaces are taken into |
4884 | consideration. When link disappears (e.g. ethernet cable is unplugged), | |
4885 | static routes directing to that interface are removed. It is possible | |
4886 | that some hardware drivers or platforms do not implement this feature. | |
4887 | Default: off. | |
4888 | ||
b9864aa8 | 4889 | <tag><label id="static-igp-table">igp table <m/name/</tag> |
43fc6bb0 OZ |
4890 | Specifies a table that is used for route table lookups of recursive |
4891 | routes. Default: the same table as the protocol is connected to. | |
4892 | </descrip> | |
4893 | ||
4894 | <p>Route definitions (each may also contain a block of per-route options): | |
79a2b697 | 4895 | |
71c51aa4 | 4896 | <sect1>Regular routes; MPLS switching rules |
dad92c30 | 4897 | |
71c51aa4 | 4898 | <p>There exist several types of routes; keep in mind that <m/prefix/ syntax is |
3e52d112 | 4899 | <ref id="type-prefix" name="dependent on network type">. |
dad92c30 | 4900 | |
3e52d112 JMM |
4901 | <descrip> |
4902 | <tag>route <m/prefix/ via <m/ip/|<m/"interface"/ [mpls <m/num/[/<m/num/[/<m/num/[...]]]]</tag> | |
4903 | Next hop routes may bear one or more <ref id="route-next-hop" name="next hops">. | |
4904 | Every next hop is preceded by <cf/via/ and configured as shown. | |
cf3e3845 | 4905 | |
3e52d112 JMM |
4906 | <tag>route <m/prefix/ recursive <m/ip/ [mpls <m/num/[/<m/num/[/<m/num/[...]]]]</tag> |
4907 | Recursive nexthop resolves the given IP in the configured IGP table and | |
4908 | uses that route's next hop. The MPLS stacks are concatenated; on top is | |
4909 | the IGP's nexthop stack and on bottom is this route's stack. | |
cf3e3845 | 4910 | |
3e52d112 | 4911 | <tag>route <m/prefix/ blackhole|unreachable|prohibit</tag> |
dad92c30 OZ |
4912 | Special routes specifying to silently drop the packet, return it as |
4913 | unreachable or return it as administratively prohibited. First two | |
4914 | targets are also known as <cf/drop/ and <cf/reject/. | |
43fc6bb0 | 4915 | </descrip> |
391931d4 | 4916 | |
3e52d112 JMM |
4917 | <p>When the particular destination is not available (the interface is down or |
4918 | the next hop of the route is not a neighbor at the moment), Static just | |
4919 | uninstalls the route from the table it is connected to and adds it again as soon | |
4920 | as the destination becomes adjacent again. | |
4921 | ||
4922 | <sect1>Route Origin Authorization | |
4923 | ||
4924 | <p>The ROA config is just <cf>route <m/prefix/ max <m/int/ as <m/int/</cf> with no nexthop. | |
4925 | ||
4926 | <sect1>Flowspec | |
4927 | <label id="flowspec-network-type"> | |
4928 | ||
4929 | <p>The flow specification are rules for routers and firewalls for filtering | |
4930 | purpose. It is described by <rfc id="5575">. There are 3 types of arguments: | |
4931 | <m/inet4/ or <m/inet6/ prefixes, bitmasks matching expressions and numbers | |
4932 | matching expressions. | |
4933 | ||
4934 | Bitmasks matching is written using <m/value/<cf>/</cf><m/mask/ or | |
4935 | <cf/!/<m/value/<cf>/</cf><m/mask/ pairs. It means that <cf/(/<m/data/ <cf/&/ | |
4936 | <m/mask/<cf/)/ is or is not equal to <m/value/. | |
4937 | ||
4938 | Numbers matching is a matching sequence of numbers and ranges separeted by a | |
4939 | commas (<cf/,/) (e.g. <cf/10,20,30/). Ranges can be written using double dots | |
4940 | <cf/../ notation (e.g. <cf/80..90,120..124/). An alternative notation are | |
4941 | sequence of one or more pairs of relational operators and values separated by | |
4942 | logical operators <cf/&&/ or <cf/||/. Allowed relational operators are <cf/=/, | |
4943 | <cf/!=/, <cf/</, <cf/<=/, <cf/>/, <cf/>=/, <cf/true/ and <cf/false/. | |
4944 | ||
4945 | <sect2>IPv4 Flowspec | |
4946 | ||
4947 | <p><descrip> | |
4948 | <tag><label id="flow-dst">dst <m/inet4/</tag> | |
4949 | Set a matching destination prefix (e.g. <cf>dst 192.168.0.0/16</cf>). | |
4950 | Only this option is mandatory in IPv4 Flowspec. | |
4951 | ||
4952 | <tag><label id="flow-src">src <m/inet4/</tag> | |
4953 | Set a matching source prefix (e.g. <cf>src 10.0.0.0/8</cf>). | |
4954 | ||
4955 | <tag><label id="flow-proto">proto <m/numbers-match/</tag> | |
4956 | Set a matching IP protocol numbers (e.g. <cf/proto 6/). | |
4957 | ||
4958 | <tag><label id="flow-port">port <m/numbers-match/</tag> | |
4959 | Set a matching source or destination TCP/UDP port numbers (e.g. | |
4960 | <cf>port 1..1023,1194,3306</cf>). | |
4961 | ||
4962 | <tag><label id="flow-dport">dport <m/numbers-match/</tag> | |
4963 | Set a mating destination port numbers (e.g. <cf>dport 49151</cf>). | |
4964 | ||
4965 | <tag><label id="flow-sport">sport <m/numbers-match/</tag> | |
4966 | Set a matching source port numbers (e.g. <cf>sport = 0</cf>). | |
4967 | ||
4968 | <tag><label id="flow-icmp-type">icmp type <m/numbers-match/</tag> | |
4969 | Set a matching type field number of an ICMP packet (e.g. <cf>icmp type | |
4970 | 3</cf>) | |
4971 | ||
4972 | <tag><label id="flow-icmp-code">icmp code <m/numbers-match/</tag> | |
4973 | Set a matching code field number of an ICMP packet (e.g. <cf>icmp code | |
4974 | 1</cf>) | |
4975 | ||
4976 | <tag><label id="flow-tcp-flags">tcp flags <m/bitmask-match/</tag> | |
4977 | Set a matching bitmask for TCP header flags (aka control bits) (e.g. | |
4978 | <cf>tcp flags 0x03/0x0f;</cf>). The maximum length of mask is 12 bits | |
4979 | (0xfff). | |
4980 | ||
4981 | <tag><label id="flow-length">length <m/numbers-match/</tag> | |
4982 | Set a matching packet length (e.g. <cf>length > 1500;</cf>) | |
4983 | ||
4984 | <tag><label id="flow-dscp">dscp <m/numbers-match/</tag> | |
4985 | Set a matching DiffServ Code Point number (e.g. <cf>length > 1500;</cf>). | |
4986 | ||
4987 | <tag><label id="flow-fragment">fragment <m/fragmentation-type/</tag> | |
4988 | Set a matching type of packet fragmentation. Allowed fragmentation | |
4989 | types are <cf/dont_fragment/, <cf/is_fragment/, <cf/first_fragment/, | |
4990 | <cf/last_fragment/ (e.g. <cf>fragment is_fragment && | |
4991 | !dont_fragment</cf>). | |
4992 | </descrip> | |
4993 | ||
4994 | <p><code> | |
4995 | protocol static { | |
4996 | flow4; | |
4997 | ||
4998 | route flow4 { | |
4999 | dst 10.0.0.0/8; | |
5000 | port > 24 && < 30 || 40..50,60..70,80 && >= 90; | |
5001 | tcp flags 0x03/0x0f; | |
5002 | length > 1024; | |
5003 | dscp = 63; | |
5004 | fragment dont_fragment, is_fragment || !first_fragment; | |
cf3e3845 | 5005 | }; |
3e52d112 JMM |
5006 | } |
5007 | </code> | |
5008 | ||
5009 | <sect2>Differences for IPv6 Flowspec | |
5010 | ||
5011 | <p>Flowspec IPv6 are same as Flowspec IPv4 with a few exceptions. | |
5012 | <itemize> | |
5013 | <item>Prefixes <m/inet6/ can be specified not only with prefix length, | |
5014 | but with prefix <cf/offset/ <m/num/ too (e.g. | |
5015 | <cf>::1234:5678:9800:0000/101 offset 64</cf>). Offset means to don't | |
5016 | care of <m/num/ first bits. | |
5017 | <item>IPv6 Flowspec hasn't mandatory any flowspec component. | |
5018 | <item>In IPv6 packets, there is a matching the last next header value | |
5019 | for a matching IP protocol number (e.g. <cf>next header 6</cf>). | |
5020 | <item>It is not possible to set <cf>dont_fragment</cf> as a type of | |
5021 | packet fragmentation. | |
5022 | </itemize> | |
5023 | ||
5024 | <p><descrip> | |
5025 | <tag><label id="flow6-dst">dst <m/inet6/ [offset <m/num/]</tag> | |
5026 | Set a matching destination IPv6 prefix (e.g. <cf>dst | |
5027 | ::1c77:3769:27ad:a11a/128 offset 64</cf>). | |
5028 | ||
5029 | <tag><label id="flow6-src">src <m/inet6/ [offset <m/num/]</tag> | |
5030 | Set a matching source IPv6 prefix (e.g. <cf>src fe80::/64</cf>). | |
5031 | ||
5032 | <tag><label id="flow6-next-header">next header <m/numbers-match/</tag> | |
5033 | Set a matching IP protocol numbers (e.g. <cf>next header != 6</cf>). | |
5034 | ||
5035 | <tag><label id="flow6-label">label <m/bitmask-match/</tag> | |
5036 | Set a 20-bit bitmask for matching Flow Label field in IPv6 packets | |
5037 | (e.g. <cf>label 0x8e5/0x8e5</cf>). | |
5038 | </descrip> | |
5039 | ||
5040 | <p><code> | |
5041 | protocol static { | |
5042 | flow6 { table myflow6; }; | |
5043 | ||
5044 | route flow6 { | |
5045 | dst fec0:1122:3344:5566:7788:99aa:bbcc:ddee/128; | |
5046 | src 0000:0000:0000:0001:1234:5678:9800:0000/101 offset 63; | |
5047 | next header = 23; | |
5048 | sport > 24 && < 30 || = 40 || 50,60,70..80; | |
5049 | dport = 50; | |
5050 | tcp flags 0x03/0x0f, !0/0xff || 0x33/0x33; | |
5051 | fragment !is_fragment || !first_fragment; | |
5052 | label 0xaaaa/0xaaaa && 0x33/0x33; | |
cf3e3845 | 5053 | }; |
3e52d112 JMM |
5054 | } |
5055 | </code> | |
dad92c30 | 5056 | |
3e52d112 | 5057 | <sect1>Per-route options |
71c51aa4 | 5058 | <p> |
43fc6bb0 | 5059 | <descrip> |
b9864aa8 | 5060 | <tag><label id="static-route-bfd">bfd <m/switch/</tag> |
43fc6bb0 OZ |
5061 | The Static protocol could use BFD protocol for next hop liveness |
5062 | detection. If enabled, a BFD session to the route next hop is created | |
5063 | and the static route is BFD-controlled -- the static route is announced | |
5064 | only if the next hop liveness is confirmed by BFD. If the BFD session | |
5065 | fails, the static route is removed. Note that this is a bit different | |
5066 | compared to other protocols, which may use BFD as an advisory mechanism | |
5067 | for fast failure detection but ignores it if a BFD session is not even | |
5068 | established. | |
5069 | ||
5070 | This option can be used for static routes with a direct next hop, or | |
5071 | also for for individual next hops in a static multipath route (see | |
5072 | above). Note that BFD protocol also has to be configured, see | |
b9864aa8 | 5073 | <ref id="bfd" name="BFD"> section for details. Default value is no. |
43fc6bb0 | 5074 | |
b9864aa8 | 5075 | <tag><label id="static-route-filter"><m/filter expression/</tag> |
43fc6bb0 OZ |
5076 | This is a special option that allows filter expressions to be configured |
5077 | on per-route basis. Can be used multiple times. These expressions are | |
5078 | evaluated when the route is originated, similarly to the import filter | |
5079 | of the static protocol. This is especially useful for configuring route | |
5080 | attributes, e.g., <cf/ospf_metric1 = 100;/ for a route that will be | |
5081 | exported to the OSPF protocol. | |
79a2b697 MM |
5082 | </descrip> |
5083 | ||
3e52d112 | 5084 | <sect1>Example static config |
79a2b697 MM |
5085 | |
5086 | <p><code> | |
5087 | protocol static { | |
3e52d112 | 5088 | ipv4 { table testable; }; # Connect to a non-default routing table |
43fc6bb0 | 5089 | check link; # Advertise routes only if link is up |
9491f9f5 | 5090 | route 0.0.0.0/0 via 198.51.100.130; # Default route |
3e52d112 | 5091 | route 10.0.0.0/8 # Multipath route |
9491f9f5 | 5092 | via 198.51.100.10 weight 2 |
43fc6bb0 | 5093 | via 198.51.100.20 bfd # BFD-controlled next hop |
9491f9f5 | 5094 | via 192.0.2.1; |
80a9cadc | 5095 | route 203.0.113.0/24 unreachable; # Sink route |
43fc6bb0 OZ |
5096 | route 10.2.0.0/24 via "arc0"; # Secondary network |
5097 | route 192.168.10.0/24 via 198.51.100.100 { | |
5098 | ospf_metric1 = 20; # Set extended attribute | |
5099 | } | |
5100 | route 192.168.10.0/24 via 198.51.100.100 { | |
5101 | ospf_metric2 = 100; # Set extended attribute | |
5102 | ospf_tag = 2; # Set extended attribute | |
5103 | bfd; # BFD-controlled route | |
5104 | } | |
79a2b697 MM |
5105 | } |
5106 | </code> | |
5107 | ||
cf3e3845 | 5108 | |
96264d4d | 5109 | <chapt>Conclusions |
b9864aa8 | 5110 | <label id="conclusion"> |
96264d4d PM |
5111 | |
5112 | <sect>Future work | |
b9864aa8 | 5113 | <label id="future-work"> |
96264d4d | 5114 | |
dad92c30 OZ |
5115 | <p>Although BIRD supports all the commonly used routing protocols, there are |
5116 | still some features which would surely deserve to be implemented in future | |
5117 | versions of BIRD: | |
96264d4d PM |
5118 | |
5119 | <itemize> | |
55b58d8c | 5120 | <item>Opaque LSA's |
96264d4d | 5121 | <item>Route aggregation and flap dampening |
96264d4d PM |
5122 | <item>Multicast routing protocols |
5123 | <item>Ports to other systems | |
5124 | </itemize> | |
5125 | ||
dad92c30 | 5126 | |
96264d4d | 5127 | <sect>Getting more help |
b9864aa8 | 5128 | <label id="help"> |
96264d4d PM |
5129 | |
5130 | <p>If you use BIRD, you're welcome to join the bird-users mailing list | |
d148d0af | 5131 | (<HTMLURL URL="mailto:bird-users@network.cz" name="bird-users@network.cz">) |
96264d4d | 5132 | where you can share your experiences with the other users and consult |
d148d0af OF |
5133 | your problems with the authors. To subscribe to the list, visit |
5134 | <HTMLURL URL="http://bird.network.cz/?m_list" name="http://bird.network.cz/?m_list">. | |
96264d4d PM |
5135 | The home page of BIRD can be found at <HTMLURL URL="http://bird.network.cz/" name="http://bird.network.cz/">. |
5136 | ||
dad92c30 OZ |
5137 | <p>BIRD is a relatively young system and it probably contains some bugs. You can |
5138 | report any problems to the bird-users list and the authors will be glad to solve | |
5139 | them, but before you do so, please make sure you have read the available | |
5140 | documentation and that you are running the latest version (available at | |
5141 | <HTMLURL URL="ftp://bird.network.cz/pub/bird" name="bird.network.cz:/pub/bird">). | |
5142 | (Of course, a patch which fixes the bug is always welcome as an attachment.) | |
5143 | ||
5144 | <p>If you want to understand what is going inside, Internet standards are a good | |
5145 | and interesting reading. You can get them from | |
5146 | <HTMLURL URL="ftp://ftp.rfc-editor.org/" name="ftp.rfc-editor.org"> (or a | |
5147 | nicely sorted version from <HTMLURL URL="ftp://atrey.karlin.mff.cuni.cz/pub/rfc" | |
5148 | name="atrey.karlin.mff.cuni.cz:/pub/rfc">). | |
69477cad | 5149 | |
c184d9d0 | 5150 | <p><it/Good luck!/ |
69477cad | 5151 | |
371adba6 | 5152 | </book> |
7581b81b | 5153 | |
a0dd1c74 | 5154 | <!-- |
75317ab8 MM |
5155 | LocalWords: GPL IPv GateD BGPv RIPv OSPFv Linux sgml html dvi sgmltools Pavel |
5156 | LocalWords: linuxdoc dtd descrip config conf syslog stderr auth ospf bgp Mbps | |
5a203dac | 5157 | LocalWords: router's eval expr num birdc ctl UNIX if's enums bool int ip GCC |
75317ab8 MM |
5158 | LocalWords: len ipaddress pxlen netmask enum bgppath bgpmask clist gw md eth |
5159 | LocalWords: RTS printn quitbird iBGP AS'es eBGP RFC multiprotocol IGP Machek | |
4e8ec666 | 5160 | LocalWords: EGP misconfigurations keepalive pref aggr aggregator BIRD's RTC |
5a203dac | 5161 | LocalWords: OS'es AS's multicast nolisten misconfigured UID blackhole MRTD MTU |
4e8ec666 | 5162 | LocalWords: uninstalls ethernets IP binutils ANYCAST anycast dest RTD ICMP rfc |
5a203dac | 5163 | LocalWords: compat multicasts nonbroadcast pointopoint loopback sym stats |
64722c98 | 5164 | LocalWords: Perl SIGHUP dd mm yy HH MM SS EXT IA UNICAST multihop Discriminator txt |
5adc02a6 | 5165 | LocalWords: proto wildcard Ondrej Filip |
5a64ac70 | 5166 | --> |