Revision 64722c98

View differences:

doc/bird.sgml
283 283
	<tag>passwords { password "<m/password/" from <m/time/ to <m/time/ passive <m/time/ id
284 284
	<m/num/ [...] }</tag> Specifies passwords to be used with this protocol. <cf>Passive <m/time/</cf> is
285 285
	time from which the password is not used for sending, but it is recognized on reception. <cf/id/ is password ID, as needed by
286
	certain protocols.
286
	certain protocols. Format of <cf><m/time/</cf> is <tt>dd-mm-yy HH:MM:SS</tt>.
287 287

  
288 288
	<tag>interface "<m/mask/"|<m/prefix/ [ { <m/option/ ; [ ... ] } ]</tag> Specifies which
289 289
	interfaces this protocol is active on, and allows you to set options on
......
309 309
own application could do that, too -- format of communication between
310 310
BIRD and BIRDC is stable (see programmer's documentation).
311 311

  
312
<p>Here is very brief list of supported functions:
313

  
314
<descrip>
315
	<tag>dump resources|sockets|interfaces|neighbors|attributs|routes|protocols</tag>
316
	Send requested information to a standard logging facility.
317

  
318
	<tag>show status|protocols [all]|interfaces [summary]|symbols</tag>
319
	Show requested information on client.
320

  
321
	<tag>show route [<m/prefix/|for <m/prefix or IP/] [table <m/name/] [table <m/sym/] [all] [stats] [count] [primary] [filter <m/name/] [import_or_proto <m/sym/]</tag>
322
	Show contents of the routing table, possibly filtered by the filter. If you put <cf><m/prefix/</cf> on the line, only routes to given destination are shown. You can also make list more verbose by using <cf/all/ or limit routes to be shown to those from given protocol (using <cf/import_or_proto/).
323
	
324
	<tag>enable|disable|restart <m/name/|all</tag>
325
	Enable/disable or restart given protocol.
326

  
327
	<tag>debug <m/protocol/|<m/pattern/|all all|off|{ states | routes | filters | events | packets }
328
	Control protocol debugging.
329
</descrip>
312 330

  
313 331
<chapt>Filters
314 332

  
......
513 531
attribute result in a runtime error; you can check if an attribute is
514 532
defined using the <cf>defined( <m>attribute</m> )</cf> operator.
515 533

  
516
<!-- fixme: say which are read-only -->
517

  
518 534
<descrip>
519 535
	<tag><m/prefix/ net</tag>
520 536
	Network the route is talking about. Read-only. (See the section about routing tables.)
521 537

  
522 538
	<tag><m/enum/ scope</tag>
523
	Address scope of the network (<cf/SCOPE_HOST/ for addresses local to this host, <cf/SCOPE_LINK/ for those specific for a physical link, ... <!-- FIXME -->)
539
	Address scope of the network (<cf/SCOPE_HOST/ for addresses local to this host, <cf/SCOPE_LINK/ for those specific for a physical link, <cf/SCOPE_SITE/, <cf/SCOPE_ORGANIZATION/, <cf/SCOPE_UNIVERSE/)
524 540

  
525 541
	<tag><m/int/ preference</tag>
526 542
	Preference of the route. (See section about routing tables.)
......
877 893
<sect1>Introduction
878 894

  
879 895
<p>Open Shortest Path First (OSPF) is a quite complex interior gateway
880
protocol. The current IPv4 version (OSPFv2) is defined in RFC 2328
881
<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2328.txt">. It's a link
896
protocol. The current IPv4 version (OSPFv2) is defined in RFC 2328<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2328.txt">. It's a link
882 897
state (a.k.a. shortest path first) protocol -- Each router maintains a database
883 898
describing the autonomous system's topology. Each participating router
884 899
has an identical copy of the database and all routers run the same algorithm
......
1188 1203
counting to infinity is necessary, because it is slow. Due to infinity being 16, you can't use
1189 1204
RIP on networks where maximal distance is higher than 15 hosts. You can read more about rip at <HTMLURL
1190 1205
URL="http://www.ietf.org/html.charters/rip-charter.html" name="http://www.ietf.org/html.charters/rip-charter.html">. Both IPv4  
1191
(RFC ????<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc????.txt">)
1206
(RFC 1723<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc1723.txt">)
1192 1207
and IPv6 (RFC 2080<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2080.txt">) versions of RIP are supported by BIRD, historical RIPv1 (RFC 1058<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc1058.txt">)is
1193 1208
not currently supported. RIPv4 md5 authentication (RFC 2082<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2082.txt">) is supported.
1194 1209

  
......
1352 1367
LocalWords:  OS'es AS's multicast nolisten misconfigured UID blackhole MRTD
1353 1368
LocalWords:  uninstalls ethernets IP binutils ANYCAST anycast dest RTD ICMP rfc
1354 1369
LocalWords:  compat multicasts nonbroadcast pointopoint
1370
LocalWords:  Perl SIGHUP dd mm yy HH MM SS EXT IA UNICAST multihop Discriminator txt
1355 1371
 -->

Also available in: Unified diff