# @(#)61 1.6 src/tcpip/etc/gated.conf, tcprouting, tcpip720 12/6/93 14:23:11 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # tcpip720 src/tcpip/etc/gated.conf 1.6 # # Licensed Materials - Property of IBM # # COPYRIGHT International Business Machines Corp. 1985,1989 # 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 # # COMPONENT_NAME: TCPIP gated.conf # # FUNCTIONS: # # ORIGINS: 27 # # (C) COPYRIGHT International Business Machines Corp. 1985, 1989 # All Rights Reserved # Licensed Materials - Property of IBM # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # # gated configuration file # ############################################################################## # # How to configure this file for your system: # # Statement classes. # There are eight classes of statements. The first two may # be specified in the configuration file in any order. # # directives # These statements are immediately acted upon by the # parser. They are used to specify included files and # the directory in which the reside. Unlike other # statements which terminate with a semi-colon (;), # directive statements terminate with a newline # character. # trace # These statements control tracing options. # # The six remaining classes must be specified in order: # # options # These statements allow specification of some global # options. # interface # These statements specify interface options. # definition # These statements options, the autonomous system and # martian networks. # protocol # These statements enable or disable protocols and set # protocol options. # route # These statements define static routes. # control # These statements define routes that are imported from # routing peers and routes that are exported to these # peers. # # Statements within a class may be listed in any order. # ############################################################################## # # 1) Directive Statements # Set optional directive statements. # # %directory "" # # Sets the current directory to . This is the # path that gated uses to look for included files that do # not begin with "/". # # %include "filename" # # Causes the specified file to be parsed completely before resuming # this file. Nesting up to 10 levels is supported. # ############################################################################## # # 2) Trace Statements # Set optional trace statements. # # tracefile ["filename" [replace]] [size [k|m] files ] ; # # Specifies the file to contain tracing output. If a filename is # specified, trace information is appended to this file unless "replace" # specified. # If specified, and cause the trace file to be limited # to , with files kept (including the active file). The # backup file names are created by appending a period and a number to # the trace file name, starting with ".0". The minimum size that can # be specified is 10k, the minimum number of files that can be specified # is 2. The default is not to rotate log files. # # traceoptions [ [ ... ]] [except [ [ ... ]]]; # # Where "traceoption" is: # # all, general, internal, external, nostamp, kernel, mark, task, # timer, parse, route, kernel, bgp, egp, rip, hello, icmp, snmp, # protocol, or update. # ############################################################################## # # 3) Options Statements # options ; # Sets gated options: # # noinstall Do not change kernel's routing table. # Useful for verifying configuration # files. # # gendefault # BGP and EGP neighbors should cause the # internal generation of a default route # when up. This route will not be # installed in the kernel's routing table, # but may be announced by other protocols. # Announcement is controlled by # referencing the special protocol # "default". # # nosend Do not send any packets. This allows # running 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 and possibly # the SMUX SNMP interface. This does not # yet apply to BGP packets. # # noresolv Do not try to resolv symbolic names into # IP addresses by using the host/network # tables or Domain Name System. This is # intended for systems where a lack of # routing information could cause a DNS # lookup to hang. # # syslog Controls the amount of data gated logs # via syslog on systems where setlogmask() # is supported. The log_levels and other # terminology are as defined in the # setlogmask() man page. The default is # equivalent to "syslog upto info". # ############################################################################## # # 4) Interface Statements # interfaces { # options [strictifs] [scaninterval