# @(#)67	1.2  src/tcpip/usr/samples/tcpip/gated.conf, tcprouting, tcpip720 8/25/98 17:16:16
# IBM_PROLOG_BEGIN_TAG 
# This is an automatically generated prolog. 
#  
# tcpip720 src/tcpip/usr/samples/tcpip/gated.conf 1.2 
#  
# Licensed Materials - Property of IBM 
#  
# COPYRIGHT International Business Machines Corp. 1998 
# All Rights Reserved 
#  
# US Government Users Restricted Rights - Use, duplication or 
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
#  
# IBM_PROLOG_END_TAG 
##############################################################################
#
#  There are several configuration commands for gated. They are summarized
#  in this file by statement type. It should be noted that lines that begin 
#  with, #, are considered to be comments.
#
##############################################################################
#
#  1) Directive Statements:
#     Provide direction to the gated parser about included files and the 
#     directories in which these files reside. Other statements terminate with 
#     a semi-colon (;), but directive statements terminate with a newline. 
#  The two directive statements are:
#     %directory "directory"
#        Defines the directory where the include files are stored. When it is
#     used, gated looks in the directory identified by pathname for any
#     included files that do not have a fully qualified filename i.e. do not
#     begin with "/". This statement does not actually change the current the
#     directory, it just specifies the prefix applied to included file names.
#------------------------------------------------------------------------------
#     %include "filename"
#        Identifies an include file. The contents of the file is included in 
#     the gated.conf file at the point in the gated.conf file where the 
#     %include directive is encountered. If the filename is not fully 
#     qualified, i.e. does not begin with "/", it is considered to be relative 
#     to the directory defined in the %directory directive. The %include 
#     directive statement causes the specified file to be parsed completely 
#     before resuming with this file. Nesting up to ten levels is supported. 
#
##############################################################################
#
#  2) Trace Statements
#     Control tracing options. Gated's tracing options may be configured at
#     many levels. Tracing options include the file specifications, control
#     options, and global and protocol specific tracing options. Unless 
#     overridden, tracing options from the next higher level are inherited by
#     lower levels.
#
#     The two ways for specifying trace options are:
#    
#     1) traceoptions ["trace_file" [replace] [size size[k|m] files files]]
#          [control_options] trace_options [except trace_options] ;
#
#     2) traceoptions none ;
#
#     trace_file
#        Specifies the file to receive tracing information. If this file name
#
#     does not begin with a slash (/) the directory where gated was started
#     in prepended to the name.
#
#     replace
#        Tracing should start by replacing an existing file. The default is to
#     append to an existing file.
#
#     size size[k|m] files files
#        Limit the maximum size of the trace file to the specified size
#        (mimimum 10k). When the trace file reaches the specified size, it is
#        renamed to file.0, then file.1, file.2 up to the maximum
#        number of files (minimum specification is 2).
#
#     control_options
#     Specifies options that control the appearance of tracing. Valid values
#     are:
#        nostamp
#          Specifies that a timestamp should not be prepended to all
#          trace lines.
#
#     except trace_options
#        Used to enable a broad class of tracing and then disable more
#     specific options.
#
#     none
#        Specifies that all tracing should be turned off for this protocol or
#     peer.
#
#     trace_options
#        global options, which affect global operations, are:
#            parse - trace the parser.
#            adv - trace the allocation of and freeing of policy blocks
#            symbols - trace symbols read from the kernel at startup. Must be
#                      be used via the -t command line option.
#            iflist - trace the reading of the kernel interface list. Useful
#                     if specified with the -t command line option.
#        protocol options, which have potential significance to protocols, are:
#            all - Turn on all of the following.
#            general -  shorthand notation for specifying both normal and route.
#            state - Trace state machine transitions in the protocols.
#            normal - Trace normal protocol occurrences. Abnormal protocol
#                     occurrences are always traced.
#            policy - Trace application of protocol and user-specified policy 
#                     to routes  being imported and exported.
#            task - Trace system interface and processing associated with this 
#                   protocol or peer.
#            timer - Trace timer usage by this protocol or peer.
#            route - Trace routing table changes for routes installed by this 
#                    protocol or peer.
#
#     Not all of the above options apply to all of the protocols. 
#
#     Packet tracing
#
#        Tracing of packets is very flexible. For any given protocol there are 
#     one or more options for tracing packets. All protocols allow the use of 
#     the packets keyword, which allows for tracing all packets sent and 
#     received by the protocol. Most protocols have other options for limiting 
#     tracing to a useful subset of packet types. These tracing options can be 
#     further controlled with the following modifiers:
#        detail
#          detail must be specified before send or recv. Normally packets
#          are traced in a terse form of one or two lines. When detail is
#          specified, a more verbose format is used to provide further detail on
#          the contents of the packet.
#        send
#        recv
#          These options limit the tracing to packets sent or received. Without
#          these options both sent and received packets will be traced.
#
##############################################################################
#  3) Definition Statements
#     General configuration statements that relate to all of gated or at least 
#     to more than one protocol. 
#        The types of Definition Statement Commands are:
#        1) Options Command
#              Options statements allow specification of some global options. 
#              If used, options must appear before any other type of 
#              configuration statement in the gated.conf file.
#
#           The options statement syntax is:
#           options
#               [ nosend ]
#               [ noresolv ]
#               [ gendefault [ preference <preference> ] [ gateway <gateway>] ]
#               [ syslog [ upto ] <log_level> ]
#               [ mark <time> ]
#               ;
#
#            The options list can contain one or more of the following options:
#              gendefault [ preference <preference> ] [ gateway <gateway>]
#                 When gendefault is enabled, when a BGP or EGP neighbor is up
#                 it causes the creation of a default route with the special 
#                 protocol, default. This can be disabled per BGP/EGP group 
#                 with the nogendefault option. By default, this route has a 
#                 preference of 20. This route is normally not installed in 
#                 the kernel forwarding table, it is only present so it can be 
#                 announced to other protocols. If a gateway is specified, the 
#                 default route will be installed in the kernel forwarding 
#                 table with a next hop of the listed gateway.
#
#              nosend
#                 Do not send any packets. This option makes it possible to 
#                 run gated on a live network to test protocol interactions 
#                 without actually participating in the routing protocols. 
#                 The packet traces in the gated log can be examined to verify 
#                 that gated is functioning properly. This is most useful for 
#                 RIP and HELLO 
#
#              noresolv
#                 By default gated will try to resolve symbolic names into IP
#                 addresses; this option will prevent that.
#
#              syslog [ upto ] <log_level>
#                 Controls the amount of data gated logs via syslog
#
#              mark <time>
#                 Specifying this option causes gated to output a message to 
#                 the trace log at the specified interval. This can be used as 
#                 one method of determining if gated is still running.
#
#-----------------------------------------------------------------------------
#       2) Interface Commands
#             An interface is the connection between a router and one of its 
#        attached networks. A physical interface may be specified by interface 
#        name, by IP address, or by domain name, (unless the network is an 
#        unnumbered point-to-point network.) Multiple levels of reference in 
#        the configuration language allow identification of interfaces using 
#        wildcard, interface type name, or delete word address. The 
#        interface_list is a list of one or more interface names including 
#        wildcard names (names without a number) and names which may specify 
#        more than one interface or address, or the token all for all 
#        interfaces.
#        
#        The interface Command syntax is:
#
#        interfaces {
#           options
#           [ strictinterfaces ]
#           [ scaninterval <time> ]
#           ;
#           interface <interface_list>
#              [ preference <preference> ]
#              [ down preference <preference> ]
#              [ passive ]
#              [ simplex ]
#              [ reject ]
#              [ blackhole ]
#              ;
#           define address
#              [ broadcast <address> ] | [ pointtopoint <address> ]
#              [ netmask <mask> ]
#              [ multicast ]
#              ;
#        } ;
#
#
#       options
#          Allows configuration of some global options related to interfaces.
#          These are:
#             strictinterfaces
#                Indicates that it is a fatal error to reference an interface 
#                in the configuration file that is not present when gated is 
#                started and not listed in a define statement. Without this 
#                option a warning message will be issued but gated will 
#                continue.
#             scaninterval <time>
#                Specifies how often gated scans the kernel interface list for
#                changes. The default is every 15 seconds on most systems,
#                and 60 seconds on systems that pass interface status changes
#                through the routing socket e.g. BSD 4.4). Note that gated
#                will also scan the interface list on receipt of a SIGUSR2.
#
#      interface <interface_list>
#         Sets interface options on the specified interfaces. An interface 
#         list is all or a list of interface names, domain names, or 
#         numeric addresses. Options available on this statement are:
#
#         preference <preference>
#            Sets the preference for routes to this interface when it is up
#            and appears to be functioning properly. The default preference
#            is 0.
#         down preference <preference>
#            Sets the preference for routes to this interface when gated
#            does not believe it to be functioning properly, but the kernel
#            does not indicate it is down. The default value is 120.
#         passive
#            Prevents gated from changing the preference of the route to
#            this interface if it is not believed to be functioning properly 
#            due to lack of received routing information. gated will only
#            perform this check if the interface is actively participating in a
#            routing protocol.
#         reject
#            Specifies that the address of the interface which matches these
#            criteria will be used as the local address when installing reject
#            routes in the kernel.
#         blackhole
#            Specifies that the address of the interface which matches these
#            criteria will be used as the local address when installing reject
#            routes in the kernel. 
#      define <address>
#         Defines interfaces that might not be present when gated is started so
#         they may be referenced in the configuration file when
#         strictinterfaces is defined. Possible define keywords are:
#
#         broadcast <address>
#            Defines the interface as broadcast capable (e.g. Ethernet or
#            Token Ring) and specifies the broadcast address.
#         pointopoint <address>
#            Defines the interface as a pointopoint interface (e.g. SLIP or
#            PPP) and specifies the address on the local side. The first
#            address on the define statement references the address of
#            the host on the remote end of the interface, the address
#            specified after this pointopoint keyword defines the
#            address on the local side of the interface.
#            An interface not defined as broadcast or pointopoint is assumed to
#            be non-broadcast multiaccess (NBMA), such as an X.25 network.
#         netmask <mask>
#            Specifies the subnetmask to be used on this interface. This is
#            ignored on pointtopoint interfaces.
#         multicast
#            Specifies that the interface is multicast capable.
#
#      Interface lists
#         An interface list is a list of references to interfaces or groups of
#      interfaces. There are four methods available for refering to interfaces.
#      They are listed here from most general to most specific.
#
#         all
#            This refers to all available interfaces.
#         Interface name wildcard
#            This refers to all the interfaces of the same type. AIX interfaces
#            consist of the name of the device driver, like en, and a unit 
#            number, like 0 or 5. References to the name contain only alphabetic
#            characters and match any interfaces that have the same alphabetic
#            part.
#         Interface name
#            This refers to a specific interface, usually one physical 
#            interface. These are specified as an alphabetic part followed by 
#            a numeric part. For example, en1 will match an interface named en1,
#            but not an interface named en10.
#         Interface address
#            This matches one specific interface. The reference should be by
#            protocol address (i.e. 10.0.0.51).
#-----------------------------------------------------------------------------
#
#       3)Autonomous System Command
#         Sets the autonomous system number of this router to be autonomous
#         system. This option is required if BGP or EGP are in use. The AS 
#         number is assigned by the Network Information Center (NIC). Must be
#         specified before any other configuration statements in the gated.conf
#         file.
#
#         The syntax is:
#             autonomoussystem <autonomous_system> [ loops <number> ] ;
#
#         loops 
#            only for protocols supporting AS paths, such as BGP. It controls
#            the number of times this autonomous system may appear in an 
#            AS path and defaults to 1 (one).
#-----------------------------------------------------------------------------
#
#       4)Router ID Command
#         Sets the router identifier for use by the BGP and OSPF protocols. 
#         Must be specified before any other configuration statements in the 
#         gated.conf file.
#         The syntax is:
#             routerid <host> ;
#
#         host
#            The default is the address of the first interface encountered by 
#            gated. The address of a non-point-to-point interface is preferred 
#            over the local address of a point-to-point interface and an 
#            address on a loopback interface that is not the loopback address 
#            (127.0.0.1) is most preferred.
#-----------------------------------------------------------------------------
#
#       5)Martian configuration
#         Defines a list of martian addresses about which all routing 
#         information is ignored. Sometimes a misconfigured system sends out 
#         obviously invalid destination addresses. These invalid addresses, 
#         called martians, are rejected by the routing software. This command 
#         allows additions to the list of martian addresses. Also, the allow 
#         parameter may be specified to explicitly allow a subset of a range 
#         that was disallowed. If used, this command must be specified before
#         any other configuration statements in the gated.conf file.
#
#         The syntax is:
#              martians {
#                 host <host> [ allow ] ;
#                 <network> [ allow ] ;
#                 <network> mask <mask> [ allow ] ;
#                 <network> masklen <number> [ allow ] ;
#                 default [ allow ] ;
#              } ;
#
#-----------------------------------------------------------------------------
#
#    Sample Definition Statements
#
#       options gendefault ;
#       autonomoussystem 249 ;
#       interface 128.66.12.2 passive ;
#       martians {
#          0.0.0.26
#       };
#
#    The statements in the sample perform the following functions:
#
#     The options statement tells the system to generate a default route
#     when it peers with an EGP or BGP neighbor.
#     The autonomoussystem statement tells gated to use AS number 249
#     for in EGP and BGP.
#     The interface statement tells gated not to mark interface
#     128.66.12.2 as down even if it sees no traffic.
#     The martians statement prevents routes to 0.0.0.26 from ever being
#     accepted.
#
##############################################################################
#
#  4) Protocol Statements
#       Enable or disable the use of a protocol and control protocol
#       options.  These may be specified in any order.
#
#     The RIP Statement
#        Enables or disables RIP. If the rip statement is not specified the 
#     default is rip on ;. If enabled, RIP will assume nobroadcast when there 
#     is only one interface and broadcast when there is more than one.
# 
#     The syntax is:
#
#     rip yes | no | on | off [ {
#        broadcast ;
#        nobroadcast ;
#        nocheckzero ;
#        preference <preference> ;
#        defaultmetric <metric> ;
#        query authentication [none | [[simple|md5] <password>]] ;
#        interface <interface_list>
#           [noripin] | [ripin]
#           [noripout] | [ripout]
#           [metricin <metric>]
#           [metricout <metric>]
#           [version 1]|[version 2 [multicast|broadcast]]
#           [[secondary] authentication [none | [[simple|md5] <password>]] ;
#        trustedgateways <gateway_list> ;
#        sourcegateways <gateway_list> ;
#        traceoptions <trace_options> ;
#      } ] ;
#
#
#     The options are as follows:
#
#     broadcast
#        Specifies that RIP packets will be broadcast regardless of the
#        number of interfaces present. This is useful when propagating static
#        routes or routes learned from anther protocol into RIP.
#     nobroadcast
#        Specifies that RIP packets will not be broadcast on attached
#        interfaces, even if there are more than one. If a sourcegateways
#        clause is present, routes will still be unicast directly to that 
#        gateway.
#     nocheckzero
#        Specifies that RIP should not make sure that reserved fields in
#        incoming version 1 RIP packets are zero. Normally RIP will reject
#        packets where the reserved fields are zero.
#     preference <preference>
#        Sets the preference for routes learned from RIP. The default
#        preference is 100. This preference may be overridden by a
#        preference specified in import policy.
#     defaultmetric <metric>
#        Defines the metric used when advertising routes via RIP that were
#        learned from other protocols. If not specified, the default value is 16
#        (unreachable). This choice of values requires you to explicitly specify
#        a metric in order to export routes from other protocols into RIP. This
#        metric may be overridden by a metric specified in export policy.
#     query authentication [none | [[simple|md5] <password>]] ;
#        Specifies the authentication required of query packets that do not
#        originate from routers. The default is none.
#     interface <interface_list>
#        Controls various attributes of sending RIP on specific interfaces. 
#
#        The possible parameters are:
#        noripin
#           Specifies that RIP packets received via the specified interface
#           will be ignored. The default is to listen to RIP packets on all
#           non-loopback interfaces.
#        ripin
#           This is the default. This argument may be necessary when
#           noripin is used on a wildcard interface descriptor.
#        noripout
#           Specifies that no RIP packets will be sent on the specified
#           interfaces. The default is to send RIP on all broadcast and
#           non-broadcast interfaces when in broadcast mode. The
#           sending of RIP on point-to-point interfaces must be manually
#           configured.
#        ripout
#           This is the default. This argument is necessary when it is
#           desired to send RIP on point-to-point interfaces and may be
#           necessary when noripin is used on a wildcard interface
#           descriptor.
#        metricin <metric>
#           Specifies the RIP metric to add to incoming routes before they
#           are installed in the routing table. The default is the kernel
#           interface metric plus 1 (which is the default RIP hop count). If
#           this value is specified it will be used as the absolute value, the
#           kernel metric will not be added. This option is used to make
#           this router prefer RIP routes learned via the specified
#           interface(s) less than RIP routes from other interfaces.
#        metricout <metric>
#           Specifies the RIP metric to be added to routes that are sent
#           via the specified interface(s). The default is zero. This option is
#           used to make other routers prefer other sources of RIP routes
#           over this router.
#        version 1
#           Specifies that RIP packets send via the specified interface(s)
#           will be version 1 packets. This is the default.
#        version 2
#           Specifies that RIP version 2 packets will be sent on the
#           specified interfaces(s). If IP multicast support is available on
#           this interface the default is to send full version 2 packets. If it
#           is not available, version 1 compatible version 2 packets will be
#           sent.
#        multicast
#           Specifies that RIP version 2 packets should be multicast on
#           this interface. This is the default.
#        broadcast
#           Specifies that RIP version 1 compatible version 2 packets
#           should be broadcast on this interface, even if IP multicast is
#           available.
#        [secondary] authentication [none | [simple|md5] <password>]
#           This defines the authentication type to use. It applies only to
#           RIP version 2 and is ignored for RIP-1 packets. The default
#           authentication type is none. If a password is specified, the
#           authentication type defaults to simple. The password should
#           be a quoted string with between 0 and 16 characters.
#
#           If secondary is specified, this defines the secondary
#           authentication. If omitted, the primary authentication is
#           specified. The default is primary authentication of none and no
#           secondary authentication.
#     trustedgateways <gateway_list>
#        Defines the list of gateways from which RIP will accept updates. The
#        gateway_list is simply a list of host names or IP addresses. By
#        default, all routers on the shared network are trusted to supply
#        routing information. But if the trustedgateways clause is specified
#        only updates from the gateways in the list are accepted.
#     sourcegateways <gateway_list>
#        Defines a list of routers to which RIP sends packets directly, not
#        through multicast or broadcast. This can be used to send different
#        routing information to specific gateways. Updates to gateways in this
#        list are not affected by noripout on the interface.
#     traceoptions <trace_options>
#       Specifies the tracing options for RIP.
#
#          The policy option logs info whenever a new route is announced, the 
#          metric being announced changes or a route goes or leaves holddown.
#
#          Packet tracing options (which may be modified with detail, send or
#          recv):
#
#               packets -   All RIP packets.
#               request -  RIP information request packets, such as REQUEST, 
#                          POLL and POLLENTRY
#               response - RIP RESPONSE packets, which is the type of packet 
#                          that actually contains routing information.
#
#------------------------------------------------------------------------------
#
#     The RIPNG Statement
#        Enables or disables RIPNG. If the RIPNG statement is not specified, 
#        the default is ripng on ;. The options are the same for RIPNG as they 
#        are for RIP, but all the addresses will be IPv6 addresses.
#
#     The syntax is:
#     ripng yes | no | on | off [ {
#        broadcast ;
#        nobroadcast ;
#        nocheckzero ;
#        preference <preference> ;
#        defaultmetric <metric> ;
#        query authentication [none | [[simple|md5] <password>]] ;
#        interface <interface_list>
#            [noripin] | [ripin]
#            [noripout] | [ripout]
#            [metricin <metric>]
#            [metricout <metric>]
#            [version 1]|[version 2 [multicast|broadcast]]
#            [[secondary] authentication [none | [[simple|md5] <password>]] ;
#        trustedgateways <gateway_list> ;
#        sourcegateways <gateway_list> ;
#        traceoptions <trace_options> ;
#     } ] ;
#
#------------------------------------------------------------------------------
#
#     The Hello Statement
#        Enables or disables HELLO. If the hello statement is not specified 
#     the default is hello off. If enabled, HELLO will assume nobroadcast when 
#     there is only one interface and broadcast when there is more than one 
#     interface.
#
#     The syntax is:
#     hello yes | no | on | off [ {
#       broadcast ;
#       nobroadcast ;
#       preference <preference> ;
#       defaultmetric <metric> ;
#       interface <interface_list>
#            [nohelloin] | [helloin]
#            [nohelloout] | [helloout]
#            [metricin <metric>]
#            [metricout <metric>] ;
#       trustedgateways <gateway_list> ;
#       sourcegateways <gateway_list> ;
#       traceoptions <trace_options> ;
#     } ] ;
#
#     The options are as follows:
#     broadcast
#        Specifies that HELLO packets will be broadcast regardless of the
#        number of interfaces present. This is useful when propagating static
#        routes or routes learned from anther protocol into HELLO. 
#     nobroadcast
#        Specifies that HELLO packets will not be broadcast on attached
#        interfaces, even if there are more than one. If a sourcegateways
#        clause is present, routes will still be unicast directly to that 
#        gateway.
#     preference <preference>
#        Sets the preference for routes learned from HELLO. The default
#        preference is 90. This preference may be overridden by a preference
#        specified in import policy.
#     defaultmetric <metric>
#        Defines the metric used when advertising routes via HELLO that
#        were learned from other protocols. If not specified, the default value
#        is 30000 (unreachable). This choice of values requires you to
#        explicitly specify a metric in order to export routes from other
#        protocols into HELLO. This metric may be overridden by a metric
#        specified in export policy.
#     interface <interface_list>
#        Controls various attributes of sending HELLO on specific interfaces.
#
#        Note that if there are multiple interfaces configured on the same
#        subnet, HELLO updates will only be sent from first one one which
#        HELLO output is configured.
#
#        The possible parameters are:
#          nohelloin
#             Specifies that HELLO packets received via the specified
#             interface will be ignored. The default is to listen to HELLO on
#             all non-loopback interfaces.
#          helloin
#             This is the default. This argument may be necessary when
#             nohelloin is used on a wildcard interface descriptor.
#          nohelloout
#             Specifies that no HELLO packets will be sent on the specified
#             non-broadcast interfaces when in broadcast mode. The
#             sending of HELLO on point-to-point interfaces must be
#             manually configured.
#          helloout
#             This is the default. This argument is necessary when it is
#             desired to send HELLO on point-to-point interfaces and may
#             be necessary when nohelloin is used on a wildcard interface
#             descriptor.
#          metricin <metric>
#             Specifies the HELLO metric to add to incoming routes before
#             they are installed in the routing table. The default is the kernel
#             interface metric plus 1 (which is the default HELLO hop
#             count). If this value is specified it will be used as the absolute
#             value, the kernel metric will not be added. This option is used
#             to make this router prefer HELLO routes learned via the
#             specified interface(s) less than HELLO routes from other
#             interfaces.
#          metricout <metric>
#             Specifies the HELLO metric to be added to routes that are
#             send via the specified interface(s). The default is zero. This
#             option is used to make other routers prefer other sources of
#             HELLO routes over this router.
#
#     trustedgateways <gateway_list>
#        Defines the list of gateways from which HELLO will accept updates.
#        The gateway_list is simply a list of host names or IP addresses. By
#        default, all routers on the shared network are trusted to supply
#        routing information. But if the trustedgateways clause is specified
#        only updates from the gateways in the list are accepted.
#     sourcegateways <gateway_list>
#        Defines a list of routers to which HELLO sends packets directly, not
#        through multicast or broadcast. This can be used to send different
#        routing information to specific gateways. Updates to gateways in this
#        list are not affected by noripout on the interface.
#     traceoptions <trace_options>
#        Specifies the tracing options for HELLO.
#
#        The policy option logs info whenever a new route is announced, the 
#        metric being announced changes or a route goes or leaves holddown.
#
#        Packet tracing options (which may be modified with detail, send and/or
#        recv):
#
#           packets - All HELLO packets
#
#------------------------------------------------------------------------------
#
#     The OSPF Statement
#        Enables or disables the OSPF protocol. The default is ospf off ;
#     
#     The syntax is:
#
#     ospf yes | no | on | off [ {
#       defaults {
#           preference <preference> ;
#           cost <cost> ;
#           tag [ as ] <tag> ;
#           type 1 | 2 ;
#       } ;
#       exportlimit <routes> ;
#       exportinterval <time> ;
#       traceoptions <trace_options> ;
#       monitorauthkey <authkey> ;
#       monitorauth none | ( [ simple | md5 ] <authkey> ) ;
#       backbone | ( area <area> ) {
#           authtype 0 | 1 | none | simple ;
#           stub [ cost <cost>] ;
#           networks {
#               <network> [ restrict ] ;
#               <network> mask <mask> [ restrict ] ;
#               <network> masklen <number> [ restrict ] ;
#               host <host> [ restrict ] ;
#           } ;
#           stubhosts {
#              <host> cost <cost> ;
#           } ;
#           interface <interface_list>; [cost <cost> ] {
#              <interface_parameters>
#           } ;
#           interface <interface_list> nonbroadcast [cost <cost> ] {
#              pollinterval <time> ;
#              routers {
#                 <gateway> [ eligible ] ;
#              } ;
#              <interface_parameters>
#           } ;
#           (Backbone only:)
#           virtuallink neighborid <router_id> transitarea <area> {
#              <interface_parameters>
#           } ;
#       } ;
#     } ] ;
#
#     The following are the interface_parameters refered to above. The may be
#     specified on any class of interface and are described under the interface
#     clause.
#
#       enable | disable ;
#       retransmitinterval <time> ;
#       transitdelay <time> ;
#       priority <priority> ;
#       hellointerval <time> ;
#       routerdeadinterval <time> ;
#       authkey <auth_key> ;
#
#     defaults
#        These parameters specify the defaults used when importing OSPF
#        ASE routes into the gated routing table and exporting routes from the
#        gated routing table into OSPF ASEs.
#
#          preference <preference>
#             The preference is used to determine how OSPF routes compete with
#             routes from other protocols in the gated routing table. The 
#             default value is 150.
#          cost <cost>
#             The cost is used when exporting a non-OSPF route from the gated
#             routing table into OSPF as an ASE. The default value is 1. This 
#             may be explicitly overridden in export policy.
#          tag [ as ] <tag>
#             OSPF ASE routes have a 32 bit tag field that is not used by the
#             OSPF protocol, but may be used by export policy to filter routes.
#             When OSPF is interacting with an egp, the tag field may be used to
#             propagate AS path information, in which case the as keyword is
#             specified and the tag is limited to 12 bits of information. If not
#             specified, the tag is set to zero.
#          type 1 | 2
#             Routes exported from the gated routing table into OSPF default to
#             becoming type 1 ASEs. This default may be explicitly changed here
#             and overridden in export policy.
#
#      ASE export rate
#         Because of the nature of OSPF, the rate at which ASEs are flooded
#         must be limited. These two parameters can be used to adjust those
#         rate limits.
#
#           exportinterval <time>
#              This specifies how often a batch of ASE link state
#              advertisements will be generated and flooded into OSPF. The
#              default is once per second.
#           exportlimit <routes>
#              This parameter specifies how many ASEs will be generated
#              and flooded in each batch. The default is 100.
#
#      traceoptions <trace_options>
#         Specifies the tracing options for OSPF.
#            lsabuild - Link State Advertisement creation
#            spf - Shortest Path First (SPF) calculations
#
#         Packet tracing options (which may be modified with detail, send and
#         recv):
#            hello - OSPF HELLO packets which are used to determine neighbor
#                    reachability.
#            dd -  OSPF Database Description packets which are used in 
#                  synchronizing OSPF databases.
#            request - OSPF Link State Request packets which are used in 
#                      synchronizing OSPF databases.
#            lsu - OSPF Link State Update packets which are used in 
#                  synchronizing OSPF databases.
#            ack - OSPF Link State Ack packets which are used in synchronizing
#                  OSPF databases.
#
#      monitorauthkey <authkey>
#         OSPF state may be queried using the ospf_monitor utility. By default 
#         the ospf-monitor requests are not authenticated, if an authentication
#         key is configured, the incoming requests must match the specified 
#         authentication key.
# 
#     backbone
#        area <area>
#           Each OSPF router must be configured into at least one OSPF area.
#           If more than one area is configured, at least one must the be
#           backbone. The backbone may only be configured using the
#           backbone keyword, it may not be specified as area 0. The
#           backbone interface may be a virtuallink.
#        authtype 0 | 1 | none | simple
#           OSPF specifies an authentication scheme per area. Each
#           interface in the area must use this same authentication scheme
#           although it may use a different authenticationkey. The
#           currently valid values are none (0) for no authentication, or
#           simple (1) for simple password authentication.
#        stub [ cost <cost>]
#           A stub area is one in which there are no ASE routes. If a
#           cost is specified, this is used to inject a default route into the
#           area with the specified cost.
#        networks
#           The networks list describes the scope of an area. Intra-area
#           LSAs that fall within the specified ranges are not advertised
#           into other areas as inter-area routes. Instead, the specified
#           ranges are advertised as summary network LSAs. If restrict
#           is specified, the summary network LSAs are not advertised.
#           Intra-area LSAs that do not fall into any range are also
#           advertised as summary network LSAs. The entries in
#           this list are either networks, or a subnetwork/mask pair. 
#        stubhosts
#           This lists specifies directly attached hosts that should be
#           advertised as reachable from this router and the costs they
#           should be advertised with. Point-to-point interfaces should be 
#           specified here.
#
#     interface <interface_list> [cost <cost> ]
#        This form of the interface clause is used to configure a broadcast
#        (which requires IP multicast support) or a point-to-point
#        interface.
#
#        Each interface has a cost. The costs of all interfaces a packet must
#        cross to reach a destination are summed to get the cost to that
#        destination. The default cost is one, but another non-zero value may
#        be specified.
#
#        Interface parameters common to all types of interfaces are:
#          retransmitinterval <time>
#             The number of seconds between link state advertisement
#             retransmissions for adjacencies belonging to this interface.
#          transitdelay <time>
#             The estimated number of seconds required to transmit a link
#             state update over this interface. Transitdelay takes into
#             acccount transmission and propagation delays and must be
#             greater than 0.
#          priority <priority>
#             A number between 0 and 255 specifying the priority for
#             becoming the designated router on this interface. When two
#             routers attached to a network both attempt to become
#             designated router, the one with the highest priority wins. A
#             router whose router priority is set to 0 is ineligible to become
#             designated router.
#          hellointerval <time>
#             The length of time, in seconds, between Hello packets that the
#             router sends on the interface.
#          routerdeadinterval <time>
#             The number of seconds not hearing a router's Hello packets
#             before the router's neighbors will declare it dovn.
#          authkey <auth_key>
#             Used by OSPF authentication to generate and verify the
#             authentication field in the OSPF header. The authentication
#             key can be configured on a per interface basis. It is specified
#             by one to eight decimal digits separated by periods, a one to
#             eight byte hexadecimal string preceded by 0x, or a one to
#             eight character string in double quotes.
#          nomulticast
#             By default, OSPF packets to neighbors on point-to-point
#             interfaces are sent via the IP multicast mechanism.
#             If the use of IP multicasting is not desired because the remote
#             neighbor does not support it, the nomulticast parameter may
#             be specified to force the use of unicast OSPF packets. 
#     interface <interface_list> nonbroadcast [cost <cost> ]
#        This form of the interface clause is used to specify a nonbroadcast
#        interface on a non-broadcast multi-access (NBMA) media.
#        Since an OSPF broadcast media must support IP multicasting, a
#        broadcast capable media, such as Ethernet, that does not support IP
#        multicasting must be configured as a non-broadcast interface.
#
#        A non-broadcast interface supports any of the standard interface
#        clauses listed above, plus the following two that are specific to
#        non-broadcast interfaces:
#            pollinterval <time>
#               Before adjacency is established with a neighbor, OSPF
#               packets are sent periodically at the specified pollinterval.
#            routers
#               By definition it is not possible to send broadcast packets to
#               discover OSPF neighbors on a non-broadcast, so all
#               neighbors must be configured. The list includes one or more
#               neighbors and an indication of their elligibility to become a
#               designated router.
#     virtuallink neighborid <router_id> transitarea <area>
#        Virtual links are used to establish or increase connectivity of the
#        backbone area. The neighborid is the router_id of the other end
#        of the virtual link. The transit area specified must also be 
#        configured on this system. All standard interface parameters defined 
#        by the interface clause above may be specified on a virtual link.
#
#------------------------------------------------------------------------------
#
#     The IS-IS Statement
#        Enables the IS-IS protocol in gated. By default IS-IS is
#     disabled. The isis statement consists of an initial description of the 
#     IS and a list of statements that determine the configuration of the 
#     specific circuits and networks to be managed. Statements may appear in 
#     any order.
#
#     The syntax is:
#     isis no | dual | ip | iso {
#        level 1|2 ;
#        [traceoptions <isis_traceoptions> ;]
#        [systemid <6_digit_hexstring> ;]
#        [area <hexstring> ;]
#        [set <isis_parm> <value> ; ... ]
#        circuit <string>
#            metric [level 1|2] <1..63>
#            ...
#            priority [level 1|2] <0..127>
#            ...
#            ;
#        ...
#     } ;
#
#     Statements include:
#
#       level
#         Indicates whether gated is running on a Level 1 (intra-area) or Level
#         2 (inter-area) IS. The default is Level 1.
#       traceoptions
#          all
#          iih
#          lanadj
#          p2padj
#          lspdb
#          lspcontent
#          lspinput
#          flooding
#          buildlsp
#          csnp
#          psnp
#          route
#          update
#          paths
#          spf
#          events
#       systemid
#          Overrides the autoconfigured system ID (determined from interface
#          addresses and corresponding netmasks.) If no system identifier is
#          specified, the system ID portion of the first real circuit's NSAP is
#          used. Once a system ID is set, it cannot be changed without disabling
#          and reenabling all of IS-IS.
#       area
#          IS-IS area addresses are automatically configured based on the real
#          circuits over which IS-IS runs. Addresses specified in this statement
#          are maintained in addition to those configured automatically from the
#          circuits. This command is used primarily for simulation.
#       circuit
#          Each circuit statement specifies one of the circuits the system will
#          manage. Circuits normally correspond to AIX interfaces, with
#          string being the interface name, but simulated device names may
#          also be specified. If the string is in the form of "simN", where N 
#          is an integer, the circuit is assumed to be a simulated circuit 
#          managed by the network simulator troll. The circuit attributes are a 
#          list of options that may appear in any order in the circuit 
#          statement.
#       metric
#          Allows specifications of Level 1 and Level 2 metrics for each 
#          circuit. Only the default metric type is supported. IS-IS metrics 
#          must be in the range 1 to 63. If no metric is set for the circuit, 
#          the default value is 63.
#       priority
#          Determines designated router election results; higher values give a
#          higher likelihood of becoming the designated router. The level
#          defaults to Level 1. If no priority is specified, priority is set 
#          to a random value between 0 and 127.
#
#          On a level 2 IS, to configure a circuit with a Level 1 metric of 10 
#          and a Level 2 metric of 20, add two metric options to the circuit
#          statement.
#
#     The default Level is 1 : the default metric is 63. The default 
#     preference for IS-IS Level 1 is 15 for IS-IS Level 2 is 18.
#
#------------------------------------------------------------------------------
#
#     The EGP Statement
#        Enables or disables the EGP protocol. the default is disable.
#     The syntax is:
#     egp yes | no | on | off
#     [ {
#         preference <preference> ;
#         defaultmetric <metric> ;
#         packetsize <number> ;
#         traceoptions <trace_options> ;
#         group
#            [ peeras <autonomous_system> ]
#            [ localas <autonomous_system> ]
#            [ maxup <number> ]
#         {
#            neighbor <host>
#                [ metricout <metric> ]
#                [ preference <preference> ]
#                [ preference2 <preference> ]
#                [ ttl <ttl> ]
#                [ nogendefault ]
#                [ importdefault ]
#                [ exportdefault ]
#                [ gateway <gateway> ]
#                [ lcladdr <local_address> ]
#                [ sourcenet <network> ]
#                [ minhello | p1 <time> ]
#                [ minpoll | p2 <time> ]
#                [ traceoptions <trace_options> ]
#                ;
#        } ;
#     } ] ;
#
#     The options are as follows:
#        preference <preference>
#           Sets the preference for routes learned from RIP. The default
#           preference is 200. This preference may be overridden by a
#           preference specified on the group or neighbor statements or by
#           import policy.
#        defaultmetric <metric> ;
#           Defines the metric used when advertising routes via EGP. If not
#           specified, the default value is 255 which some systems may consider
#           unreachable. This choice of values requires you to explicitly 
#           specify a metric when exporting routes to EGP neighbors. This 
#           metric may be overridden by a metric specified on the neighbor or 
#           group statements or in export policy.
#        packetsize <maxpacketsize>
#           This defines the expected maximum size of a packet that EGP
#           expects to receive from this neighbor. If a packet larger than this
#           value is received, it will be incomplete and have to be discarded. 
#           The length of this packet will be noted and the expected size will 
#           be increased to be able to receive a packet of this size. 
#           Specifying the parameter here will prevent the first packet from 
#           being dropped. If not specified, the default size is 8192 bytes. 
#        traceoptions <trace_options>
#           Specifies the tracing options for EGP. By default these are 
#           inherited from the global trace options. These values may be 
#           overridden on a group or neighbor basis. 
#           The state and policy options work with EGP.
#           Packet tracing options (which may be modified with detail, send and
#           recv):
#
#               packets - All EGP packets
#               hello - EGP HELLO/I-HEARD-U packets which are used to determine
#                       neighbor reachability.
#               acquire - EGP ACQUIRE/CEASE packets which are used to 
#                         initiate and terminate EGP sessions.
#               update - EGP POLL/UPDATE packets which are used to request and 
#                        receive reachability updates.
#        group
#           EGP neighbors must be specified as members of a group. A group
#           is usually used to group all neighbors in one autonomous system.
#           Parameters specified on the group clause apply to all of the
#           subsidiary neighbors unless explicitly overridden on a neighbor
#           clause. Any number of group clauses may specify any number of
#           neighbor clauses.
#
#           Any parameters from the neighbor subclause may be specified on
#           the group clause to provide defaults for the whole group (which may
#           be overridden for individual neighbors). In addition, the group 
#           clause is the only place to set the following attributes:
#               peeras
#                 Identifies the autonomous system number expected from peers
#                 in the group. If not specified it will be learned dynamically.
#               localas
#                 Identifies the autonomous system which gated is representing
#                 to the group. The default is that which has been set 
#                 globally in the autonomoussystem statement. This option's use
#                 is discouraged.
#               maxup
#                 Specifies the number of neighbors gated should acquire from
#                 this group. The default is to acquire all of the neighbors 
#                 in the group. Gated will attempt to acquire the first maxup 
#                 neighbors in the order listed. If one of the first neighbors 
#                 is not available, it will acquire one further down the list. 
#                 If after start-up gated does manage to acquire the more 
#                 desirable neighbor, it will drop the less desirable one.
#        neighbor <neighbor_address>
#           Each neighbor subclause defines one EGP neighbor within a group.
#           The only part of the subclause that is required is the
#           neighbor_address argument which is the symbolic host name or
#           IP address of the neighbor. All other parameters are optional.
#        preference <preference>
#           Specifies the preference used for routes learned from these
#           neighbors. This can differ from the default EGP preference set
#           in the egp statement, so that gated can prefer routes from
#           one neighbor, or group of neighbors, over another. This
#           preference may be explicitly overriden by import policy.
#        preference2 <preference>
#           In the case of a preference tie, the second preference,
#           preference2 may be used to break the tie. The default value
#           is 0.
#        metricout <metric>
#           This defines a metric to be used for all routes sent to this
#           neighbor. The value overrides the default metric set in the egp
#           statement and any metrics specified by export policy, but only
#           for this specific neighbor or group of neighbors.
#        nogendefault
#           Prevents gated from generating a default route when EGP
#           receives a valid update from its neighbor. The default route is
#           only generated when the gendefault option is enabled.
#        importdefault
#           included in a received EGP update. If not specified, the default
#           route contained in an EGP update is ignored. For efficiency,
#           some networks have external routers announce a default route
#           to avoid sending large EGP update packets.
#        exportdefault
#           Enables gated to include the default route (0.0.0.0) in EGP
#           updates sent to this EGP neighbor. This allows the system to
#           advertise the default route via EGP. Normally a default route is
#           not included in EGP updates.
#        gateway <gateway>
#           If a network is not shared with a neighbor, gateway specifies
#           a router on an attached network to be used as the next hop
#           router for routes received from this neighbor. This option is
#           only rarely used.
#        lcladdr <local_address>
#           Specifies the address to be used on the local end of the
#           connection with the neighbor. The local address must be on an
#           interface which is shared with the neighbor or with the
#           neighbor's gateway when the gateway parameter is used. A
#           sessionwill only be opened when an interface with the
#           appropriate local address (through which the neighbor or
#           gateway address is directly reachable) is operating.
#        sourcenet <network>
#           Specifies the network queried in the EGP Poll packets. By
#           default this is the network shared with neighbors address
#           specified. If there is no network shared with the neighbor, one
#           of the network the neighbor is attached to should be specified.
#           This parameter can also be used to specify a network shared
#           with the neighbor other than the one on which the EGP
#        p1 <time>
#        minhello <time>
#           Sets the minimum acceptable interval between the transmission
#           of EGP HELLO packets. The default hello interval is 30
#           seconds. If the neighbor fails to respond to three hello
#           packets, gated stops trying to acquire the neighbor. Setting a
#           larger interval gives the neighbor a better chance to respond.
#           Minhello is an alias for the P1 value defined in the EGP
#           specification.
#        p2 <time>
#        minpoll <time>
#           Sets the time interval between polls to the neighbor. The
#           default is 120 seconds. If three polls are sent without a
#           response, the neighbor is declared "down" and all routes
#           learned from that neighbor are removed from the routing
#           database. A longer polling interval supports a more stable
#           routing database but is not as responsive to routing changes.
#           Minpoll is an alias for the P2 value defined in the EGP
#           specification.
#        ttl <ttl>
#          By default, gated sets the IP TTL for local neighbors to one
#          and the TTL for non-local neighbors to 255. This option is
#          provided when attempting to communicate with improperly
#          functioning routers that ignore packets sent with a TTL of one.
#          Specifies the tracing options for this EGP neighbor. By default
#          these are inherited from group or EGP global trace options.
#
#------------------------------------------------------------------------------
#
#     The BGP Statement
#       Enables or disables BGP. By default BGP is disabled.
#     The default metric for announcing routes via BGP is not to send a metric.
#
#     The syntax is:
#     bgp yes | no | on | off
#     [ {
#          preference <preference> ;
#          defaultmetric <metric> ;
#          traceoptions <trace_options> ;
#          group type ( external peeras <autonomous_system> )
#            | ( internal peeras <autonomous_system> )
#            | ( igp peeras <autonomous_system> proto <proto> )
#            | ( routing peeras <autonomous_system> proto <proto>
#                    interface <interface_list> )
#            | ( test peeras <autonomous_system> )
#          {
#            allow {
#                <network>
#                <network> mask <mask>
#                <network> masklen <number>
#                all
#                host <host>
#            } ;
#            peer <host>
#                [ metricout <metric> ]
#                [ localas <autonomous_system> ]
#                [ nogendefault ]
#                [ gateway <gateway> ]
#                [ preference <preference> ]
#                [ preference2 <preference> ]
#                [ lcladdr <local_address> ]
#                [ holdtime <time> ]
#                [ version <number> ]
#                [ passive ]
#                [ sendbuffer <number> ]
#                [ recvbuffer <number> ]
#                [ indelay <time> ]
#                [ outdelay <time> ]
#                [ keep [ all | none ] ]
#                [ analretentive ]
#                [ noauthcheck ]
#                [ noaggregatorid ]
#                [ keepalivesalways ]
#                [ v3asloopokay ]
#                [ nov4asloop ]
#                [ logupdown ]
#                [ traceoptions <trace_options> ]
#                ;
#          } ;
#     } ] ;
#     external | internal | igp | test
#
#     The clause options are as follows:
#     preference <preference>
#        Sets the preference for routes learned from RIP. The default
#        preference is 170. This preference may be overridden by a
#        preference specified on the group or peer statments or by import
#        policy.
#     defaultmetric <metric>
#        Defines the metric used when advertising routes via BGP. If not
#        specified, no metric is propagated. This metric may be overridden by
#        a metric specified on the neighbor or group statements or in export
#        policy.
#     traceoptions <trace_options>
#        Specifies the tracing options for BGP. By default these are inherited
#        from the global trace options. These values may be overridden on a
#        group or neighbor basis.
#        Packet tracing options (which may be modified with detail, send and
#        recv):
#
#          packets - All BGP packets
#          open - BGP OPEN packets which are used to establish a peer 
#                 relationship.
#          update - BGP UPDATE packets which are used to pass network 
#                   reachability information.
#          keepalive - BGP KEEPALIVE packets which are used to verify peer 
#                      reachability.
#
#     Groups
#
#     BGP peers are grouped by type and the autonomous system of the peers.
#     Any number of groups may be specified, but each must have a unique
#     combination of type and peer autonomous system. There are four possible
#     group types:
#
#        group type external peeras <autonomous_system>
#           In the classic external BGP group, full policy checking is applied 
#           to all incoming and outgoing advertisements. The external neighbors
#           must be directly reachable through one of the machine's local
#           interfaces. By default no metric is included in external 
#           advertisements, and the next hop is computed with respect to the 
#           shared interface.
#
#        group type internal peeras <autonomous_system>
#           An internal group operating where there is no IP-level IGP.
#           All neighbors in this group are required to be directly reachable 
#           via a single interface. All next hop information is computed with 
#           respect to this interface. Import and export policy may be applied 
#           to group advertisements. Routes received from external BGP or EGP 
#           neighbors are by default readvertised with the received metric.
#
#        group type igp peeras <autonomous_system> proto <proto>
#           An internal group that runs in association with an interior 
#           protocol. The IGP group examines routes which the IGP is exporting 
#           and sends an advertisement only if the path attributes could not be 
#           entirely represented in the IGP tag mechanism. Only the AS path, 
#           path origin, and transitive optional attributes are sent with 
#           routes. No metric is sent, and the next hop is set to the local 
#           address used by the connection. Received internal BGP routes are 
#           not used or readvertised. Instead, the AS path information is 
#           attached to the corresponding IGP route and the latter is used for 
#           readvertisement. Since internal IGP peers are sent only a subset of 
#           the routes which the IGP is exporting, the export policy used is 
#           the IGP's. There is no need to implement the "don't routes from 
#           peers in the same group" constraint since the advertised routes are 
#           routes that IGP already exports.
#
#        group type routing peeras <autonomous_system> proto <proto> interface
#        <interface_list>
#           An internal group which uses the routes of an interior protocol to
#           resolve forwarding addresses. A type routing group propagates
#           external routes between routers which are not directly connected,
#           and computes immediate next hops for these routes by using the
#           BGP next hop which arrived with the route as a forwarding address
#           to be resolved via an internal protocol's routing information. In
#           essence, internal BGP is used to carry AS external routes, while the
#           IGP is expected to only carry AS internal routes, and the latter is
#           used to find immediate next hops for the former.
#
#           The proto names the interior protocol to be used to resolve BGP
#           route next hops, and may be the name of any IGP in the
#           configuration. By default the next hop in BGP routes advertised to
#           type routing peers will be set to the local address on the BGP
#           connection to those peers, as it is assumed a route to this address 
#           will be propagated via the IGP. The interface_list can optionally 
#           provide a list interfaces whose routes are carried via the IGP for 
#           which third party next hops may be used instead.
#
#        group type test peeras <autonomous_system>
#           An extension to external BGP which implements a fixed policy using
#           test peers. Fixed policy and special case code make test peers
#           relatively inexpensive to maintain. Test peers do not need to be on #           a directly attached network. If gated and the peer are on the same
#           (directly attached) subnet, the advertised next hop is computed with
#           respect to that network, otherwise the next hop is the local 
#           machine's current next hop. All routing information advertised by 
#           and received is sent back to the test peer. Metrics from EGP- and 
#           BGP-derived routes are forwarded in the advertisement, otherwise no #           metric is included.
#
#     Group parameters
#
#     The BGP statement has group clauses and peer subclauses. Any number
#     of peer subclauses may be specified within a group. A group clause usually
#     defines default parameters for a group of peers, these parameters apply to
#     all subsidiary peer subclauses. Any parameters from the peer subclause may
#     be specified on the group clause to provide defaults for the whole group
#     (which may be overridden for individual peers).
#
#        Specifying peers
#
#        Within a group, BGP peers may be configured in one of two ways. They
#        may be explicitly configured with a peer statement, or implicitly 
#        configured with the allow statement. Both are described here:
#
#         allow
#           allows for peer connections from any addresses in the specified 
#           range of network and mask pairs. All parameters for these peers 
#           must be configured on the group clause. 
#         peer <host>
#            configures an individual peer. Each peer inherits all
#            parameters specified on a group as defaults. Those default may be
#            overridden by parameters explicitly specified on the 
#            peer subclause.
#
#         Peer parameters (All optional)
#            metricout <metric>
#              If specified, this metric is used as the primary metric on all 
#              routes a metric specified on the group and any metric specified 
#              by export policy.
#            localas <autonomous_system>
#              Identifies the autonomous system which gated is representing to 
#              this group of peers. The default is that which has been set 
#              globally in the autonomoussystem statement.
#            nogendefault
#              Prevents gated from generating a default route when EGP 
#              receives a valid update from its neighbor. The default route is 
#              only generated when the gendefault option is enabled.
#            gateway <gateway>
#              If a network is not shared with a peer, gateway specifies a 
#              router on an attached network to be used as the next hop router 
#              for routes received from this neighbor. This parameter is not 
#              needed in most cases.
#            preference <preference>
#              Specifies the preference used for routes learned from these 
#              peers. This can differ from the default BGP preference set in 
#              the bgp statement, so that gated can prefer routes from one 
#              peer, or group of peers, over others. This preference may be 
#              explicitly overriden by import policy.
#            preference2 <preference>
#              In the case of a preference tie, the second preference,
#              preference2 may be used to break the tie. The default value is 0.
#            lcladdr <local_address>
#              Specifies the address to be used on the local end of the TCP
#              connection with the peer. For external peers the local address 
#              must be on an interface which is shared with the peer or with 
#              the peer's gateway when the gateway parameter is used. A 
#              session with an external peer will only be opened when an 
#              interface with the appropriate local address (through which 
#              the peer or gateway address is directly reachable) is operating.
#              For other types of peers, a peer session will be maintained 
#              when any interface with the specified local address is operating.#              In either case incoming connections will only be recognized as 
#              matching a configured peer if they are addressed to the 
#              configured local address.
#            holdtime <time>
#              Specifies the BGP holdtime value to use when negotiating the
#              connection with this peer, in seconds. According to BGP, if gated
#              does not receive a keepalive, update, or notification message 
#              within the period specified in the Hold Time field of the BGP 
#              Open message, then the BGP connection will be closed. 
#              The value must be either 0 (no keepalives will be sent) or at 
#              least 3.
#            version <version>
#              Specifies the version of the BGP protocol to use with this peer. 
#              If not specified, the highest supported version is used first 
#              and version negotiation is attempted. If it is specified, only 
#              the specified version will be offered during negotiation. 
#              The currently supported versions are 2, 3, and 4.
#            passive
#              Specifies that active OPENs to this peer should not be attempted.
#              gated should wait for the peer to issue an open. By default all
#              explicitly configured peers are active, they periodically send 
#              OPEN messages until the peer responds.
#            indelay <time>
#            outdelay <time>
#               Used to dampen route fluctuations. Indelay is the amount of 
#               time a route learned from a BGP peer must be stable before it 
#               is accepted into the gated routing database. Outdelay is the 
#               amount of time a route must be present in the gated routing 
#               database before it is exported to BGP. The default value for 
#               each is 0, meaning that these features are disabled.
#            keep all
#               Used to retain routes learned from a peer even if the routes' AS
#               paths contain one of our exported AS numbers.
#            noauthcheck
#               Normally gated verifies that incoming packets have an 
#               authentication field of all ones. This option may be used to 
#               allow communication with an implementation that uses some 
#               other form of authentication.
#            noaggregatorid
#               Causes gated to specify the routerid in the aggregator 
#               attribute as zero (instead of its routerid) in order to prevent 
#               different routers in an AS from creating aggregate routes with 
#               different AS paths.
#            keepalivesalways
#               Causes gated to always send keepalives, even when an update 
#               could have correctly substituted for one. This allows 
#               interoperability with routers that do not completely obey the 
#               protocol specifications on this point.
#            v3asloopokay
#               By default gated will not advertise routes whose AS path is 
#               looped (i.e. with an AS appearing more than once in the path) 
#               to version 3 external peers. Setting this flag removes this 
#               constraint. Ignored when set on internal groups or peers.
#             nov4asloop
#               Prevents routes with looped AS paths from being advertised to
#               version 4 external peers. This can be useful to avoid 
#               advertising such routes to peers which would incorrectly 
#               forward the routes on to version 3 neighbors.
#             logupdown
#               Causes a message to be logged via the syslog mechanism whenever 
#               a BGP peer enters or leaves the ESTABLISHED state.
#             traceoptions <trace_options>
#               Specifies the tracing options for this BGP neighbor. 
#               By default these are inherited from group or BGP global trace 
#               options. 
#
#------------------------------------------------------------------------------
#
#     The BGP4+ Statement
#     The options are the same for BGP4+ as they are for BGP but all the 
#     addresses will be IPv6 addresses.
#
#     The syntax is:
#     bgp4+ yes | no | on | off
#     [ {
#        preference <preference> ;
#        defaultmetric <metric> ;
#        traceoptions <trace_options> ;
#        group type ( external peeras <autonomous_system> )
#            | ( internal peeras <autonomous_system> )
#            | ( igp peeras <autonomous_system> proto <proto> )
#            | ( routing peeras <autonomous_system> proto <proto>
#                    interface <interface_list> )
#            | ( test peeras <autonomous_system> )
#        {
#            allow {
#                <network>
#                <network> masklen <number>
#                all
#                host <IPv6 host address>
#            } ;
#            peer <IPv6 host address>
#                [ metricout <metric> ]
#                [ localas <autonomous_system> ]
#                [ nogendefault ]
#                [ gateway <gateway> ]
#                [ preference <preference> ]
#                [ preference2 <preference> ]
#                [ lcladdr <local_address> ]
#                [ holdtime <time> ]
#                [ version <number> ]
#                [ passive ]
#                [ sendbuffer <number> ]
#                [ recvbuffer <number> ]
#                [ indelay <time> ]
#                [ outdelay <time> ]
#                [ keep [ all | none ] ]
#                [ analretentive ]
#                [ noauthcheck ]
#                [ noaggregatorid ]
#                [ keepalivesalways ]
#                [ v3asloopokay ]
#                [ nov4asloop ]
#                [ logupdown ]
#                [ ttl <ttl> ]
#                [ traceoptions <trace_options> ]
#                ;
#        } ;
#     } ] ;
#
#
#------------------------------------------------------------------------------
#
#      The Redirect Statement
#
#      redirect yes | no | on | off
#      [ {
#          preference <preference> ;
#          interface <interface_list>
#              [ noredirects ] | [redirects ] ;
#          trustedgateways <gateway_list> ;
#          traceoptions <trace_options> ;
#      } ] ;
#
#     preference
#        Sets the preference for a route learned from a redirect. 
#        The default is 30.
#     interface <interface_list>
#        The interface statement allows the enabling and disabling of
#        redirects on an interface-by-interface basis. 
#        The possible parameters are:
#        noredirects
#          Specifies that redirects received via the specified interface will
#          be ignored. The default is to accept redirects on all interfaces.
#        redirects
#          This is the default. This argument may be necessary when
#          noredirects is used on a wildcard interface descriptor.
#     trustedgateways <gateway_list>
#        Defines the list of gateways from which redirects will be accepted.
#        The gateway_list is simply a list of host names or addresses. By
#        default, all routers on the shared network(s) are trusted to supply
#        redirects. But if the trustedgateways clause is specified only
#        redirects from the gateways in the list are accepted.
#     traceoptions <trace_options>
#       There are no redirect-specific tracing options. 
#
#------------------------------------------------------------------------------
#
#     The SNMP statement
#        SNMP is not a routing protocol, but a network management protocol.
#     This statement controls whether gated tries to contact the SNMP daemon 
#     to register supported variables. The SNMP daemon must be run 
#     independently. The default is to on, or yes.
#     
#     The syntax is:
#     snmp yes | no | on | off
#     [ {
#        port <port> ;
#        debug ;
#        traceoptions <traceoptions> ;
#     } ] ;
#
#     port <port>
#        By default, the SMUX daemon listens for requests on port 199.
#        gated can be configured to try to contact the SMUX daemon on a
#        different port by explictly specifying the port.
#     debug
#        Specifying this option enables debugging of the ISODE SMUX
#        code. The default is debugging disabled.
#     traceoptions <trace_options>
#        There are no SNMP-specific trace options. 
#
#------------------------------------------------------------------------------
#
#      The ICMP statement
#
#      icmp {
#        traceoptions <trace_options> ;
#      }
#
#      traceoptions <trace_options> ;
#          Specifies the tracing options for ICMP.
#      Packet tracing options (which may be modified with detail and recv):
#        packets
#           All ICMP packets received.
#        redirect
#           Only ICMP REDIRECT packets received.
#        routerdiscovery
#           Only ICMP ROUTER DISCOVERY packets received.
#        info
#           Only ICMP informational packets, which include mask
#           request/response, info request/response, echo request/response and
#           time stamp request/response.
#        error
#           Only ICMP error packets, which include time exceeded, parameter
#           problem, unreachable and source quench.
#
#------------------------------------------------------------------------------
#
#      The Router Discovery Server Statement
#         Enables or disables  the router discovery protocol on routers.
#    
#       routerdiscovery server yes | no | on | off [ {
#          traceoptions <trace_options> ;
#          interface <interface_list>
#             [ minadvinterval <time> ]
#             [ maxadvinterval <time> ]
#             [ lifetime <time> ]
#           ;
#          address <interface_list>
#            [ advertise ] | [ ignore ]
#            [ broadcast ] | [ multicast ]
#            [ ineligible ] | [ preference <preference> ]
#          ;
#       } ] ;
#
#      traceoptions <trace_options>
#         Specifies the Router Discovery tracing options.
#      interface <interface_list>
#         Specifies the parameters that apply to physical interfaces. Note a
#         slight difference in convention from the rest of gated, interface
#         specifies just physical interfaces (such as en0 and tr1), while
#         address specifies protocol (in this case IP) addresses.
#
#        Interface parameters are:
#           maxadvinterval <time>
#              The maximum time allowed between sending broadcast or
#              multicast Router Advertisements from the interface. Must be
#              no less than 4 and no more than 30:00 (30 minutes or 1800
#              seconds). The default is 10:00 (10 minutes or 600 seconds).
#           minadvinterval <time>
#              The minimum time allowed between sending unsolicited
#              broadcast or multicast Router Advertisements from the
#              interface. Must be no less than 3 seconds and no greater than
#              maxadvinterval. The default is 0.75 * maxadvinterval.
#           lifetime <time>
#              The lifetime of addresses in a Router Advertisement. Must be
#              no less than maxadvinterval and no greater than 2:30:00
#              (two hours, thirty minutes or 9000 seconds). The default is 3 *
#              maxadvinterval.
#      address <interface_list>
#         Specifies the parameters that apply to the specified set of addresses
#         on this physical interface. Note a slight difference in convention 
#         from the rest of gated, interface specifies just physical interfaces 
#         (such as en0 and tr1), while address specifies protocol (in this case
#         IP) addresses.  
#            advertise
#              Specifies that the specified address(es) should be included in
#              Router Advertisements. This is the default.
#            ignore
#              Specifies that the specified address(es) should not be included
#              in Router Advertisements.
#            broadcast
#              Specifies that the given address(es) should be included in a
#              broadcast Router Advertisement because this system does not
#              support IP multicasting, or some hosts on attached network
#              do not support IP multicasting. It is possible to mix addresses
#              on a physical interface such that some are included in a
#              broadcast Router Advertisement and some are included in a
#              multicast Router Advertisement. This is the default if the router
#              does not support IP multicasting.
#           multicast
#              Specifies that the given address(es) should only be included in
#              a multicast Router Advertisement. If the system does not
#              support IP multicasting the address(es) will not be included. If
#              the system supports IP multicasting, the default is to include
#              the address(es) in a multicast Router Advertisement if the
#              given interface supports IP multicasting, if not the address(es)
#              will be included in a broadcast Router Advertisement.
#           preference <preference>
#              The preferability of the address(es) as a default router
#              address, relative to other router addresses on the same subnet.
#              A 32-bit, signed, twos-complement integer, with higher values
#              meaning more preferable. Note that hex 80000000 may only
#              be specified as ineligible. The default is 0.
#           ineligible
#              Specifies that the given address(es) will be assigned a
#              preference of (hex 80000000) which means that it is not
#              eligible to be the default route for any hosts.
#
#              This is useful when the address(es) should not be used as a
#              default route, but are given as the next hop in an ICMP
#              redirect. This allows the hosts to verify that the given
#              addresses are up and available.
#
#------------------------------------------------------------------------------
#
#      The Router Discovery Client Statement
#         Enables or disables  the router discovery protocol on routers.
#
#      routerdiscovery client yes | no | on | off [ {
#         traceoptions <trace_options> ;
#         preference <preference> ;
#         interface <interface_list>
#           [ enable ] | [ disable ]
#           [ broadcast ] | [ multicast ]
#           [ quiet ] | [ solicit ]
#         ;
#      } ] ;
#
#     traceoptions <trace_options>
#         Specifies the tracing options for the Router Discovery Client
#         There are no packet tracing options; tracing of the router discocery
#         packets is enabled via the ICMP statement.
#            state - State transitions
#     preference <preference> ;
#        Specifies the preference of all Router Discovery default routes. The
#        default is 55.
#     interface <interface_list>
#        Specifies the parameters that apply to physical interfaces. Note a
#        slight difference in convention from the rest of gated, interface
#        specifies just physical interfaces (such as en0 and tr1). The
#        Router Discovery Client has no parameters that apply only to
#        interface addresses.
#           enable
#             Specifies that Router Discovery should be performed on the
#             specified interface(s). This is the default.
#           disable
#             Specifies that Router Discovery should not be performed on
#             the specified interface(s).
#           broadcast
#             Specifies that Router Solicitations should be broadcast on the
#             specified interface(s). This is the default if IP multicast 
#             support is not available on this host or interface.
#           multicast
#             Specifies that Router Solicitations should be multicast on the
#             specified interface(s). If IP multicast is not available on this
#             host and interface, no solicitation will be performed. The
#             default is to multicast Router Solicitations if the host and
#             interface support it, otherwise Router Solicitations are
#             broadcast.
#           quiet
#             Specifies that no Router Solicitations will be sent on this
#             interface, even though Router Discovery will be performed.
#           solicit
#             Specifies that initial Router Solicitations will be sent on this
#             interface. This is the default.
#
###############################################################################
#  5) Static Statements
#       Define the static routes used by gated. These statements occur after
#       the protocol statements and before any control statements. These routes
#       can be overridden by routes with better preference values.   
#
#     static {
#       ( host <host> ) | default |
#       ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] )
#           gateway <gateway_list>
#            [ interface <interface_list> ]
#            [ preference <preference> ]
#            [ retain ]
#            [ reject ]
#            [ blackhole ]
#            [ noinstall ] ;
#       ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] )
#           interface <interface>
#            [ preference <preference> ]
#            [ retain ]
#            [ reject ]
#            [ blackhole ]
#            [ noinstall ] ;
#      } ;
#
#      host <host> gateway <gateway_list>
#      ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] )
#
#      default gateway <gateway_list>
#          This is the most general form of the static statement. It defines a
#          static route through one or more gateways. 
#
#     Parameters for static routes are:
#     interface <interface_list>
#          When this paramter is specified, gateways are only considered
#          valid when they are on one of these interfaces.
#     preference <preference>
#          This option selects the preference of this static route. The
#          preference controls how this route competes with routes from
#          other protocols. The default preference is 60.
#     retain
#          Normally gated removes all routes except interface routes
#          from the kernel forwarding table during a graceful shutdown.
#          The retain option may be used to prevent specific static
#          routes from being removed. This is useful to insure that some
#          routing is available when gated is not running.
#     reject
#          Instead of forwarding a packet like a normal route, reject
#          routes cause packets to be dropped and unreachable
#          messages to be sent to the packet originators. Specifying this
#          option causes this route to be installed as a reject route. 
#     blackhole
#          A blackhole route is the same as a reject route except
#          that unreachable messages are not supported.
#     noinstall
#          Normally the route with the lowest preference is installed in the
#          kernel forwarding table and is the route exported to other
#          protocols. When noinstall is specified on a route, it will not
#          be installed in the kernel forwarding table when it is active, but
#          it will still be elligible to be exported to other protocols.
#
#   ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] ) interface interface
#     This form defines a static interface route which is used for primitive
#     support of multiple network addresses on one interface. The
#     preference, retain, reject, blackhole and noinstall
#     options are the same as described above.
#
#
##############################################################################
#
#  6) Control Statements
#          Importation of routes from routing protocol peers and
#          exportation of routes to routing protocol peers are
#          controlled  by "import" and "export" clauses.
#
#     1)The Import Clause
#        Importation of routes from routing protocols and installation of 
#        the routes in gated's routing database is controlled by import 
#        statements. The format of an import statement varies depending on the 
#        source protocol.
#
#     Specifying preferences
#
#     In all cases, one of two keywords may be specified to control how routes
#i    compete with other protocols:
#
#        restrict
#          Specifies that the routes are not desired in the routing table. This
#          prevents them from becoming active so they will not be installed in 
#          the forwarding table, or exported to other protocols.
#        preference <preference>
#          Specifies the preference value used when comparing this route to
#          other routes from other protocols. The route with the lowest
#          preference available at any given route becomes the active route, is
#          installed in the forwarding table, and is eligible to be exported to
#          other protocols. The default preferences are configured by the
#          individual protocols.
#
#------------------------------------------------------------------------------
#
#    Importing routes from BGP and EGP
#
#      import proto bgp | egp autonomoussystem <autonomous_system>
#         restrict ;
#      import proto bgp | egp autonomoussystem <autonomous_system>
#        [ preference <preference> ] {
#          route_filter [ restrict | ( preference <preference> ) ] ;
#        } ;
#
#       import proto bgp aspath <aspath_regexp>
#         origin any | ( [ igp ] [egp ] [ incomplete ] )
#         restrict ;
#       import proto bgp aspath <aspath_regexp>
#         origin any | ( [ igp ] [egp ] [ incomplete ] )
#         [ preference <preference> ] {
#            <route_filter> [ restrict | ( preference <preference> ) ] ;
#         } ;
#
#  EGP importation may be controlled by autonomous system. BGP also
#  supports controlling propagation by the use of an AS path regular
#  expressions, which are documented in the section on Matching AS paths.
#  Note that EGP and BGP versions 2 and 3 only support the propagation of
#  natural networks, so the host and default route filters are meaningless.
#  BGP version 4 supports the propagation of any destination along with a
#  contiguous network mask.
#
#  EGP and BGP both store any routes that were rejected implicitly by not
#  being metioned in a route filter, or explicitly with the restrict keyword in
#  the routing table with a negative preference. A negative preference prevents
#  a route from becoming active, which prevents it from being installed in the
#  forwarding table, or exported to other protocols. This aleviates the need to
#  break and re-establish a session upon reconfiguration if importation policy
#  is changed.
#
#----------------------------------------------------------------------------
#
#    Importing routes from an RIP, HELLO and Redirects
#
#    import proto rip | hello | redirect
#       [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#       restrict ;
#    import proto rip | hello | redirect
#       [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#       [ preference <preference> ] {
#       <route_filter> [ restrict | ( preference <preference> ) ] ;
#       } ;
#
#   The importation of RIP, HELLO and Redirect routes may be controlled by
#   any protocol, source interface and/or source gateway. If more than one is
#   specified, they are processed from most general (protocol) to most specific
#   (gateway).
#
#   RIP and HELLO don't support the use of preference to choose between
#   routes of the same protocol. That is left to the protocol metrics. These
#   protocols do not save routes that were rejected since they have short
#   update intervals.
#
#-----------------------------------------------------------------------------
#
#    Importing routes from OSPF
#
#    import proto ospfase [ tag <ospf_tag> ] restrict ;
#    import proto ospfase [ tag <ospf_tag> ]
#       [ preference <preference> ] {
#         <route_filter> [ restrict | ( preference <preference> ) ] ;
#       } ;
#
#   Due to the nature of OSPF, only the importation of ASE routes may be
#   controlled. OSPF intra- and inter-area routes are always imported into the
#   gated routing table with a preference of 10. If a tag is specified, the
#   import clause will only apply to routes with the specified tag.
#
#   It is only possible to restrict the importation of OSPF ASE routes when
#   functioning as an AS border router. This is accomplished by specifying an
#   export ospfase clause. Specification of an empty export clause may be
#   used to restrict importation of ASEs when no ASEs are being exported.
#
#   Like the other interior protocols, preference can not be used to choose
#   between OSPF ASE routes, that is done by the OSPF costs. Routes that
#   are rejected by policy are stored in the table with a negative preference.
#
#-----------------------------------------------------------------------------
#
#     2)The Export Clause
#         Controls which routes are advertised by gated to other systems. The
#         syntax of the export statement varies slightly per protocol. 
#         The syntax of the export statement is similar to the syntax of the 
#         import statement, and the meanings of many of the parameters are 
#         identical. The main difference between the two is that while route 
#         importation is just controlled by source information, route 
#         exportation is controlled by both destination and source.
#
#         The outer portion of a given export statement specifies the 
#         destination of the routing information you are controlling. The 
#         middle portion restricts the sources of importation that you wish 
#         to consider. And the innermost portion is a route filter used to 
#         select individual routes.
#
#
#   Specifying metrics
#
#   The most specific specification of a metric is the one applied to the route
#   being exported. The values that may be specified for a metric depend on the
#   destination protocol that is referenced by this export statement.
#
#   restrict
#     Specifies that nothing should be exported. If specified on the
#     destination portion of the export statement it specifies that nothing at
#     all should be exported to this destination. If specified on the source
#     portion it specifies that nothing from this source should be exported
#     to this destination. If specified as part of a route filter it specifies
#     that the routes matching that filter should not be exported.
#   metric <metric>
#     Specifies the metric to be used when exporting to the specified
#     destination.
#
#------------------------------------------------------------------------------
#
#  Exporting to EGP and BGP
#
#  export proto bgp | egp as <autonomous system>
#    restrict ;
#  export proto bgp | egp as <autonomous system>
#    [ metric <metric> ] {
#     <export_list> ;
#    } ;
#
#  Exportation to EGP and BGP is controlled by autonomous system, the
#  same policy is applied to all routers in the AS. EGP metrics range from 0 to
#  255 inclusive with 0 being the most attractive.
#
#  BGP metrics are 16 bit unsigned quantities, i.e. they range from 0 to 65535
#  inclusive with 0 being the most attractive.
#
#  If no export policy is specified, only routes to attached interfaces will be
#  exported. If any policy is specified the defaults are overridden; it is
#  necessary to explicitly specify everything that should be exported.
#
#  Note that EGP and BGP versions 2 and 3 only support the propagation of
#  natural networks, so the host and default route filters are meaningless.
#  BGP version 4 supports the propagation of any destination along with a
#  contiguous network mask.
#
#------------------------------------------------------------------------------
#
#  Exporting to RIP and HELLO
#
#  export proto rip | hello
#    [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#    restrict ;
#  export proto rip | hello
#    [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#    [ metric <metric> ] {
#    <export_list> ;
#    } ;
#
#  Exportation to RIP and HELLO is controlled by any protocol, interface
#  or gateway. If more than one is specified, they are processed from most
#  general (protocol) to most specific (gateway).
#
#  It is not possible to set metrics for exporting RIP routes into RIP, or
#  exporting HELLO routes into HELLO. Attempts to do this are silently
#  ignored.
#
#  If no export policy is specified, RIP and interface routes are exported into
#  RIP and HELLO and interface routes are exported into HELLO. If any
#  policy is specified the defaults are overridden; it is necessary to
#  explicitly specify everything that should be exported.
#
#  RIP version 1 and HELLO assume that all subnets of the shared network
#  have the same subnet mask so they are only able to propagate subnets of
#  that network. RIP version 2 removes that restriction and is capable of
#  propagating all routes when not sending version 1 compatible updates.
#
#  To announce routes which specify a next hop of the loopback interface (i.e.
#  static and internally generated default routes) via RIP or HELLO, it is
#  necessary to specify the metric at some level in the export clause. Just
#  setting a default metric for e.g. RIP or HELLO is not sufficient. This is a
#  safeguard to verify that the announcement is intended.
#
#------------------------------------------------------------------------------
#  Exporting to OSPF
#
#  export proto osfpase [ type 1 | 2 ] [ tag <ospf_tag> ]
#    restrict ;
#  export proto osfpase [ type 1 | 2 ] [ tag <ospf_tag> ]
#    [ metric <metric> ] {
#    <export_list> ;
#    } ;
#
#  It is not possible to create OSPF intra- or inter-area routes by exporting
#  routes from the gated routing table into OSPF. It is only possible to export
#  from the gated routing table into OSPF ASE routes. It is also not possible
#  to control the propagation of OSPF routes within the OSPF protocol.
#
#  There are two types of OSPF ASE routes, type 1 and type 2, see the
#  OSPF protocol configuration for a detailed explaination of the two types.
#  The default type is specified by the defaults subclause of the ospf
#  clause. This may be overridden by a specification on the export statement.
#
#  OSPF ASE routes also have the provision to carry a tag. This is an
#  arbitrary 32 bit number that can be used on OSPF routers to filter routing
#  information. See the OSPF protocol configuration for detailed information
#  on OSPF tags. The default tag specified by the ospf defaults clause may
#  be overridden by a tag specified on the export statement.
#
#------------------------------------------------------------------------------
#  Specifying the source
#   The export list specifies export based on the origin of a route and the
#   syntax varies depending on the source.
#
#------------------------------------------------------------------------------
#
#   Exporting BGP and EGP routes
#
#   proto bgp | egp autonomoussystem <autonomous_system>
#     restrict ;
#   proto bgp | egp autonomoussystem <autonomous_system>
#      [ metric <metric> ] {
#      <route_filter> [ restrict | ( metric <metric> ) ] ;
#   } ;
#
#   BGP and EGP routes may be specified by source autonomous system. All
#   routes may be exported by as path, see below for more information.
#
#------------------------------------------------------------------------------
#
#  Exporting RIP and HELLO routes
#
#  proto rip | hello
#    [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#    restrict ;
#  proto rip | hello
#    [ ( interface <interface_list> ) | (gateway <gateway_list> ) ]
#    [ metric <metric> ] {
#    <route_filter> [ restrict | ( metric <metric> ) ] ;
#  } ;
#
#  RIP and HELLO routes may be exported by protocol, source interface
#  and/or source gateway.
#
#------------------------------------------------------------------------------
#
#  Exporting OSPF routes
#
#  proto ospf | ospfase restrict ;
#  proto ospf | ospfase [ metric <metric> ] {
#    <route_filter> [ restrict | ( metric <metric> ) ] ;
#  } ;
#
#  Both OSPF, and OSPF ASE routes may be exported into other protocols.
#
#------------------------------------------------------------------------------
#
#  Exporting routes from non-routing protocols
#
#  Non-routing with interface
#
#  proto direct | static | kernel
#    [ (interface <interface_list> ) ]
#    restrict ;
#  proto direct | static | kernel
#    [ (interface <interface_list> ) ]
#    [ metric <metric> ] {
#    <route_filter> [ restrict | ( metric <metric> ) ] ;
#   } ;
#
#  These protocols may be exported by protocol, or by the interface of the
#  next hop. These protocols are:
#
#  direct -  Routes to directly attached interfaces.
#  static -  Static routes specified in a static clause.
#
#------------------------------------------------------------------------------
#
#   Non-routing by protocol
#
#   proto default | aggregate
#      restrict ;
#   proto default | aggregate
#      [ metric <metric> ] {
#      <route_filter> [ restrict | ( metric <metric> ) ] ;
#      } ;
#
#  These protocols may only be referenced by protocol.
#
#  default
#     Refers to routes created by the gendefault option. It is
#     recommended that route generation be used instead.
#  aggregate
#     Refers to routes synthesized from other routes when the aggregate
#     and generate statements are used. See the section on Route
#     Aggregation for more information.
#
#----------------------------------------------------------------------------
#
#  Exporting by AS path
#
#  proto <proto> | all aspath <aspath_regexp>
#     origin any | ( [ igp ] [egp ] [ incomplete ] )
#     restrict ;
#  proto <proto> | all aspath <aspath_regexp>
#     origin any | ( [ igp ] [egp ] [ incomplete ] )
#     [ metric <metric> ] {
#     <route_filter> [ restrict | ( metric <metric> ) ] ;
#     } ;
#
#  When BGP is configured, all routes are assigned an AS path when they are
#  added to the routing table. For all interior routes this AS path specifies
#  IGP as the origin and no ASes in the AS path (the current AS is added when
#  the route is exported). For EGP routes this AS path specifies EGP as the
#  origin and the source AS as the AS path. For BGP routes, the AS path is
#  stored as learned from BGP.
#
#  AS path regular expressions are documented in the section on Matching AS
#  paths.
#
#------------------------------------------------------------------------------
#
#  Exporting by route Tag
#
#  proto <proto> | all tag <tag> restrict ;
#  proto <proto> | all tag <tag>
#      [ metric <metric> ] {
#      <route_filter> [ restrict | ( metric <metric> ) ] ;
#      } ;
#
#  Both OSPF and RIP version 2 currently support tags, all other protocols
#  always have a tag of zero. The source of exported routes may be selected
#  based on this tag. This is useful when routes are classified by tag when the
#  are exported into a given routing protocol.
#
#------------------------------------------------------------------------------
#
# Route Aggregation
#
#  Route aggregation is a method of generating a more general route given the
#  presence of a specific route. It is used, for example, at an autonomous
#  system border to generate a route to a network to be advertised via EGP
#  given the presence of one or more subnets of that network learned via RIP.
#  Aggregation must be explicitly configured. No aggregation is performed
#  unless explicitly requested in an aggregate statement.
#
#  Aggregation and Generation syntax
#
#  aggregate default
#    | ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] )
#    [ preference <preference> ] [ brief ] {
#    proto [ all | direct | static | kernel | aggregate | proto ]
#        [ ( as <autonomous system> ) | ( tag <tag> )
#            | ( aspath <aspath_regexp> ) ]
#        restrict ;
#    proto [ all | direct | static | kernel | aggregate | proto ]
#        [ ( as <autonomous system> ) | ( tag <tag> )
#            | ( aspath <aspath_regexp> ) ]
#        [ preference <preference> ] {
#        <route_filter> [ restrict | ( preference <preference> ) ] ;
#        } ;
#    } ;
#
#  generate default
#    | ( <network> [ ( mask <mask> ) | ( masklen <number> ) ] )
#    [ preference <preference> ] {
#        [ ( as <autonomous system> ) | ( tag <tag> )
#            | ( aspath <aspath_regexp> ) ]
#        restrict ;
#    proto [ all | direct | static | kernel | aggregate | proto ]
#        [ ( as <autonomous system> ) | ( tag <tag> )
#            | ( aspath <aspath_regexp> ) ]
#        [ preference <preference> ] {
#        <route_filter> [ restrict | ( preference <preference> ) ] ;
#        } ;
#   } ;
#
#  Routes that match the route filters are called contributing routes. They are
#  ordered according to the aggregation preference that applies to them. If
#  there are more than one contributing routes with the same aggregating
#  preference, the route's own preferences are used to order the routes. The
#  preference of the aggregate route will be that of contributing route with the
#  lowest aggregate preference.
#
#  preference <preference>
#     Specifies the preference to assign to the resulting aggregate route.
#     The default preference is 130.
#  brief
#     Used to specify that the AS path should be truncated to the longest
#     common AS path. The default is to build an AS path consisting of
#     SETs and SEQUENCEs of all contributing AS paths.
#  proto <proto>
#     In addition to the special protocols listed, the contributing protocol
#     may be chosen from among any of the ones supported (and currently
#     configured into) gated.
#  as <autonomous_system>
#     Restrict selection of routes to those learned from the specified
#     autonomous system.
#  tag <tag>
#     Restrict selection of routes to those with the specified tag.
#  aspath <aspath_regexp>
#     Restrict selection of routes to those that match the specified AS path.
#  restrict
#     Indicates that these routes are not to be considered as contributors of
#     the specified aggregate. The specified protocol may be any of the
#     protocols supported by gated.
#  <route_filter>
#     See section on route filters.
#
#  A route may only contribute to an aggregate route which is more general
#  than itself; it must match the aggregate under its mask. Any given route may
#  only contribute to one aggregate route, which will be the most specific
#  configured, but an aggregate route may contribute to a more general
#  aggregate.
#
#------------------------------------------------------------------------------
#
#  Route Filters
#
#  Routes are filtered by specifying configuration language that will match a
#  certain set of routes by destination, or by destination and mask. Among
#  other places, route filters are used on martians, import and export
#  statements.
#
#  The action taken when no match is found is dependent on the context, for
#  instance import and export route filters assume an all reject ; at the
#  end a list.
#
#  A route will match the most specific filter that applies. Specifying more
#  than one filter with the same destination, mask and modifiers will generate
#  an error.
#
#
#  Filtering syntax
#
#    <network> [ exact | refines ]
#    <network> mask <mask> [ exact | refines ]
#    <network> masklen <number> [ exact | refines ]
#    all
#    default
#    host <host>
#
#  These are all the possible formats for a route filter. Not all of these
#  formats are available in all places, for instance the host and default
#  formats are not valid for martians.
#
#  In most cases it is possible to specify additional parameters relevent to the
#  context of the filter. For example, on a martian statement it is possible to
#  specify the allow keyword, on an import statement you can specify a
#  preference, and on a export you can specify a metric.
#
#  <network> [ exact | refines ]
#  <network> mask <mask> [ exact | refines ]
#  <network> masklen <number> [ exact | refines ]
#     Matching usually requires both an address and a mask, although the
#     mask is implied in the shorthand forms listed below. These three
#     forms vary in how the mask is specified. In the first form, the mask is
#     implied to be the natural mask of the network. In the second, the
#     mask is explicitly specified. In the third, the mask is specified by the
#     number of contiguous one bits.
#
#     If no additional parameters are specified, any destination that falls in
#     the range given by the network and mask is matched, the mask of the
#     destination is ignored. If a natural network is specified, the network,
#     any subnets, and any hosts will be match. The two optional modifiers
#     cause the mask of the destination to be considered also:
#     exact
#          This parameter specifies that the mask of the destination must
#          match the supplied mask exactly. This is used to match a
#          network, but no subnets or hosts of that network.
#     refines
#          Specifies that the mask of the destination must be more
#          specified (i.e. longer) than the filter mask. This is used to
#          match subnets and/or hosts of a network, but not the network.
#  all
#    This entry matches anything. It is equivalent to:
#
#          0.0.0.0 mask 0.0.0.0
#
#
#  default
#    Matches the default route. To match, the address must be the
#    default address and the mask must be all zeros. This is equivalent to:
#
#          0.0.0.0 mask 0.0.0.0 exact
#
#
#  host <host>
#     Matches the specific host. To match, the address must exactly match
#     the specified host and the network mask must be a host mask (i.e. all
#     ones). This is equivalent to:
#
#          host mask 255.255.255 exact
#
#------------------------------------------------------------------------------
#
#  Matching AS paths
#
#  An AS path is a list of autonomous_systems that routing information has
#  passed through to get to this router, and an indicator of the origin of the
#  AS path. This information can be used to prefer one path to a destination
#  network over another. The primary method for doing this with gated is to
#  specify a list of patterns to be applied to AS paths when importing and
#  exporting routes.
#
#  Each autonomous system that a route passed through prepends it's AS
#  number to the beginning of the AS path.
#
#  The origin information details the completeness of AS path information. An
#  origin of igp indicates the route was learned from an interior routing
#  protocol and is most likely complete. An origin of egp indicates the route
#  was learned from an exterior routing protocol that does not support AS
#  paths (EGP for example) and the path is most likely not complete. When
#  the path information is definitely not complete, an origin of incomplete is
#  used.
#
#  AS path regular expressions are defined in RFC 1164 section 4.2.
#
#
#  AS path matching syntax
#
#  An AS path is matched using the following syntax.
#
#  aspath aspath_regexp origin any | ( [ igp ] [egp ] [ incomplete ] )
#
#  This specifies that an AS matching the aspath_regexp with the specified
#  origin is matched.
#
#  AS path regular expressions
#
#  Technically, an AS path regular expression is a regular expression with the
#  alphabet being the set of AS numbers. An AS path regular expression is
#  composed of one or more AS paths expressions. An AS path expressions
#  is composed of AS path terms and AS path operators.
#
#  AS path terms
#
#  An AS path term is one of the following three objects:
#
#    autonomous_system
#    .
#    ( aspath_regexp )
#
#  autonomous_system
#     Is any valid autonomous system number, from one through 65534
#     inclusive.
#     .
#     matches any autonomous system number.
#     ( aspath_regexp )
#     parentheses group subexpressions--an operator, such as * or ?
#     works on a single element or on a regular expression enclosed in
#     parentheses
#
#  AS path operators
#
#  An AS path operator is one of the following:
#
#    aspath_term {m,n}
#    aspath_term {m}
#    aspath_term {m,}
#    aspath_term *
#    aspath_term ?
#    aspath_term | aspath_term
#
#  aspath_term {m,n}
#     a regular expression followed by {m,n} (where m and n are both
#     non-negative integers and m <= n) means at least m and at most n
#     repetitions.
#  aspath_term {m}
#     a regular expression followed by {m} (where m is a positive integer)
#     means exactly m repetitions.
#  aspath_term {m,}
#     a regular expression followed by {m,} (where m is a positive integer)
#     means m or more repetitions.
#  aspath_term *
#     an AS path term followed by * means zero or more repetitions. This
#     is shorthand for {0,}.
#  aspath_term +
#     a regular expression followed by + means one or more repetitions.
#     This is shorthand for {1,}.
#  aspath_term ?
#     a regular expression followed by ? means zero or one repetition.
#     This is shorthand for {0,1}.
#  aspath_term | aspath_term
#     matches the AS term on the left, or the AS term on the right.
#
##############################################################################
#
#  Sample setups.
#
##############################################################################
#
#  Simple RIP quiet
#	This configuration runs RIP in quiet mode, it only listens to
#	packets, no matter how many interfaces are configured.
#	It traces all trace output to a file called /var/tmp/rip.quiet.trace.
#	The tracefile options allow the creation of 4 files to rotate trace
#	information.  Each of these trace files will grow to about 50K bytes
#	before rotating to the next trace file.  The trace files will be called,
#	/var/tmp/rip.quite.trace, /var/tmp/rip.quite.trace.0,
#	/var/tmp/rip.quite.trace.1, and /var/tmp/rip.quite.trace.2.
#
# traceoptions tracefile "/var/tmp/rip.quiet.trace" replace size 50k
#	files 4 all ;
#
# rip yes {
#        nobroadcast ;
# } ;
#
##############################################################################
#
#  Simple RIP supplier
#	Run as a RIP supplier, do not supply RIP packets to
#	tr0, and only listen to RIP packets from 192.100.110.1.
#
# rip yes {
#	broadcast ;
#	interface tr0 noripout ;
#	trustedgateways 192.100.110.1 ;
# } ;
#
##############################################################################
#
#  Simple EGP
#	This host is in autonomous system 283.  Verify neighbor
#	192.35.82.100 is in autonomous system 145.  Do not
#	generate a default route from EGP information learned.
#
# autonomoussystem 283;
#
# egp yes {
#	group peeras 145 {
#		neighbor 192.100.110.100 nogendefault ;
#	} ;
# } ;
#
##############################################################################
#
#  Simple BGP
#	This host is in autonomous system 283.  Verify peer
#	192.100.110.1 is in autonomous system 145.
#
# autonomoussystem 283;
#
# bgp yes {
#	group type
#	   External peeras 145 {
# 		peer 192.100.110.1 ;
#	} ;
# } ;
#
##############################################################################
#Sample Host Configurations
#
#End system configuration is simple, usually containing only two configuration
#statements. The configuration shown here emulates routed. It runs RIP,
#and it only sends updates if there is more than one interface up and IP
#forwarding is enabled in the kernel.
#
#    #
#    rip yes ;
#    #
#
#Note: RIP will not run if UDP checksums are disabled in the kernel.
#
##############################################################################
#
#This configuration runs RIP in quiet mode; it only listens to packets, no
#matter how many interfaces are configured.
#
#    #
#    rip yes ;
#    {
#        nobroadcast ;
#    } ;
#    #
#
##############################################################################
#
#This configuration should work for any system that runs RIP and has only
#one network interface.
#
#    #
#    # don't time-out the network interface
#    #
#    interface 136.66.12.2 passive ;
#    #
#    # enable rip
#    #
#    rip yes ;
#    #
#
#The keyword passive prevents gated from changing the preference of the
#route to this interface if it is believed to be down due to lack of received
#routing information. The purpose of the interface passive statement is to
#identify a router with a guest host on an Ethernet. In this example the route
#is through the directly attached network interface. Normally when gated
#thinks an interface is down, it removes it from the routing database to
#prevent a gateway from announcing that it can route data through a
#non-operational interface. If the host has only one interface, it should not
#be removed from the routing database even if the interface is down i.e. the
#statement interface 136.66.12.2 passive in this configuration. RIP is enabled
#with a rip yes statement. This statement is not required as it is the default
#but the explicit statement in the gated.conf file serves to document the
#configuration preventing future confusion.
#
##############################################################################
#
#RIP only, subnet to backbone
#
#Gateway configurations are more complicated than a simple host
#configuration as gateways have multiple interfaces and may run multiple
#protocols. This sample configuration file connects two nets within an
#autonomous system. This configuration can be used for any gateway that
#uses only RIP and that connects a single subnet to a larger network.
#
#    #
#    # enable rip
#    #
#    rip yes ;
#    #
#    #  using  rip,  announce subnet 3 via  interface 136.66.1.2
#    export proto rip interface 136.66.1.2
#    {
#        proto direct
#        {
#            announce 136.66.3.0 metric 0 ;
#        } ;
#    } ;
#    #
#    #  using  rip, announce all routes learned from interface 136.66.1.2
#    #
#    export proto rip interface 136.66.3.1
#    {
#        proto rip interface 136.66.1.2
#        {
#            announce all ;
#        } ;
#    } ;
#
#The configuration contains two export statements. The first one tells gated
#to announce, via the RIP protocol and interface 136.66.1.2 a direct route to
#subnet 136.66.3.0. The second route announces to subnet 3 all routes
#learned from the interface 136.66.12. This includes subnet routes and any
#routes to the rest of the world, including default routes. The first export
#statement was not required since by default gated announces every
#network that is directly connected to the gateway. The first export statement
#was explicitly entered to document the intended structure. In any export 
#statement the main proto clause and the main interface clause
#may define the protocol and interface through which the routes are
#advertised. Subsidiary proto and interface clauses define the protocols and
#the interfaces from which the routes must be learned.
#
#############################################################################
#
#RIP with default announcement
#
#If the gateway only runs RIP and connects a local backbone to a subnet
#which in turn provides a gateway to the outside world, the file is configured
#differently. In this example, the gateway announces a default route to the
#backbone and announces all of the individual subnet routes to the outside
#world.
#
#    #
#    # enable rip
#    #
#    rip yes ;
#    #
#    #  using  rip, announce all local subnets via 136.66.12.3
#    #
#    export proto rip interface 136.66.12.3 metric 3
#    {
#        proto rip interface 136.66.1.5
#        {
#            announce all ;
#        } ;
#    };
#    #
#    #  using  rip,  announce default  to  the  local backbone via 136.66.1.5
#    #
#    export proto rip interface 136.66.3.1
#    {
#        proto rip interface 136.66.12.3
#        {
#            announce 0.0.0.0 ;
#        } ;
#    } ;
#
#The first export statement statement explictly directs gated to announce all
#of the routes it learns from interface 136.66.1.5 out through interface
#136.66.12.3. The explicit announce all is not required. The metric value is
#specified in the main statement and applies to every route announced via this
#protocol and interface. When the metric is specified in the export clause it
#only applies to the routes specified in that clause. In this example metric 3
#applies to every route announced over interface 136.66.12.3 via RIP.
#
##############################################################################
#
#RIP and OSPF
#
#This configuration for AS 283 enables both RIP and OSPF protocols and
#can be used for testing RIP and OSPF.
#
#    #options noinstall ;
#    interfaces {
#       interface le0 passive ;
#    } ;
#    autonomoussystem 283 ;
#    snmp yes ;
#    rip yes {
#       broadcast ;
#      defaultmetric 5 ;
#       interface le version 2 multicast ;
#    } ;
#   ospf yes {
#       monauthkey "ZZZZZZZZ" ;
#       backbone {
#            authtype simple ;
#            interface all {
#                 priority 2 ;
#            interface le {
#                 authkey "YYYYYYYY" ;
#            } ;
#       | ;
#    } ;
#    static {
#        default  gateway 132.236.200.200  preference 140 retain ;
#    }
#
#In the RIP case version 2 multicast packets are generated on all ethernet
#interfaces (le0, le1...). This is a safe way to test RIP since the production
#gateways on this network do not support RIP version 2. In the OSPF case,
#all interfaces are configured to be Priority 2 so the Proteon routers
#(Priority 0) will become designated routers. A simple password is specified
#"YYYYYYYY" for authentication of all Ethernet interfaces. (The only kind
#of interfaces in this configuration.)
#
##############################################################################
#
#Sample BGP4+ Configuration
#
#traceoptions "/tmp/gated.log" replace size 1m files 7 general;
#
#autonomous-system 777;
#
#router-id 128.93.30.39;
#
#rip off;
#ripng off;
#
#bgp4+ on {
#	group type external peeras 775 {
#		peer 5f06:b500:c133:c100:f0:0:c05d:171;
#	};
#	traceoptions packets detail update;
#};
#
#static {
#	inet6 5f01:: masklen 16 gateway fe80::20:fe00:8781 retain;
#};
#
#aggregate 5f06:b500:805d:: masklen 64 {
#	proto all {
#		5f06:b500:805d:: masklen 64;
#	};
#};
#
#export inet6 proto bgp4+ as 775 { proto static { 5f01:: masklen 16; }; proto
#aggregate { 5f00:: masklen 8; }; };
#
##############################################################################
#
#Sample RIPNG configuration
#
#traceoptions "/tmp/gated.log" replace size 1m files 7 general;
#
#autonomous-system 775;
#
#router-id 128.93.30.39;
#
#rip off;
#ripng on;
#bgp4+ off;
#
#static {
#	inet6 5f01:: masklen 16 gateway 5f06:b500:805d::20:fe00:8781 retain;
#};
#
#export inet6 proto ripng { proto static metric 4 { 5f01:: masklen 16; }; proto
#direct { 5f06:b500:c133:c100:80:: masklen 80 exact; }; };
#
#
##############################################################################
#
#Sample Preference Specifications
#
#    interfaces {
#            interface 138.66.12.2 preference 10 ;
#    } ;
#    rip yes {
#        preference 90 ;
#    } ;
#    import proto rip gateway 138.66.12.1 preference 75 ;
#
#In these statements the preference applicable to routes learned via RIP from
#gateway 138.66.12.1 is 75. The last preference applicable to routes learned
#via RIP from gateway 128.66.12.1 is defined in the accept statement. The
#preference applicable to other RIP routes is found in the rip statement. The
#preference set on the interface statement applies only to the route to that
#interface.
#
##############################################################################