NAME
	  gated	 - The gateway routing daemon

     SYNOPSIS
	  gated	[-teiHprRu]

	  The gated daemon processes multiple routing protocols
	  according to the configuration set in	gated.conf file.

     FLAGS
	  -e   Logs all	external errors	due to EGP, exterior routing
	       errors, and EGP state changes.

	  -H   Traces all HELLO	packets	received.

	  -i   Logs all	internal errors	and interior routing errors.

	  -p
	       Traces all EGP packets sent and received.

	  -R   Traces all RIP packets received.

	  -r   Logs all	routing	changes.

	  -t   If used alone, the -t flag starts the -i, -e, -r, and
	       -p trace	flags.
	       When used with another flag, the	-t flag	has no effect
	       and only	the accompanying flags are recognized. Note
	       that when other flags are used, the -t flag must	be
	       used with them and must be the first flag given in the
	       command line.

	  -u   Logs all	routing	updates	sent.
	       The gated daemon	always logs fatal errors. If no	log
	       file is specified and none of the preceding trace flags
	       are set,	all messages are sent to the /dev/null file.

     DESCRIPTION
	  The gated daemon manages multiple routing protocols, includ-
	  ing the Routing Information Protocol (RIP), Exterior Gateway
	  Protocol (EGP), and Local Network Protocol (HELLO). The
	  gated	process	can be configured to perform all or any	combi-
	  nation of these routing protocols. It	replaces daemons that
	  use the HELLO	routing	protocol; for example, routed (8) and
	  egpup	(8). The configuration for the gated daemon is by
	  default stored in the	/etc/gated.conf	file, and can be
	  changed at compile time in the file defs.h.  The gated dae-
	  mon stores its process ID in the /etc/gated/pid file.

	  When a routing update	indicates that the route in use	is
	  being	deleted, the gated daemon waits	for 2 minutes before
	  deleting the route.  Be aware	that unpredictable results may
	  occur	when the gated and routed daemons are run together on
	  the same host.

	  Start	the gated daemon with a	log file that you specify on
	  the command line. You	can also enter one or more trace flags
	  on the command line or specify the flags in the traceflags
	  stanza of the	gated.conf configuration file. When trace
	  flags	are specified without a	log file, all trace output is
	  sent to the controlling terminal.

	  By default, the gated	daemon forks and detaches itself from
	  the controlling terminal.

	  When certain networks	are restricted from using the Internet
	  network, the gated daemon uses both the syslogd daemon at
	  the LOG_WARNING log level and	the LOG_DAEMON facility	to
	  record all invalid networks.

	  If you use the EGP when you supply the default route (by the
	  RIP or HELLO gateway)	and all	EGP neighbors are lost,	the
	  default route	is not advertised until	at least one EGP
	  neighbor is regained.

	  The RIP both propagates and listens to host routes.  This
	  allows the gated daemon to handle point-to-point links with
	  consistency.	The gated daemon also supports the RIP_TRACE
	  commands.

	  The gated daemon detects changes made	to the network inter-
	  faces	and its	own start-up flags while it is running.	Thus,
	  you need not restart the gated daemon	if you change the con-
	  figuration. However, if the net mask,	subnet mask, broadcast
	  address, or interface	metric is changed, use the ifconfig(8)
	  command to mark the interface	down and then up 30 seconds
	  later.

	  Subnet interfaces are	supported. Subnet information is
	  passed through interfaces to other subnets of	the same net-
	  work.

	  The gated daemon listens to host and network REDIRECT	sig-
	  nals.	The daemon tries to take an action for its own inter-
	  nal tables. This action is parallel to the action the	kernel
	  takes	on the REDIRECT	signal.
	  In addition, the gated daemon	cancels	(times out) all	routes
	  learned from REDIRECT	signals	in 6 minutes. The daemon then
	  deletes the route from the kernel routing tables, which
	  keeps	the routing tables consistent.
	  No routing protocol announces	routes learned from REDIRECT
	  signals.

	  The gated EGP	code verifies that all networks	sent and
	  received are valid class A, B, or C networks as specified by
	  the EGP. The gated daemon does not contribute	information
	  about	networks that do not meet EGP specifications. If an
	  EGP update packet contains information about a network that
	  is not class A, B, or	C, the gated daemon considers the
	  update to be in error	and ignores it.

	Signals
	  The gated server performs the	following actions when you use
	  the kill(1) command to send it the SIGHUP and	SIGINT sig-
	  nals.

	  SIGHUP
	       When a SIGHUP signal is sent to a gated daemon that was
	       invoked with trace flags	and a log file,	tracing	is
	       toggled off and the log file is closed. At this point
	       the log file can	be moved or deleted. When the next
	       SIGHUP signal is	sent to	the gated daemon, tracing is
	       toggled on. The gated daemon reads the /etc/gated.conf
	       configuration file and sets the trace flags to those
	       specified by the	traceflags stanza.
	       If no traceflags	stanza exists, tracing resumes and
	       uses any	trace flags specified on the command line.
	       Trace output is sent to the log file specified on the
	       command line. The output	is appended if the log file
	       already exists, and the file is created if it does not
	       exist.

	  SIGINT
	       Sending the gated daemon	a SIGINT signal	causes a
	       memory dump to be scheduled within the next 60 seconds.
	       The memory dump is written to a file named
	       /usr/temp/gated_dump. The gated daemon processes	all
	       pending routing updates before performing the memory
	       dump.

	  The memory dump contains a snapshot of the current gated
	  daemon status, including the interface configurations, EGP
	  neighbor status, and the routing tables. If the
	  /usr/tmp/gated_dump file already exists, the memory dump is
	  appended to the existing file.

	Internal Metrics for the gated Daemon
	  The gated daemon stores all metrics internally as a time
	  delay	in milliseconds	to preserve the	granularity of HELLO
	  time delays. The internal delay ranges from 0	to 30,000 mil-
	  liseconds, with 30,000 representing infinity.	Metrics	from
	  other	protocols are translated to and	from a time delay as
	  they are received and	transmitted. EGP distances are not
	  comparable to	HELLO and RIP metrics but are stored as	time
	  delays internally for	comparison with	other EGP metrics. The
	  conversion factor between EGP	distances and time delays is
	  100.

	  RIP and interface metrics are	translated to and from the
	  internal time	delays with the	use of the following transla-
	  tion tables. The first two columns represent the time	delay
	  to RIP metric	translation, while the second two columns
	  represent the	RIP metric to time delay translation.

	       Time Delay
	    Minimum   Maximum	RIP Metric   RIP Metric	  Time Delay

		 0	   0	     0		  0		 0
		 1	 100	     1		  1	       100
	       101	 148	     2		  2	       148
	       149	 219	     3		  3	       219
	       220	 325	     4		  4	       325
	       326	 481	     5		  5	       481
	       482	 713	     6		  6	       713
	       714	1057	     7		  7	      1057
	      1058	1567	     8		  8	      1567
	      1568	2322	     9		  9	      2322
	      2323	3440	    10		 10	      3440
	      3441	5097	    11		 11	      5097
	      5098	7552	    12		 12	      7552
	      7553    11,190	    13		 13	    11,190
	    11,191    16,579	    14		 14	    16,579
	    16,580    24,564	    15		 15	    24,564
	    24,565    30,000	    16		 16	    30,000

     CAUTIONS
	  Unpredictable	results	may occur when the gated and routed
	  daemons are run together on the same host.

     FILES
	  /usr/sbin/gated
	       Specifies the command path

	  /etc/gated.conf
	       Contains	the gated configuration	information

	  /etc/gated.pid
	       Contains	the gated process ID

	  /usr/tmp/gated_dump
	       Specifies the memory dump file

     RELATED INFORMATION
	  Commands: kill, routed(8)




Acknowledgement and Disclaimer