Makefile.in
draft-zebra-00.txt
zebra.info-*
+zebra.html
machine can be used to collect differing routing views from differing
points in the network.
+@item -A @var{address}
+@itemx --vty_addr=@var{address}
+Set the VTY local address to bind to. If set, the VTY socket will only
+be bound to this address.
+
@item -P @var{port}
@itemx --vty_port=@var{port}
-Set the VTY port number.
+Set the VTY TCP port number. If set to 0 then the TCP VTY sockets will not
+be opened.
+
+@item -u @var{user}
+@itemx --vty_addr=@var{user}
+Set the user and group to run as.
@item -v
@itemx --version
not turn on netlink support.
@item --enable-snmp
Enable SNMP support. By default, SNMP support is disabled.
+@item --enable-nssa
+Enable support for Not So Stubby Area (see RC3101) in ospfd.
+@item --enable-opaque-lsa
+Enable support for Opaque LSAs (RFC2370) in ospfd.
+@item --disable-ospfapi
+Disable support for OSPF-API, an API to interface directly with ospfd.
+OSPF-API is enabled if --enable-opaque-lsa is set.
+@item --disable-ospfclient
+Disable building of the example OSPF-API client.
+@item --enable-ospf-te
+Enable support for OSPF Traffic Engineering Extension (internet-draft) this
+requires support for Opaque LSAs.
+@item --enable-multipath=@var{ARG}
+Enable support for Equal Cost Multipath. @var{ARG} is the maximum number
+of ECMP paths to allow, set to 0 to allow unlimited number of paths.
+@item --enable-rtadv
+Enable support IPV6 router advertisement in zebra.
@end table
You may specify any combination of the above options to the configure
@item --prefix=@var{prefix}
Install architecture-independent files in @var{prefix} [/usr/local].
@item --sysconfdir=@var{dir}
-Read-only sample configuration file in @var{dir} [@var{prefix}/etc].
+Look for configuration files in @var{dir} [@var{prefix}/etc]. Note
+that sample configuration files will be installed here.
+@item --localstatedir=@var{dir}
+Configure zebra to use @var{dir} for local state files, such
+as pid files and unix sockets.
@end table
+Additionally, you may configure zebra to drop its elevated
+privileges shortly after startup and switch
+to another user, there are three configure options
+to control zebra's behaviour.
+
+@table @option
+@item --enable-user=@var{user}
+Switch to user @var{ARG} shortly after startup, and run as user @var{ARG}
+in normal operation.
+@item --enable-group=@var{group}
+Switch real and effective group to @var{group} shortly after
+startup.
+@item --enable-vty-group=@var{group}
+Create Unix Vty sockets (for use with vtysh) with group owndership set to
+@var{group}. This allows one to create a seperate group which is
+restricted to accessing only the Vty sockets, hence allowing one to
+delegate this group to individual users, or to run vtysh setgid to
+this group.
+@end table
+
+The default user and group which will be configured is 'zebra' if no user
+or group is specified. Note that this user or group requires write access
+to the local state directory (see --localstatedir) and requires at least
+read access, and write access if you wish to allow daemons
+to write out their configuration, to the configuration directory
+(see --sysconfdir).
+
+On systems which have the 'libcap' capabilities manipulation library
+(currently only linux), the zebra system will retain
+only minimal capabilities required, further it will only raise these
+capabilities for brief periods. On systems without libcap, zebra will run
+as the user specified and only raise its uid back to uid 0 for brief
+periods.
+
@example
% ./configure --disable-ipv6
@end example
Up or down the current interface.
@end deffn
-@deffn {Interface Command} {ip address @var{address}} {}
-Set ip address for the interface.
+@deffn {Interface Command} {ip address @var{address/prefix}} {}
+@deffnx {Interface Command} {ip6 address @var{address/prefix}} {}
+@deffnx {Interface Command} {no ip address @var{address/prefix}} {}
+@deffnx {Interface Command} {no ip6 address @var{address/prefix}} {}
+Set the IPv4 or IPv6 address/prefix for the interface.
+@end deffn
+
+@deffn {Interface Command} {ip address @var{address/prefix} secondary} {}
+@deffnx {Interface Command} {no ip address @var{address/prefix} secondary} {}
+Set the secondary flag for this address. This causes ospfd to not treat the
+address as a distinct subnet.
@end deffn
@deffn {Interface Command} {description @var{description} ...} {}
@deffn {Interface Command} {bandwidth <1-10000000>} {}
@deffnx {Interface Command} {no bandwidth <1-10000000>} {}
-Set bandwidth value to the interface. This is for calculating OSPF
-cost. This command does not affect the actual device configuration.
+Set bandwidth value of the interface in kilobits/sec. This is for
+calculating OSPF cost. This command does not affect the actual device
+configuration.
+@end deffn
+
+@deffn {Interface Command} {link-detect} {}
+@deffnx {Interface Command} {no link-detect} {}
+Enable/disable link-detect on platforms which support this. Currently
+only linux and with certain drivers - those which properly support the
+IFF_RUNNING flag.
@end deffn
@node Static Route Commands, zebra Terminal Mode Commands, Interface Commands, Zebra
@var{network} is destination prefix with format of A.B.C.D/M.
@var{gateway} is gateway for the prefix. When @var{gateway} is
A.B.C.D format. It is taken as a IPv4 address gateway. Otherwise it
-is treated as an interface name.
+is treated as an interface name. If the interface name is @var{null0} then
+zebra installs a blackhole route.
@example
ip route 10.0.0.0/8 10.0.0.2
ip route 10.0.0.0/8 ppp0
+ip route 10.0.0.0/8 null0
@end example
First example defines 10.0.0.0/8 static route with gateway 10.0.0.2.
-Second one defines the same prefix but with gateway to interface ppp0.
+Second one defines the same prefix but with gateway to interface ppp0. The
+third install a blackhole route.
@end deffn
@deffn Command {ip route @var{network} @var{netmask} @var{gateway}} {}
@example
ip route 10.0.0.0 255.255.255.0 10.0.0.2
ip route 10.0.0.0 255.255.255.0 ppp0
+ip route 10.0.0.0 255.255.255.0 null0
@end example
-This is a same setting using this statement.
+These statements are equivalent to those in the previous example.
@end deffn
@deffn Command {ip route @var{network} @var{gateway} @var{distance}} {}
-
+Installs the route with the specified distance.
@end deffn
Multiple nexthop static route
If there is no route to 10.0.0.2 and 10.0.0.3, and interface eth0
is reachable, then the last route is installed into the kernel.
+If zebra has been compiled with multipath support, and both 10.0.0.2 and
+10.0.0.3 are reachable, zebra will install a multipath route via both
+nexthops, if the platform supports this.
+
@example
zebra> show ip route
S> 10.0.0.1/32 [1/0] via 10.0.0.2 inactive
* is directly connected, eth0
@end example
-Floating static route
-
-@deffn Command {ipv6 route @var{network} @var{gateway}} {}
+@example
+ip route 10.0.0.0/8 10.0.0.2
+ip route 10.0.0.0/8 10.0.0.3
+ip route 10.0.0.0/8 null0 255
+@end example
-@end deffn
+This will install a multihop route via the specified next-hops if they are
+reachable, as well as a high-metric blackhole route, which can be useful to
+prevent traffic destined for a prefix to match less-specific routes (eg
+default) should the specified gateways not be reachable. Eg:
-@deffn Command {ipv6 route @var{network} @var{gateway} @var{distance}} {}
+@example
+zebra> show ip route 10.0.0.0/8
+Routing entry for 10.0.0.0/8
+ Known via "static", distance 1, metric 0
+ 10.0.0.2 inactive
+ 10.0.0.3 inactive
+
+Routing entry for 10.0.0.0/8
+ Known via "static", distance 255, metric 0
+ directly connected, Null0
+@end example
+@deffn Command {ipv6 route @var{network} @var{gateway}} {}
+@deffnx Command {ipv6 route @var{network} @var{gateway} @var{distance}} {}
+These behave similarly to their ipv4 counterparts.
@end deffn
@comment node-name, next, previous, up
@section How to get Zebra
- Zebra is still beta software and there is no officially
-released version. So currently Zebra is distributed from Zebra beta ftp
-site located at:
-
-@url{ftp://ftp.zebra.org/pub/zebra}
-
- Once Zebra is released you can get it from @sc{gnu} FTP site and
-its mirror sites. We are planning Zebra-1.0 as the first released
-version.
+ Zebra is still beta software and there is no officially released
+version. Once Zebra is released you can get it from @sc{gnu} FTP
+site and its mirror sites. We are planning Zebra-1.0 as the first
+released version.
Zebra's official web page is located at:
@url{http://www.gnu.org/software/zebra/zebra.html}.
- There is a Zebra beta tester web page at:
+ The original Zebra web site is located at:
@url{http://www.zebra.org/}.
- You can get the latest beta software information from this page.
+ As of this writing, development by zebra.org on Zebra has slowed down.
+There is some work being done by third-parties to try maintain bug-fixes and
+enhancements to the current Zebra code-base. Please see:
+
+@url{http://zebra.dishone.st/}.
+
+for further information, as well as links to additional zebra resources.
@node Mailing List, Bug Reports, How to get Zebra, Overview
@comment node-name, next, previous, up
unsubscribe zebra
@end quotation
+ There is an additional mailing list, @email{znog@@dishone.st,ZNOG} for
+discussion of zebra related issues and network operation. To subscribe
+send an email to @email{znog-subscribe@@dishone.st} with a message body that
+includes only:
+
+@quotation
+subscribe znog
+@end quotation
+
+ To unsubscribe, send an email to @email{znog-unsubscribe@@dishone.st}
+with a message body that includes only:
+
+@quotation
+unsubscribe znog
+@end quotation
+
+ Alternatively, you may use the web interface located at
+@url{http://www.dishone.st/mailman/listinfo/znog}. Links to archives of the
+znog list are available at this URL.
+
@node Bug Reports, , Mailing List, Overview
@comment node-name, next, previous, up
@section Bug Reports
carrying out any of the RIP commands.
@end deffn
-@deffn Command {no rouer rip} {}
+@deffn Command {no router rip} {}
Disable RIP.
@end deffn
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 of RIP being used. The version can be specified globally, and
+also on a per-interface basis (see below).
+
+@deffn {RIP Command} {version @var{version}} {}
+Set RIP process's version. @var{version} can be `1'' or `2''.
+@end deffn
@deffn {RIP Command} {network @var{network}} {}
@deffnx {RIP Command} {no network @var{network}} {}
Passive interface
-@deffn {RIP command} {passive-interface @var{IFNAME}} {}
+@deffn {RIP command} {passive-interface (@var{IFNAME}|default)} {}
@deffnx {RIP command} {no passive-interface @var{IFNAME}} {}
This command sets the specified interface to passive mode. On passive mode
interface, all receiving packets are processed as normal and ripd does
not send either multicast or unicast RIP packets except to RIP neighbors
-specified with @code{neighbor} command.
+specified with @code{neighbor} command. The interface may be specified
+as @var{default} to make ripd default to passive on all interfaces.
+
+The default is to be passive on all interfaces.
@end deffn
RIP version handling
-@deffn {RIP Command} {version @var{version}} {}
-Set RIP process's version. @var{version} can be ``1'' or ``2''.
-@end deffn
-
@deffn {Interface command} {ip rip send version @var{version}} {}
@var{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.
@end deffn
@deffn {Interface command} {ip rip receive version @var{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.
@end deffn
RIP split-horizon
directory for configuration file because the file includes user
authentication settings.
-Currently, vtysh.conf has only one command.
+Currently, vtysh.conf has only two commands.
-@example
-!
-username foo nopassword
-!
-@end example
+@deffn {Command} {username @var{username} nopassword} {}
With this set, user foo does not need password authentication for user vtysh.
With PAM vtysh uses PAM authentication mechanism.
If vtysh is compiled without PAM authentication, every user can use vtysh
-without authentication.
+without authentication. vtysh requires read/write permission
+to the various daemons vty sockets, this can be accomplished through use
+of unix groups and the --enable-vty-group configure option.
+
+@end deffn
+
+@deffn {Command} {write-conf daemon} {}
+Instruct daemons to write out their config files when 'write file'
+is issued.
+@end deffn
+@deffn {Command} {write-conf integrated} {}
+Write out integrated Zebra.conf file when 'write file' is issued.
+@end deffn
+
+This command controls the behaviour of vtysh when it is told
+to write out the configuration. If @command{write-conf integrated} is
+set, the daemon will write out a Zebra.conf with all daemons' commands
+integrated into it. If @command{write-conf daemon} is set, vtysh
+will instruct each daemon to write out their config files.
+
+Vtysh per default behaves as if @command{write-conf daemon} is set. Note
+that both may be set at same time if one wishes to have both
+Zebra.conf and daemon specific files written out. Further, note that the
+daemons are hard-coded to first look for the integrated Zebra.conf
+file before looking for their own file.
+
+We recommend you do not mix the use of the two types of files.
+Further, it is better not to use the integrated Zebra.conf file,
+as any syntax error in it can lead to /all/ of your daemons being unable
+to start up. Per daemon files are more robust as impact of errors in
+configuration are limited to the daemon in whose file the error is made.
-This is zebra.info, produced by makeinfo version 4.2 from zebra.texi.
+This is zebra.info, produced by makeinfo version 4.3 from zebra.texi.
INFO-DIR-SECTION Routing Software:
START-INFO-DIR-ENTRY
This file documents the GNU Zebra software which manages common
TCP/IP routing protocols.
- This is Edition 0.1, last updated 12 September 2002 of `The GNU
-Zebra Manual', for Zebra Version 0.93b.
+ This is Edition 0.1, last updated 26 January 2003 of `The GNU Zebra
+Manual', for Zebra Version 0.94.
Copyright (C) 1999, 2000, 2001, 2002 Kunihiro Ishiguro
\1f
Indirect:
-zebra.info-1: 1121
-zebra.info-2: 48818
-zebra.info-3: 95581
-zebra.info-4: 143934
+zebra.info-1: 1118
+zebra.info-2: 48684
+zebra.info-3: 97595
+zebra.info-4: 140430
\1f
Tag Table:
(Indirect)
-Node: Top\7f1121
-Node: Overview\7f1646
-Node: About Zebra\7f3063
-Node: System Architecture\7f5332
-Node: Supported Platforms\7f8330
-Node: Supported RFC\7f9317
-Node: How to get Zebra\7f11119
-Node: Mailing List\7f11824
-Node: Bug Reports\7f12491
-Node: Installation\7f13336
-Node: Configure the Software\7f13767
-Ref: Configure the Software-Footnote-1\7f16134
-Node: Build the Software\7f17776
-Node: Install the Software\7f18318
-Node: Basic commands\7f19689
-Node: Config Commands\7f20402
-Node: Basic Config Commands\7f21284
-Node: Sample Config File\7f23682
-Node: Common Invocation Options\7f24442
-Node: Virtual Terminal Interfaces\7f25564
-Node: VTY Overview\7f26069
-Node: VTY Modes\7f27353
-Node: VTY View Mode\7f27793
-Node: VTY Enable Mode\7f28047
-Node: VTY Other Modes\7f28311
-Node: VTY CLI Commands\7f28473
-Node: CLI Movement Commands\7f28923
-Node: CLI Editing Commands\7f29456
-Node: CLI Advanced Commands\7f30029
-Node: Zebra\7f30780
-Node: Invoking zebra\7f31287
-Node: Interface Commands\7f31873
-Node: Static Route Commands\7f32703
-Node: zebra Terminal Mode Commands\7f34790
-Node: RIP\7f35751
-Node: Starting and Stopping ripd\7f36686
-Node: RIP netmask\7f38107
-Node: RIP Configuration\7f39229
-Node: How to Announce RIP route\7f43124
-Node: Filtering RIP Routes\7f45653
-Node: RIP Metric Manipulation\7f47112
-Node: RIP distance\7f48015
-Node: RIP route-map\7f48818
-Node: RIP Authentication\7f51320
-Node: RIP Timers\7f52410
-Node: Show RIP Information\7f53685
-Node: RIP Debug Commands\7f55048
-Node: RIPng\7f56032
-Node: Invoking ripngd\7f56350
-Node: ripngd Configuration\7f56607
-Node: ripngd Terminal Mode Commands\7f57346
-Node: ripngd Filtering Commands\7f57696
-Node: OSPFv2\7f58195
-Node: Configuring ospfd\7f58752
-Node: OSPF router\7f59229
-Node: OSPF area\7f60960
-Node: OSPF interface\7f63174
-Node: Redistribute routes to OSPF\7f65956
-Node: Showing OSPF information\7f68072
-Node: Debugging OSPF\7f69292
-Node: OSPFv3\7f70303
-Node: OSPF6 router\7f70621
-Node: OSPF6 area\7f70978
-Node: OSPF6 interface\7f71150
-Node: Redistribute routes to OSPF6\7f72002
-Node: Showing OSPF6 information\7f72306
-Node: BGP\7f73111
-Node: Starting BGP\7f73972
-Node: BGP router\7f74557
-Node: BGP distance\7f75793
-Node: BGP decision process\7f76234
-Node: BGP network\7f76490
-Node: BGP route\7f76671
-Node: Route Aggregation\7f77232
-Node: Redistribute to BGP\7f77784
-Node: BGP Peer\7f78293
-Node: Defining Peer\7f78471
-Node: BGP Peer commands\7f79087
-Node: Peer filtering\7f81458
-Node: BGP Peer Group\7f81949
-Node: BGP Address Family\7f82251
-Node: Autonomous System\7f82396
-Node: AS Path Regular Expression\7f83227
-Node: Display BGP Routes by AS Path\7f84490
-Node: AS Path Access List\7f84919
-Node: Using AS Path in Route Map\7f85373
-Node: Private AS Numbers\7f85639
-Node: BGP Communities Attribute\7f85784
-Node: BGP Community Lists\7f88245
-Node: Numbered BGP Community Lists\7f90926
-Node: BGP Community in Route Map\7f92500
-Node: Display BGP Routes by Community\7f94427
-Node: Using BGP Communities Attribute\7f95581
-Node: BGP Extended Communities Attribute\7f99139
-Node: BGP Extended Community Lists\7f100905
-Node: BGP Extended Communities in Route Map\7f102806
-Node: Displaying BGP routes\7f103249
-Node: Show IP BGP\7f103475
-Node: More Show IP BGP\7f104197
-Node: Capability Negotiation\7f105317
-Node: Route Reflector\7f108605
-Node: Route Server\7f108870
-Node: Multiple instance\7f109928
-Node: BGP instance and view\7f111741
-Node: Routing policy\7f113107
-Node: Viewing the view\7f113863
-Node: How to set up a 6-Bone connection\7f114135
-Node: Dump BGP packets and table\7f115507
-Node: VTY shell\7f116037
-Node: Filtering\7f116877
-Node: IP Access List\7f117225
-Node: IP Prefix List\7f117616
-Node: ip prefix-list description\7f120785
-Node: ip prefix-list sequential number control\7f121318
-Node: Showing ip prefix-list\7f121843
-Node: Clear counter of ip prefix-list\7f122926
-Node: Route Map\7f123347
-Node: Route Map Command\7f123848
-Node: Route Map Match Command\7f124051
-Node: Route Map Set Command\7f124659
-Node: IPv6 Support\7f125517
-Node: Router Advertisement\7f126082
-Node: Kernel Interface\7f126413
-Node: SNMP Support\7f128363
-Node: How to get ucd-snmp\7f128992
-Node: SMUX configuration\7f130040
-Node: Zebra Protocol\7f130473
-Node: Packet Binary Dump Format\7f132367
-Node: Command Index\7f143934
-Node: VTY Key Index\7f173652
+Node: Top\7f1118
+Node: Overview\7f1642
+Node: About Zebra\7f3059
+Node: System Architecture\7f5328
+Node: Supported Platforms\7f8326
+Node: Supported RFC\7f9313
+Node: How to get Zebra\7f11115
+Node: Mailing List\7f11959
+Node: Bug Reports\7f13170
+Node: Installation\7f14015
+Node: Configure the Software\7f14446
+Ref: Configure the Software-Footnote-1\7f19218
+Node: Build the Software\7f20860
+Node: Install the Software\7f21402
+Node: Basic commands\7f22773
+Node: Config Commands\7f23486
+Node: Basic Config Commands\7f24368
+Node: Sample Config File\7f26766
+Node: Common Invocation Options\7f27526
+Node: Virtual Terminal Interfaces\7f28924
+Node: VTY Overview\7f29429
+Node: VTY Modes\7f30712
+Node: VTY View Mode\7f31152
+Node: VTY Enable Mode\7f31406
+Node: VTY Other Modes\7f31670
+Node: VTY CLI Commands\7f31832
+Node: CLI Movement Commands\7f32282
+Node: CLI Editing Commands\7f32815
+Node: CLI Advanced Commands\7f33388
+Node: Zebra\7f34139
+Node: Invoking zebra\7f34646
+Node: Interface Commands\7f35232
+Node: Static Route Commands\7f36739
+Node: zebra Terminal Mode Commands\7f40004
+Node: RIP\7f40965
+Node: Starting and Stopping ripd\7f41900
+Node: RIP netmask\7f43321
+Node: RIP Configuration\7f44443
+Node: How to Announce RIP route\7f48684
+Node: Filtering RIP Routes\7f51213
+Node: RIP Metric Manipulation\7f52672
+Node: RIP distance\7f53575
+Node: RIP route-map\7f54378
+Node: RIP Authentication\7f56880
+Node: RIP Timers\7f57970
+Node: Show RIP Information\7f59245
+Node: RIP Debug Commands\7f60608
+Node: RIPng\7f61592
+Node: Invoking ripngd\7f61910
+Node: ripngd Configuration\7f62167
+Node: ripngd Terminal Mode Commands\7f62906
+Node: ripngd Filtering Commands\7f63256
+Node: OSPFv2\7f63755
+Node: Configuring ospfd\7f64312
+Node: OSPF router\7f64789
+Node: OSPF area\7f67629
+Node: OSPF interface\7f69843
+Node: Redistribute routes to OSPF\7f72625
+Node: Showing OSPF information\7f74741
+Node: Debugging OSPF\7f75961
+Node: OSPFv3\7f76972
+Node: OSPF6 router\7f77290
+Node: OSPF6 area\7f77647
+Node: OSPF6 interface\7f77819
+Node: Redistribute routes to OSPF6\7f78671
+Node: Showing OSPF6 information\7f78975
+Node: BGP\7f79780
+Node: Starting BGP\7f80641
+Node: BGP router\7f81226
+Node: BGP distance\7f82462
+Node: BGP decision process\7f82903
+Node: BGP network\7f83159
+Node: BGP route\7f83340
+Node: Route Aggregation\7f83901
+Node: Redistribute to BGP\7f84453
+Node: BGP Peer\7f84962
+Node: Defining Peer\7f85140
+Node: BGP Peer commands\7f85756
+Node: Peer filtering\7f88127
+Node: BGP Peer Group\7f88618
+Node: BGP Address Family\7f88920
+Node: Autonomous System\7f89065
+Node: AS Path Regular Expression\7f89896
+Node: Display BGP Routes by AS Path\7f91159
+Node: AS Path Access List\7f91588
+Node: Using AS Path in Route Map\7f92042
+Node: Private AS Numbers\7f92308
+Node: BGP Communities Attribute\7f92453
+Node: BGP Community Lists\7f94914
+Node: Numbered BGP Community Lists\7f97595
+Node: BGP Community in Route Map\7f99169
+Node: Display BGP Routes by Community\7f101096
+Node: Using BGP Communities Attribute\7f102250
+Node: BGP Extended Communities Attribute\7f105808
+Node: BGP Extended Community Lists\7f107574
+Node: BGP Extended Communities in Route Map\7f109475
+Node: Displaying BGP routes\7f109918
+Node: Show IP BGP\7f110144
+Node: More Show IP BGP\7f110866
+Node: Capability Negotiation\7f111986
+Node: Route Reflector\7f115274
+Node: Route Server\7f115539
+Node: Multiple instance\7f116597
+Node: BGP instance and view\7f118410
+Node: Routing policy\7f119776
+Node: Viewing the view\7f120532
+Node: How to set up a 6-Bone connection\7f120804
+Node: Dump BGP packets and table\7f122176
+Node: VTY shell\7f122706
+Node: Filtering\7f124940
+Node: IP Access List\7f125288
+Node: IP Prefix List\7f125679
+Node: ip prefix-list description\7f128848
+Node: ip prefix-list sequential number control\7f129381
+Node: Showing ip prefix-list\7f129906
+Node: Clear counter of ip prefix-list\7f130989
+Node: Route Map\7f131410
+Node: Route Map Command\7f131911
+Node: Route Map Match Command\7f132114
+Node: Route Map Set Command\7f132722
+Node: IPv6 Support\7f133580
+Node: Router Advertisement\7f134145
+Node: Kernel Interface\7f134476
+Node: SNMP Support\7f136426
+Node: How to get ucd-snmp\7f137055
+Node: SMUX configuration\7f138103
+Node: Zebra Protocol\7f138536
+Node: Packet Binary Dump Format\7f140430
+Node: Command Index\7f151997
+Node: VTY Key Index\7f182299
\1f
End Tag Table
projects / mirror / frr.git / commitdiff