-This is ../../../doc/quagga.info, produced by makeinfo version 4.8 from
-../../../doc/quagga.texi.
+This is quagga.info, produced by makeinfo version 4.8 from quagga.texi.
Copyright (C) 1999-2005 Kunihiro Ishiguro, et al.
This file documents the Quagga Software Routing Suite which manages
common TCP/IP routing protocols.
- This is Edition 0.99.3, last updated 10 September 2005 of `The
-Quagga Manual', for Quagga Version 0.99.3.
+ This is Edition 0.99.4, last updated 10 September 2005 of `The
+Quagga Manual', for Quagga Version 0.99.4.
Copyright (C) 1999-2005 Kunihiro Ishiguro, et al.
******
Quagga is an advanced routing software package that provides a suite of
-TCP/IP based routing protocols. This is the Manual for Quagga 0.99.3.
+TCP/IP based routing protocols. This is the Manual for Quagga 0.99.4.
Quagga is a fork of GNU Zebra.
Copyright (C) 1999-2005 Kunihiro Ishiguro, et al.
Connected to localhost.
Escape character is '^]'.
- Hello, this is Quagga (version 0.99.3)
+ Hello, this is Quagga (version 0.99.4)
Copyright (C) 1999-2005 Kunihiro Ishiguro, et al.
User Access Verification
`--keep_kernel'
When zebra starts up, don't delete old self inserted routes.
-`-l'
-`--log_mode'
- Set verbose logging on.
-
`-r'
`--retain'
When program terminates, retain routes added by zebra.
* Starting and Stopping ripd::
* RIP Configuration::
+* RIP Version Control::
* How to Announce RIP route::
* Filtering RIP Routes::
* RIP Metric Manipulation::
equal cost multipath routing.
\1f
-File: quagga.info, Node: RIP Configuration, Next: How to Announce RIP route, Prev: Starting and Stopping ripd, Up: RIP
+File: quagga.info, Node: RIP Configuration, Next: RIP Version Control, Prev: Starting and Stopping ripd, Up: RIP
5.2 RIP Configuration
=====================
-- Command: no router rip
Disable RIP.
- RIP can be configured to process either Version 1 or Version 2
-packets, the default mode is Version 2. If no version is specified,
-then the RIP daemon will default to Version 2. If RIP is set to Version
-1, the setting "Version 1" will be displayed, but the setting "Version
-2" will not be displayed whether or not Version 2 is set explicitly as
-the version of RIP being used. The version can be specified globally,
-and also on a per-interface basis (see below).
-
- -- RIP Command: version VERSION
- Set RIP process's version. VERSION can be `1" or `2".
-
-- RIP Command: network NETWORK
-- RIP Command: no network NETWORK
Set the RIP enable interface by NETWORK. The interfaces which
The default is to be passive on all interfaces.
- RIP version handling
-
- -- Interface command: ip rip send version VERSION
- VERSION can be `1', `2', `1 2'. This configuration command
- overrides the router's rip version setting. The command will
- enable the selected interface to send packets with RIP Version 1,
- RIP Version 2, or both. In the case of '1 2', packets will be
- both broadcast and multicast.
-
- The default is to send only version 2.
-
- -- Interface command: ip rip receive version VERSION
- Version setting for incoming RIP packets. This command will
- enable the selected interface to receive packets in RIP Version 1,
- RIP Version 2, or both.
-
- The default is to receive both versions.
-
RIP split-horizon
-- Interface command: ip split-horizon
interface, please specify `no ip split-horizon'.
\1f
-File: quagga.info, Node: How to Announce RIP route, Next: Filtering RIP Routes, Prev: RIP Configuration, Up: RIP
+File: quagga.info, Node: RIP Version Control, Next: How to Announce RIP route, Prev: RIP Configuration, Up: RIP
+
+5.3 RIP Version Control
+=======================
+
+RIP can be configured to send either Version 1 or Version 2 packets.
+The default is to send RIPv2 while accepting both RIPv1 and RIPv2 (and
+replying with packets of the appropriate version for REQUESTS /
+triggered updates). The version to receive and send can be specified
+globally, and further overriden on a per-interface basis if needs be
+for send and receive seperately (see below).
+
+ It is important to note that RIPv1 can not be authenticated. Further,
+if RIPv1 is enabled then RIP will reply to REQUEST packets, sending the
+state of its RIP routing table to any remote routers that ask on
+demand. For a more detailed discussion on the security implications of
+RIPv1 see *Note RIP Authentication::.
+
+ -- RIP Command: version VERSION
+ Set RIP version to accept for reads and send. VERSION can be
+ either `1" or `2".
+
+ Disabling RIPv1 by specifying version 2 is STRONGLY encouraged,
+ *Note RIP Authentication::. This may become the default in a future
+ release.
+
+ Default: Send Version 2, and accept either version.
+
+ -- RIP Command: no version
+ Reset the global version setting back to the default.
+
+ -- Interface command: ip rip send version VERSION
+ VERSION can be `1', `2' or `1 2'.
+
+ This interface command overrides the global rip version setting,
+ and selects which version of RIP to send packets with, for this
+ interface specifically. Choice of RIP Version 1, RIP Version 2, or
+ both versions. In the latter case, where `1 2' is specified,
+ packets will be both broadcast and multicast.
+
+ Default: Send packets according to the global version (version 2)
+
+ -- Interface command: ip rip receive version VERSION
+ VERSION can be `1', `2' or `1 2'.
+
+ This interface command overrides the global rip version setting,
+ and selects which versions of RIP packets will be accepted on this
+ interface. Choice of RIP Version 1, RIP Version 2, or both.
+
+ Default: Accept packets according to the global setting (both 1
+ and 2).
+
+\1f
+File: quagga.info, Node: How to Announce RIP route, Next: Filtering RIP Routes, Prev: RIP Version Control, Up: RIP
-5.3 How to Announce RIP route
+5.4 How to Announce RIP route
=============================
-- RIP command: redistribute kernel
\1f
File: quagga.info, Node: Filtering RIP Routes, Next: RIP Metric Manipulation, Prev: How to Announce RIP route, Up: RIP
-5.4 Filtering RIP Routes
+5.5 Filtering RIP Routes
========================
RIP routes can be filtered by a distribute-list.
\1f
File: quagga.info, Node: RIP Metric Manipulation, Next: RIP distance, Prev: Filtering RIP Routes, Up: RIP
-5.5 RIP Metric Manipulation
+5.6 RIP Metric Manipulation
===========================
RIP metric is a value for distance for the network. Usually `ripd'
\1f
File: quagga.info, Node: RIP distance, Next: RIP route-map, Prev: RIP Metric Manipulation, Up: RIP
-5.6 RIP distance
+5.7 RIP distance
================
Distance value is used in zebra daemon. Default RIP distance is 120.
\1f
File: quagga.info, Node: RIP route-map, Next: RIP Authentication, Prev: RIP distance, Up: RIP
-5.7 RIP route-map
+5.8 RIP route-map
=================
Usage of `ripd''s route-map support.
\1f
File: quagga.info, Node: RIP Authentication, Next: RIP Timers, Prev: RIP route-map, Up: RIP
-5.8 RIP Authentication
+5.9 RIP Authentication
======================
+RIPv2 allows packets to be authenticated via either an insecure plain
+text password, included with the packet, or via a more secure MD5 based
+HMAC (keyed-Hashing for Message AuthentiCation), RIPv1 can not be
+authenticated at all, thus when authentication is configured `ripd'
+will discard routing updates received via RIPv1 packets.
+
+ However, unless RIPv1 reception is disabled entirely, *Note RIP
+Version Control::, RIPv1 REQUEST packets which are received, which
+query the router for routing information, will still be honoured by
+`ripd', and `ripd' WILL reply to such packets. This allows `ripd' to
+honour such REQUESTs (which sometimes is used by old equipment and very
+simple devices to bootstrap their default route), while still providing
+security for route updates which are received.
+
+ In short: Enabling authentication prevents routes being updated by
+unauthenticated remote routers, but still can allow routes (I.e. the
+entire RIP routing table) to be queried remotely, potentially by anyone
+on the internet, via RIPv1.
+
+ To prevent such unauthenticated querying of routes disable RIPv1,
+*Note RIP Version Control::.
+
-- Interface command: ip rip authentication mode md5
-- Interface command: no ip rip authentication mode md5
Set the interface with RIPv2 MD5 authentication.
\1f
File: quagga.info, Node: RIP Timers, Next: Show RIP Information, Prev: RIP Authentication, Up: RIP
-5.9 RIP Timers
-==============
+5.10 RIP Timers
+===============
-- RIP command: timers basic UPDATE TIMEOUT GARBAGE
RIP protocol has several timers. User can configure those timers'
\1f
File: quagga.info, Node: Show RIP Information, Next: RIP Debug Commands, Prev: RIP Timers, Up: RIP
-5.10 Show RIP Information
+5.11 Show RIP Information
=========================
To display RIP routes.
\1f
File: quagga.info, Node: RIP Debug Commands, Prev: Show RIP Information, Up: RIP
-5.11 RIP Debug Commands
+5.12 RIP Debug Commands
=======================
Debug for RIP protocol.
its attributes modified. Those routes which are accepted by the
`Out' filters of a peer are announced to that peer.
- Figure 10.1: Announcement processing inside a "normal" BGP speaker
- Figure 10.2: Full Mesh
+ _______________________________
+ / _________ _________ \
+From Peer A --->|(A)-|Best | | |-[A]|--->To Peer A
+From Peer B --->|(B)-|Path |-->|Local-RIB|-[B]|--->To Peer B
+From Peer C --->|(C)-|Selection| | |-[C]|--->To Peer C
+From Peer D --->|(D)-|_________| |_________|-[D]|--->To Peer D
+ \_______________________________/
+
+Key: (X) - 'In' Filter applied to Peer X's announcements
+ [X] - 'Out' Filter applied to announcements to Peer X
+
+Figure 10.1: Announcement processing inside a "normal" BGP speaker
+
+(RF1)--(RF2)
+ | \ / |
+ | \/ |
+ | /\ |
+ | / \ |
+(RF3)--(RF4)
+
+Figure 10.2: Full Mesh
+
+(RF1) (RF2)
+ \ /
+ [RS]
+ / \
+(RF3) (RF4)
- Figure 10.3: Route Server and clients
+Figure 10.3: Route Server and clients
Of course we want that the routing tables obtained in each of the
routers are the same when using the route server than when not. But as
previous announcements for the same destination. This is the expected
behavior of a BGP speaker as defined in `RFC1771', and even though
there are some proposals of mechanisms that permit multiple paths for
-the same destination to be sent through a single BGP peering, none of
-them are currently supported by most of the existing BGP
-implementations.
+the same destination to be sent through a single BGP peering, none are
+currently supported by most existing BGP implementations.
As a consequence a route server must maintain additional information
and perform additional tasks for a RS-client that those necessary for
not to remove them as they do not hurt anybody (they can always be
left empty).
-\0\b[image src="fig-rs-processing.png" alt="Route Server Processing Model"\0\b]
+\0\b[image src="fig-rs-processing.png" alt="Route Server Processing Model" text="From Peer A
+ | From RS-Client B
+ | | From RS-Client C
+ | | | From RS-Client D
+ | | | |
+ | | | | Main / Normal RIB
+ | | | | ________________________________
+ | | | | / _________ _________ \\
+ | | | +--->|(D)-|Best | | Main | |
+ | | +--|--->|(C)-|Path |-->|Local-RIB|->[A]|--->To Peer A
+ | +--|--|--->|(B)-|Selection| | | |
+ +--|--|--|--->|(A)-|_________| |_________| |
+ | | | | \\________________________________/
+ | | | |
+ | | | | ________________________________
+ | | | | / _________ _________ \\
+ | | | +--->*D*->|{B}-|Best | |RS-Client| |
+ | | +--|--->*C*->|{B}-|Path |-->|Local-RIB|->[B]|--->To RS-Client B
+ | | | | | |Selection| | for B | |
+ +--|--|--|-------->|{B}-|_________| |_________| |
+ | | | | \\________________________________/
+ | | | |
+ | | | | ________________________________
+ | | | | / _________ _________ \\
+ | | | +--->*D*->|{C}-|Best | |RS-Client| |
+ | | | | | |Path |-->|Local-RIB|->[C]|--->To RS-Client C
+ | +--|--|--->*B*->|{C}-|Selection| | for C | |
+ +--|--|--|-------->|{C}-|_________| |_________| |
+ | | | \\________________________________/
+ | | |
+ | | | ________________________________
+ | | | / _________ _________ \\
+ | | | | |Best | |RS-Client| |
+ | | +------>*C*->|{D}-|Path |-->|Local-RIB|->[D]|--->To RS-Client D
+ | +--------->*B*->|{D}-|Selection| | for D | |
+ +----------------->|{D}-|_________| |_________| |
+ \\________________________________/
+
+
+Key: (X) - 'In' Filter applied to Peer X's announcements before
+ considering announcement for the normal main Local-RIB
+ [X] - 'Out' Filter applied to announcements to Peer X
+ *X* - 'Export' Filter of RS-Client X, to apply X's policies
+ before its routes may be considered for other RS-Clients
+ RIBs.
+ {X} - 'Import' Filter of RS-Client X, to apply X's policies
+ on routes before allowing them into X's RIB.
+"\0\b]
Figure 10.4: Announcement processing model implemented by the Route Server
Appendix A Zebra Protocol
*************************
-Zebra Protocol is a protocol which is used between protocol daemon and
-zebra. Each protocol daemon sends selected routes to zebra daemon.
-Then zebra manages which route is installed into the forwarding table.
+A.1 Overview of the Zebra Protocol
+==================================
+
+Zebra Protocol is used by protocol daemons to communicate with the
+zebra daemon.
+
+ Each protocol daemon may request and send information to and from the
+zebra daemon such as interface states, routing state,
+nexthop-validation, and so on. Protocol daemons may also install routes
+with zebra. The zebra daemon manages which route is installed into the
+forwarding table with the kernel.
+
+ Zebra Protocol is a streaming protocol, with a common header. Two
+versions of the header are in use. Version 0 is implicitely versioned.
+Version 1 has an explicit version field. Version 0 can be distinguished
+from all other versions by examining the 3rd byte of the header, which
+contains a marker value for all versions bar version 0. The marker byte
+corresponds to the command field in version 0, and the marker value is
+a reserved command in version 0.
+
+ We do not anticipate there will be further versions of the header for
+the foreseeable future, as the command field in version 1 is wide
+enough to allow for future extensions to done compatibly through
+seperate commands.
+
+ Version 0 is used by all versions of GNU Zebra as of this writing,
+and versions of Quagga up to and including Quagga 0.98. Version 1 will
+be used as of Quagga 1.0.
+
+A.2 Zebra Protocol Definition
+=============================
- Zebra Protocol is a TCP-based protocol. Below is common header of
-Zebra Protocol.
+A.2.1 Zebra Protocol Header (version 0)
+---------------------------------------
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ +-------------------------------+---------------+
| Length (2) | Command (1) |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ +-------------------------------+---------------+
- Length is total packet length including this header length. So
-minimum length is three. Command is Zebra Protocol command.
-
- ZEBRA_INTERFACE_ADD 1
- ZEBRA_INTERFACE_DELETE 2
- ZEBRA_INTERFACE_ADDRESS_ADD 3
- ZEBRA_INTERFACE_ADDRESS_DELETE 4
- ZEBRA_INTERFACE_UP 5
- ZEBRA_INTERFACE_DOWN 6
- ZEBRA_IPV4_ROUTE_ADD 7
- ZEBRA_IPV4_ROUTE_DELETE 8
- ZEBRA_IPV6_ROUTE_ADD 9
- ZEBRA_IPV6_ROUTE_DELETE 10
- ZEBRA_REDISTRIBUTE_ADD 11
- ZEBRA_REDISTRIBUTE_DELETE 12
- ZEBRA_REDISTRIBUTE_DEFAULT_ADD 13
- ZEBRA_REDISTRIBUTE_DEFAULT_DELETE 14
- ZEBRA_IPV4_NEXTHOP_LOOKUP 15
- ZEBRA_IPV6_NEXTHOP_LOOKUP 16
+A.2.2 Zebra Protocol Common Header (version 1)
+----------------------------------------------
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- | Type | Flags |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ +-------------------------------+---------------+-------------+
+ | Length (2) | Marker (1) | Version (1) |
+ +-------------------------------+---------------+-------------+
+ | Command (2) |
+ +-------------------------------+
+
+A.2.3 Zebra Protocol Header Field Definitions
+---------------------------------------------
+
+`Length'
+ Total packet length including this header. The minimum length is 3
+ bytes for version 0 messages and 6 bytes for version 1 messages.
+
+`Marker'
+ Static marker with a value of 255 always. This is to allow version
+ 0 Zserv headers (which do not include version explicitely) to be
+ distinguished from versioned headers. Not present in version 0
+ messages.
+
+`Version'
+ Version number of the Zserv message. Clients should not continue
+ processing messages past the version field for versions they do not
+ recognise. Not present in version 0 messages.
+
+`Command'
+ The Zebra Protocol command.
+
+A.2.4 Zebra Protocol Commands
+-----------------------------
+
+Command Value
+-----------------------------------------------------
+ZEBRA_INTERFACE_ADD 1
+ZEBRA_INTERFACE_DELETE 2
+ZEBRA_INTERFACE_ADDRESS_ADD 3
+ZEBRA_INTERFACE_ADDRESS_DELETE 4
+ZEBRA_INTERFACE_UP 5
+ZEBRA_INTERFACE_DOWN 6
+ZEBRA_IPV4_ROUTE_ADD 7
+ZEBRA_IPV4_ROUTE_DELETE 8
+ZEBRA_IPV6_ROUTE_ADD 9
+ZEBRA_IPV6_ROUTE_DELETE 10
+ZEBRA_REDISTRIBUTE_ADD 11
+ZEBRA_REDISTRIBUTE_DELETE 12
+ZEBRA_REDISTRIBUTE_DEFAULT_ADD 13
+ZEBRA_REDISTRIBUTE_DEFAULT_DELETE 14
+ZEBRA_IPV4_NEXTHOP_LOOKUP 15
+ZEBRA_IPV6_NEXTHOP_LOOKUP 16
\1f
File: quagga.info, Node: Packet Binary Dump Format, Next: Command Index, Prev: Zebra Protocol, Up: Top
* ip prefix-list sequence-number: ip prefix-list sequential number control.
(line 7)
* ip rip authentication key-chain KEY-CHAIN: RIP Authentication.
- (line 21)
-* ip rip authentication mode md5: RIP Authentication. (line 7)
-* ip rip authentication mode text: RIP Authentication. (line 11)
-* ip rip authentication string STRING: RIP Authentication. (line 15)
-* ip rip receive version VERSION: RIP Configuration. (line 90)
-* ip rip send version VERSION: RIP Configuration. (line 81)
+ (line 43)
+* ip rip authentication mode md5: RIP Authentication. (line 29)
+* ip rip authentication mode text: RIP Authentication. (line 33)
+* ip rip authentication string STRING: RIP Authentication. (line 37)
+* ip rip receive version VERSION: RIP Version Control. (line 44)
+* ip rip send version VERSION: RIP Version Control. (line 33)
* ip route NETWORK GATEWAY: Static Route Commands.
(line 10)
* ip route NETWORK GATEWAY DISTANCE: Static Route Commands.
(line 36)
* ip route NETWORK NETMASK GATEWAY: Static Route Commands.
(line 25)
-* ip split-horizon: RIP Configuration. (line 99)
+* ip split-horizon: RIP Configuration. (line 70)
* ip6 address ADDRESS/PREFIX: Interface Commands. (line 14)
* ipv6 nd adv-interval-option: Router Advertisement.
(line 127)
* multicast: Interface Commands. (line 27)
* neigbor {A.B.C.D|X.X::X.X|peer-group} route-map WORD {import|export}: Commands for configuring a Route Server.
(line 29)
-* neighbor A.B.C.D: RIP Configuration. (line 45)
+* neighbor A.B.C.D: RIP Configuration. (line 34)
* neighbor A.B.C.D route-server-client: Commands for configuring a Route Server.
(line 11)
* neighbor PEER default-originate: BGP Peer commands. (line 47)
* network A.B.C.D/M area A.B.C.D: OSPF router. (line 154)
* network IFNAME <1>: ripngd Configuration.
(line 18)
-* network IFNAME: RIP Configuration. (line 38)
+* network IFNAME: RIP Configuration. (line 27)
* network NETWORK <1>: ripngd Configuration.
(line 15)
-* network NETWORK: RIP Configuration. (line 26)
+* network NETWORK: RIP Configuration. (line 15)
* no aggregate-address A.B.C.D/M: Route Aggregation. (line 18)
* no area <0-4294967295> authentication: OSPF area. (line 129)
* no area <0-4294967295> export-list NAME: OSPF area. (line 87)
* no ip prefix-list sequence-number: ip prefix-list sequential number control.
(line 11)
* no ip rip authentication key-chain KEY-CHAIN: RIP Authentication.
- (line 22)
-* no ip rip authentication mode md5: RIP Authentication. (line 8)
-* no ip rip authentication mode text: RIP Authentication. (line 12)
-* no ip rip authentication string STRING: RIP Authentication. (line 16)
-* no ip split-horizon: RIP Configuration. (line 100)
+ (line 44)
+* no ip rip authentication mode md5: RIP Authentication. (line 30)
+* no ip rip authentication mode text: RIP Authentication. (line 34)
+* no ip rip authentication string STRING: RIP Authentication. (line 38)
+* no ip split-horizon: RIP Configuration. (line 71)
* no ip6 address ADDRESS/PREFIX: Interface Commands. (line 16)
* no ipv6 nd adv-interval-option: Router Advertisement.
(line 128)
* no max-metric router-lsa [on-startup|on-shutdown|administrative]: OSPF router.
(line 113)
* no multicast: Interface Commands. (line 28)
-* no neighbor A.B.C.D: RIP Configuration. (line 46)
+* no neighbor A.B.C.D: RIP Configuration. (line 35)
* no neighbor PEER default-originate: BGP Peer commands. (line 48)
* no neighbor PEER description ...: BGP Peer commands. (line 21)
* no neighbor PEER dont-capability-negotiate: Capability Negotiation.
* no network A.B.C.D/M: BGP route. (line 17)
* no network A.B.C.D/M area <0-4294967295>: OSPF router. (line 157)
* no network A.B.C.D/M area A.B.C.D: OSPF router. (line 156)
-* no network IFNAME: RIP Configuration. (line 39)
-* no network NETWORK: RIP Configuration. (line 27)
+* no network IFNAME: RIP Configuration. (line 28)
+* no network NETWORK: RIP Configuration. (line 16)
* no ospf abr-type TYPE: OSPF router. (line 27)
* no ospf rfc1583compatibility: OSPF router. (line 49)
* no ospf router-id: OSPF router. (line 17)
* no passive interface INTERFACE: OSPF router. (line 60)
-* no passive-interface IFNAME: RIP Configuration. (line 69)
+* no passive-interface IFNAME: RIP Configuration. (line 58)
* no redistribute (kernel|connected|static|rip|bgp): Redistribute routes to OSPF.
(line 22)
* no redistribute bgp: How to Announce RIP route.
(line 32)
* no timers basic: RIP Timers. (line 31)
* no timers throttle spf: OSPF router. (line 72)
+* no version: RIP Version Control. (line 30)
* offset-list ACCESS-LIST (in|out): RIP Metric Manipulation.
(line 20)
* offset-list ACCESS-LIST (in|out) IFNAME: RIP Metric Manipulation.
* ospf rfc1583compatibility: OSPF router. (line 48)
* ospf router-id A.B.C.D: OSPF router. (line 16)
* passive interface INTERFACE: OSPF router. (line 59)
-* passive-interface (IFNAME|default): RIP Configuration. (line 68)
+* passive-interface (IFNAME|default): RIP Configuration. (line 57)
* password PASSWORD: Basic Config Commands.
(line 10)
* redistribute (kernel|connected|static|rip|bgp): Redistribute routes to OSPF.
* timers throttle spf DELAY INITIAL-HOLDTIME MAX-HOLDTIME: OSPF router.
(line 71)
* username USERNAME nopassword: VTY shell username. (line 7)
-* version VERSION: RIP Configuration. (line 23)
+* version VERSION: RIP Version Control. (line 20)
* who: Terminal Mode Commands.
(line 21)
* write file: Terminal Mode Commands.
Node: CLI Advanced Commands\7f39432
Node: Zebra\7f40198
Node: Invoking zebra\7f40707
-Node: Interface Commands\7f41286
-Node: Static Route Commands\7f42818
-Node: zebra Terminal Mode Commands\7f46091
-Node: RIP\7f47056
-Node: Starting and Stopping ripd\7f47993
-Node: RIP netmask\7f49406
-Node: RIP Configuration\7f50505
-Node: How to Announce RIP route\7f54770
-Node: Filtering RIP Routes\7f57333
-Node: RIP Metric Manipulation\7f58800
-Node: RIP distance\7f59713
-Node: RIP route-map\7f60528
-Node: RIP Authentication\7f63044
-Node: RIP Timers\7f64151
-Node: Show RIP Information\7f65437
-Node: RIP Debug Commands\7f66810
-Node: RIPng\7f67806
-Node: Invoking ripngd\7f68126
-Node: ripngd Configuration\7f68375
-Node: ripngd Terminal Mode Commands\7f69126
-Node: ripngd Filtering Commands\7f69490
-Node: OSPFv2\7f69999
-Node: Configuring ospfd\7f70651
-Node: OSPF router\7f71199
-Node: OSPF area\7f79525
-Node: OSPF interface\7f85650
-Ref: ip ospf dead-interval minimal\7f87219
-Node: Redistribute routes to OSPF\7f89791
-Node: Showing OSPF information\7f92449
-Ref: show ip ospf\7f92634
-Node: Debugging OSPF\7f93965
-Node: OSPF Configuration Examples\7f95040
-Node: OSPFv3\7f96410
-Node: OSPF6 router\7f96763
-Node: OSPF6 area\7f97117
-Node: OSPF6 interface\7f97295
-Node: Redistribute routes to OSPF6\7f98172
-Node: Showing OSPF6 information\7f98488
-Node: OSPF6 Configuration Examples\7f99345
-Node: BGP\7f99766
-Node: Starting BGP\7f100688
-Node: BGP router\7f101265
-Node: BGP distance\7f102509
-Node: BGP decision process\7f102947
-Node: BGP network\7f103429
-Node: BGP route\7f103619
-Node: Route Aggregation\7f104175
-Node: Redistribute to BGP\7f104744
-Node: BGP Peer\7f105271
-Node: Defining Peer\7f105458
-Node: BGP Peer commands\7f106071
-Node: Peer filtering\7f108475
-Node: BGP Peer Group\7f108983
-Node: BGP Address Family\7f109296
-Node: Autonomous System\7f109450
-Node: AS Path Regular Expression\7f110327
-Node: Display BGP Routes by AS Path\7f111574
-Node: AS Path Access List\7f112014
-Node: Using AS Path in Route Map\7f112481
-Node: Private AS Numbers\7f112762
-Node: BGP Communities Attribute\7f112920
-Node: BGP Community Lists\7f115381
-Node: Numbered BGP Community Lists\7f118035
-Node: BGP Community in Route Map\7f119622
-Node: Display BGP Routes by Community\7f121565
-Node: Using BGP Communities Attribute\7f122734
-Node: BGP Extended Communities Attribute\7f126302
-Node: BGP Extended Community Lists\7f128074
-Node: BGP Extended Communities in Route Map\7f129949
-Node: Displaying BGP routes\7f130408
-Node: Show IP BGP\7f130645
-Node: More Show IP BGP\7f131345
-Node: Capability Negotiation\7f132496
-Node: Route Reflector\7f135968
-Node: Route Server\7f136247
-Node: Multiple instance\7f137313
-Node: BGP instance and view\7f139158
-Node: Routing policy\7f140538
-Node: Viewing the view\7f141306
-Node: How to set up a 6-Bone connection\7f141591
-Node: Dump BGP packets and table\7f142963
-Node: BGP Configuration Examples\7f143545
-Node: Configuring Quagga as a Route Server\7f152496
-Node: Description of the Route Server model\7f153457
-Ref: fig:normal-processing\7f155034
-Ref: fig:full-mesh\7f155103
-Ref: fig:route-server\7f155128
-Ref: filter-delegation\7f155470
-Ref: Route Server tasks\7f156654
-Ref: Route-server path filter process\7f157025
-Ref: fig:rs-processing\7f159339
-Node: Commands for configuring a Route Server\7f159492
-Node: Example of Route Server Configuration\7f162519
-Node: Configuration of the BGP routers without Route Server\7f163440
-Node: Configuration of the BGP routers with Route Server\7f166323
-Node: Configuration of the Route Server itself\7f167624
-Node: Further considerations about Import and Export route-maps\7f172623
-Node: VTY shell\7f175667
-Node: VTY shell username\7f176336
-Node: VTY shell integrated configuration\7f176968
-Node: Filtering\7f178416
-Node: IP Access List\7f178769
-Node: IP Prefix List\7f179155
-Node: ip prefix-list description\7f182174
-Node: ip prefix-list sequential number control\7f182701
-Node: Showing ip prefix-list\7f183243
-Node: Clear counter of ip prefix-list\7f184351
-Node: Route Map\7f184790
-Node: Route Map Command\7f188235
-Node: Route Map Match Command\7f188544
-Node: Route Map Set Command\7f189168
-Node: Route Map Call Command\7f190076
-Node: Route Map Exit Action Command\7f190406
-Node: Route Map Examples\7f190888
-Node: IPv6 Support\7f191400
-Node: Router Advertisement\7f191972
-Node: Kernel Interface\7f197588
-Node: SNMP Support\7f199545
-Node: Getting and installing an SNMP agent\7f200144
-Node: SMUX configuration\7f200717
-Node: MIB and command reference\7f202853
-Node: Handling SNMP Traps\7f204268
-Node: Zebra Protocol\7f210347
-Node: Packet Binary Dump Format\7f212261
-Node: Command Index\7f223871
-Node: VTY Key Index\7f282532
+Node: Interface Commands\7f41238
+Node: Static Route Commands\7f42770
+Node: zebra Terminal Mode Commands\7f46043
+Node: RIP\7f47008
+Node: Starting and Stopping ripd\7f47969
+Node: RIP netmask\7f49382
+Node: RIP Configuration\7f50481
+Node: RIP Version Control\7f53481
+Node: How to Announce RIP route\7f55663
+Node: Filtering RIP Routes\7f58228
+Node: RIP Metric Manipulation\7f59695
+Node: RIP distance\7f60608
+Node: RIP route-map\7f61423
+Node: RIP Authentication\7f63939
+Node: RIP Timers\7f66182
+Node: Show RIP Information\7f67470
+Node: RIP Debug Commands\7f68843
+Node: RIPng\7f69839
+Node: Invoking ripngd\7f70159
+Node: ripngd Configuration\7f70408
+Node: ripngd Terminal Mode Commands\7f71159
+Node: ripngd Filtering Commands\7f71523
+Node: OSPFv2\7f72032
+Node: Configuring ospfd\7f72684
+Node: OSPF router\7f73232
+Node: OSPF area\7f81558
+Node: OSPF interface\7f87683
+Ref: ip ospf dead-interval minimal\7f89252
+Node: Redistribute routes to OSPF\7f91824
+Node: Showing OSPF information\7f94482
+Ref: show ip ospf\7f94667
+Node: Debugging OSPF\7f95998
+Node: OSPF Configuration Examples\7f97073
+Node: OSPFv3\7f98443
+Node: OSPF6 router\7f98796
+Node: OSPF6 area\7f99150
+Node: OSPF6 interface\7f99328
+Node: Redistribute routes to OSPF6\7f100205
+Node: Showing OSPF6 information\7f100521
+Node: OSPF6 Configuration Examples\7f101378
+Node: BGP\7f101799
+Node: Starting BGP\7f102721
+Node: BGP router\7f103298
+Node: BGP distance\7f104542
+Node: BGP decision process\7f104980
+Node: BGP network\7f105462
+Node: BGP route\7f105652
+Node: Route Aggregation\7f106208
+Node: Redistribute to BGP\7f106777
+Node: BGP Peer\7f107304
+Node: Defining Peer\7f107491
+Node: BGP Peer commands\7f108104
+Node: Peer filtering\7f110508
+Node: BGP Peer Group\7f111016
+Node: BGP Address Family\7f111329
+Node: Autonomous System\7f111483
+Node: AS Path Regular Expression\7f112360
+Node: Display BGP Routes by AS Path\7f113607
+Node: AS Path Access List\7f114047
+Node: Using AS Path in Route Map\7f114514
+Node: Private AS Numbers\7f114795
+Node: BGP Communities Attribute\7f114953
+Node: BGP Community Lists\7f117414
+Node: Numbered BGP Community Lists\7f120068
+Node: BGP Community in Route Map\7f121655
+Node: Display BGP Routes by Community\7f123598
+Node: Using BGP Communities Attribute\7f124767
+Node: BGP Extended Communities Attribute\7f128335
+Node: BGP Extended Community Lists\7f130107
+Node: BGP Extended Communities in Route Map\7f131982
+Node: Displaying BGP routes\7f132441
+Node: Show IP BGP\7f132678
+Node: More Show IP BGP\7f133378
+Node: Capability Negotiation\7f134529
+Node: Route Reflector\7f138001
+Node: Route Server\7f138280
+Node: Multiple instance\7f139346
+Node: BGP instance and view\7f141191
+Node: Routing policy\7f142571
+Node: Viewing the view\7f143339
+Node: How to set up a 6-Bone connection\7f143624
+Node: Dump BGP packets and table\7f144996
+Node: BGP Configuration Examples\7f145578
+Node: Configuring Quagga as a Route Server\7f154529
+Node: Description of the Route Server model\7f155490
+Ref: fig:normal-processing\7f157067
+Ref: fig:full-mesh\7f157669
+Ref: fig:route-server\7f157764
+Ref: filter-delegation\7f158159
+Ref: Route Server tasks\7f159328
+Ref: Route-server path filter process\7f159699
+Ref: fig:rs-processing\7f162013
+Node: Commands for configuring a Route Server\7f164422
+Node: Example of Route Server Configuration\7f167449
+Node: Configuration of the BGP routers without Route Server\7f168370
+Node: Configuration of the BGP routers with Route Server\7f171253
+Node: Configuration of the Route Server itself\7f172554
+Node: Further considerations about Import and Export route-maps\7f177553
+Node: VTY shell\7f180597
+Node: VTY shell username\7f181266
+Node: VTY shell integrated configuration\7f181898
+Node: Filtering\7f183346
+Node: IP Access List\7f183699
+Node: IP Prefix List\7f184085
+Node: ip prefix-list description\7f187104
+Node: ip prefix-list sequential number control\7f187631
+Node: Showing ip prefix-list\7f188173
+Node: Clear counter of ip prefix-list\7f189281
+Node: Route Map\7f189720
+Node: Route Map Command\7f193165
+Node: Route Map Match Command\7f193474
+Node: Route Map Set Command\7f194098
+Node: Route Map Call Command\7f195006
+Node: Route Map Exit Action Command\7f195336
+Node: Route Map Examples\7f195818
+Node: IPv6 Support\7f196330
+Node: Router Advertisement\7f196902
+Node: Kernel Interface\7f202518
+Node: SNMP Support\7f204475
+Node: Getting and installing an SNMP agent\7f205074
+Node: SMUX configuration\7f205647
+Node: MIB and command reference\7f207783
+Node: Handling SNMP Traps\7f209198
+Node: Zebra Protocol\7f215277
+Node: Packet Binary Dump Format\7f219366
+Node: Command Index\7f230976
+Node: VTY Key Index\7f289710
\1f
End Tag Table
projects / mirror / frr.git / commitdiff