gated.conf.4 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

gated.conf(4) gated.conf(4)

multicast

Speciﬁes 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 avail-

able for referring to interfaces. They are listed here from most general to most speciﬁc.

all This refers to all available interfaces.

Interface name wildcard

This refers to all the interfaces of the same type. Unix interfaces consist of the name of the

device driver, like ie, and a unit number, like 0, 5 or 22. Reference to the name contain only

alphabetic characters and match any interfaces that have the same alphabetic part.

For example, ie on a Sun would refer to all Interlan Ethernet interfaces, le would refer to all

Lance Ethernet interfaces. But ie would not match iel0.

Interface name

This refers to a speciﬁc interface, usually one physical interface. These are speciﬁed as an

alphabetic part followed by a numeric part. This will match one speciﬁc interface. But be

aware that on many systems, there can be more than one protocol (IP) address on a given phy-

sical interface. For example, ef1 will match an interface named ef1, but not an interface

named ef10.

Interface address

This matches one speciﬁc interface. The reference can be by protocol address (10.0.0.51), or by

symbolic hostname (nic.ddn.mil). Note that a symbolic hostname reference is only valid when

it resolves to only one address. Use of symbolic hostnames is not recommended.

If many interface lists are present in the conﬁguration ﬁle with more than one parameter, these parame-

ters are collected at run-time to create the speciﬁc parameter list for a given interface. If the same param-

eter is speciﬁed on more than one list, the parameters with the most speciﬁc interface is used.

For example, consider a system with three interfaces, le0, le1 and du0.

rip yes {

interface all noripin noripout ;

interface le ripin ;

interface le1 ripout ;

};

RIP packets would only be accepted from interfaces le0 and le1, but not from du0. RIP packets would

only be sent on interface le1.

IP Interface addresses and routes

The BSD 4.3 and later networking implementations allow four types of interfaces. Some implementations

allow multiple protocol addresses per physical interface, these are mostly based on BSD 4.3 Reno or later.

loopback

This interface must have the address of 127.0.0.1. Packets sent to this interface are sent back

to the originator. This interface is also used as a catch all interface for implementing other

features, such as reject and blackhole routes. Although a netmask is reported on this interface,

it is ignored. It is useful to assign an additional address to this interface that is the same as

the OSPF or BGP router id; this allows routing to a system based on the router id which will

work if some interfaces are down.

broadcast

This is a multiaccess interface capable of a physical level broadcast, such as Ethernet, Token

Ring and FDDI. This interface has an associated subnet mask and broadcast address. The

interface route to an broadcast network will be a route to the complete subnet.

point-to-point

This is a tunnel to another host, usually on some sort of serial link. This interface has a local

address, and a remote address. Although it may be possible to specify multiple addresses for a

point-to-point interface, there does not seem to be a useful reason for doing so.

The remote address must be unique among all the interface addresses on a given router. The

local address may be shared among many point-to-point and up to one non-point-to-point

interface. This is technically a form of the router id method for addressless links. This tech-

nique conserves subnets as none are required when using this technique.

HP-UX 11i Version 3: September 2010 − 9 − Hewlett-Packard Company 9