The GateD makefile system is set up to allow object directories for multiple architectures to use one source tree. The object directories consist of a few configured files and symlinks for the majority of the GateD files. They are named obj.<arch> where arch is the architecture of your system as reported by the arch or machine program. If one of these programs can not be found, the first part of your hostname is used. See src/util/archtype for more information.
GateD-Multicast (version 5.0) and Gated-Unicast (4.2) now uses GNU autoconf to detect platform-specific configuration options. You do not need to install autoconf to build gated. By default, gated is compiled with all protocols available. Should you wish to disable support for some protocols, this can be done through an "options" file. Normally, protocols will only be turned on/off via the gated.conf run-time configuration file.
GateD-Multicast (version 5.0) and GateD-Unicast (version 4.2) both originate from a "new" gated-multi library which uses the GNU autoconf. The gated (version 3.5 or public) code and the GateD-Unicast (version 4.0) code do not support the GNU autoconf usage. Instead these libraries use the Manual configuration methods based on gated "Config" files to determine platform-specific configuration options.
Manual configuration of GateD is the use of Configuration files to set platform-specific configuration options. Merit and the GateD Community have prepared a number of configuration files to set these platform-specific configuration options for various hardware and software architectures. Section 5.2.x provides a link to the list of existing GateD build configuration files for each of the following releases:
After you have "untared" the gated.tar file, you follow the simple steps below to get your gated built and installed. The Merit GateD Consortium does not release binaries, but your host vendor or routing system vendor may release binaries for the hardware and software platforms.
Please read all of section 5.2 prior to attempting any manual configuration builds for gated (version 3.5) or gated-unicast (version 4.0). If you have problems, you can contact either the gated mailing list gated-people@merit.edu or the merit help list gated@gated.merit.edu.
Below is quick form of each of these steps. Please click on each step to receive additional information on the exact commands you need to perform each step.
(In /gated/src directory)
(For example, find merit.SunOS-5.5.1
cp /configs/merit.SunOS-5.5.1 obj.`/util/archtype`
(In /gated/src directory)
make config
(In /gated/src directory)
This section goes into a detailed description of the Manual Configuration file format, and provides examples for common operating systems.
(need text from Sue)
This sections will cover:
The GateD Routing deamon relies on services of the unix kernel for the TCP/IP stack such as:
(Sue add text here to glue paragraphs together.)
GateD runs on large number of platforms using the system functions specified above. In order to select the correct set of system functions, GateD uses types of configuration:
Section 5.4 provides notes on how to configure unix system functions needed on various systems. The unix system configurations described are:
3) Interfacing
to the SNMP SMUX interface in GateD (5.4.3)
(Ask sue to fill in list.)
5.)
Compiling GateD on systems with shared libraries (5.4.5)
(need text)
yacc problems have been reported with AIX 3.1/3.1. The solution is to use GNU libraires. For more details, refer to section 5.3.7. (Sue - there is no section 5.3.7 ?????)
7.) Running
HELLO and/or EGP on 4.2 based systems (5.4.7)
Last updated November 28, 1997
gated@gated.merit.edu