Technical data

Gateway Routing Daemon (GATED) Configuration Reference
A.18 Control Statements
Exporting to RIP
export proto rip
[ ( interface interface_list ) | (gateway gateway_list )]
restrict ;
export proto rip
[ ( interface interface_list ) | (gateway gateway_list )]
[ metric metric ]{
export_list ;
};
Exportation to RIP is controlled by any of protocol, interface or gateway. If more
than one is specified, they are processed from most general (protocol) to most
specific (gateway).
It is not possible to set metrics for exporting RIP routes into RIP. Attempts to do
this are silently ignored.
If no export policy is specified, RIP and interface routes are exported into RIP.
If any policy is specified, the defaults are overridden; it is necessary to explicitly
specify everything that should be exported in the export_list .
When exporting routes from other protocols, it is important to specify a metric
on the
export statement or in the route filters. Unless this is done, the value
specified in defaultmetric is used. If not specified, the defaultmetric value is
16 (unreachable). It is likely that this is not the desired result.
RIP version 1 assumes that all subnets of the shared network have the same
subnet mask so they are only able to propagate subnets of that network. RIP
version 2 removes that restriction and is capable of propagating all routes when
not sending version 1 compatible updates.
To announce routes which specify a next hop of the loopback interface (that is,
static and internally generated default routes) via RIP, it is necessary to specify
the metric at some level in the export clause. Just setting a default metric for
RIP is not sufficient. This is a safeguard to verify that the announcement is
intended.
Exporting to OSPF
export proto osfpase [ type 1 | 2 ] [ tag ospf_tag ]
restrict ;
export proto osfpase [ type 1 | 2 ] [ tag ospf_tag ]
[ metric metric ] {
export_list ;
};
It is not possible to create OSPF intra- or interarea 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. 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. The
default tag specified by the OSPF defaults clause may be overridden by a tag
specified on the export statement.
Gateway Routing Daemon (GATED) Configuration Reference A–39