HP-UX Reference (11i v1 05/09) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
non-broadcast multi-access or nbma
This type of interface is multi-access, but not capable of broadcast. And example would be frame
relay and X.25. This type of interface has a local address and a subnet mask.
GateD insures that there is a route available to each IP interface that is configured and up. Normally this
this done by the ifconfig command that configures the interface; GateD does it to insure consistency.
For point-to-point interfaces, gated installs some special routes. If the local address on one or more point-
to-point interfaces is not shared with a non-point-to-point interface, gated installs a route to the local
address pointing at the loopback interface with a preference of 110. This insures that packets originating on
this host destined for this local address are handled locally. OSPF prefers to route packets for the local
interface across the point-to-point link where they will be returned by the router on the remote end. This is
used to verify operation of the link. Since OSPF installs routes with a preference of 10, these routes will
override the route installed with a preference of 110.
If the local address of one or more point-to-point interfaces is shared with a non-point-to-point interface,
gated installs a route to the local with a preference of 0 that will not be installed in the forwarding table.
This is to prevent protocols like OSPF from routing packets to this address across a serial interface when
this system could be functioning as a host.
When the status of an interface changes, GateD notifies all the protocols, which take the appropriate
action. GateD assumes that interfaces which are not marked UP do not exist. While this might not be the
most correct action, it is the way things currently work.
GateD ignores any interfaces that have invalid data for the local, remote or broadcast addresses or the sub-
net mask. Invalid data includes zeros in any field. GateD will also ignore any point-to-point interface that
has the same local and remote addresses, it assumes it is in some sort of loopback test mode.
Definition Statements
Definition statements are general configuration statements that relate to all of GateD or at least to more
than one protocol. The three definition statements are autonomoussystem, routerid and martians.if
used, autonomoussystem, routerid and martians must appear before any other type of configuration
statement in gated.conf file.
Autonomous System configuration
autonomoussystem autonomous_system [ loops number ] ;
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).
Loops is only for protocols supporting AS paths, such as BGP. It controls the number of times this auto-
nomous system may appear in an AS path and defaults to 1 (one).
Router ID configuration
routerid host ;
Sets the router identifier for use by the BGP and OSPF protocols. 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.
Martian configuration
martians {
host host [ allow ] ;
network [ allow ] ;
network mask mask [ allow ] ;
network masklen number [ allow ] ;
default [ allow ] ;
};
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. See the section on Route Filtering for more information on specifying ranges. Also, the allow
parameter may be specified to explicitly allow a subset of a range that was disallowed.
HP-UX 11i Version 1: September 2005 − 10 − Hewlett-Packard Company Section 4−−79