HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
g
gated.conf(4) gated.conf(4)
};
BGP and EGP routes may be specified by source autonomous system. All routes may be exported by as
path, see below for more information.
Exporting RIP and HELLO routes
proto rip | hello
[(interface interface_list )|(gateway gateway_list )]
restrict ;
proto rip | hello
[(interface interface_list )|(gateway gateway_list )]
[ metric metric ] {
route_filter [ restrict |(metric metric )];
};
RIP and HELLO routes may be exported by protocol, source interface and/or source gateway.
Exporting OSPF routes
proto ospf | ospfase restrict ;
proto ospf | ospfase [ metric metric ] {
route_filter [ restrict |(metric metric )];
};
Both OSPF, and OSPF ASE routes may be exported into other protocols. See below for information on
exporting by tag.
Exporting routes from non-routing protocols
Non-routing with interface
proto direct | static | kernel
[(interface interface_list )]
restrict ;
proto direct | static | kernel
[(interface interface_list )]
[ metric metric ] {
route_filter [ restrict |(metric metric )];
};
These protocols may be exported by protocol, or by the interface of the next hop. These protocols are:
direct
Routes to directly attached interfaces.
static
Static routes specified in a static clause.
kernel
On systems with the routing socket, routes learned from the routing socket are installed in the
GateD routing table with a protocol of kernel. These routes may be exported by referencing this
protocol. This is useful when it is desirable to have a script install routes with the route com-
mand and propagate them to other routing protocols.
Non-routing by protocol
proto default | aggregate
restrict ;
proto default | aggregate
[ metric metric ] {
route_filter [ restrict |(metric metric )];
};
These protocols may only be referenced by protocol.
default
Refers to routes created by the gendefault option. It is recommended that route generation be
used instead.
aggregate
Refers to routes synthesized from other routes when the aggregate and generate statements
Section 4−−118 − 47 − HP-UX Release 11i: December 2000
___
___