gated.conf.4 (2010 09)

g
gated.conf(4) gated.conf(4)
[ metric metric ] {
export_list ;
};
It is not possible to create OSPF intra- or inter-area routes by exporting routes from the GateD routing
table into OSPF. It is only possible to export from the GateD routing table into OSPF ASE routes. It is
also not possible to control the propagation of OSPF routes within the OSPF protocol.
There are two types of OSPF ASE routes, type 1 and type 2, see the OSPF protocol configuration for a
detailed explanation of the two types. The default type is specified by the defaults subclause of the
ospf clause. This may be overridden by a specification on the export statement.
OSPF ASE routes also have the provision to carry a tag. This is an arbitrary 32 bit number that can be
used on OSPF routers to filter routing information. See the OSPF protocol configuration for detailed infor-
mation on OSPF tags. The default tag specified by the ospf defaults clause may be overridden by a
tag specified on the export statement.
Specifying the source
The export list specifies export based on the origin of a route and the syntax varies depending on the
source.
Exporting BGP and EGP routes
proto bgp | egp autonomoussystem autonomous_system
restrict ;
proto bgp | egp autonomoussystem autonomous_system
[ metric metric ] {
route_filter [ restrict |(metric metric )];
};
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 nonrouting protocols
Nonrouting 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:
HP-UX 11i Version 3: September 2010 − 47 − Hewlett-Packard Company 47