Technical data

Gateway Routing Daemon (GATED) Configuration Reference
A.18 Control Statements
A.18.5 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 as the source autonomous system. All
routes may be exported by AS path.
Exporting RIP Routes
proto rip
[ ( interface interface_list ) | (gateway gateway_list )]
restrict ;
proto rip
[ ( interface interface_list ) | (gateway gateway_list )]
[ metric metric ]{
route_filter [ restrict | ( metric metric )];
};
RIP routes may be exported by protocol, source interface, 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.
Exporting Routes from Nonrouting 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 command
and propagate them to other routing protocols.
A–40 Gateway Routing Daemon (GATED) Configuration Reference