way of propagating those routes throughout the network. Connected routes Routes that are in the routing table as a result of a directly connected interface on the router doing the redistribution can also be redistributed into routing pro- tocols. When redistributing a connected route, the network in question will be inserted into the routing protocol, but the interfaces configured within that net- work will not advertise or listen for route advertisements. This can be used as an alternative to the network command when such behavior is desired. Other routing protocols Routes can be learned dynamically from other routing protocols that are active on the router doing the redistribution. Routes from any routing protocol can be redistributed into any other routing protocol. An example of redistributing between routing protocols would be OSPF redistributing into EIGRP. Redistribution The same routing protocol from a different autonomous system or process Protocols that support autonomous systems, such as EIGRP, OSPF, and BGP, can redistribute between these systems. An example of a single protocol redis- tributing between autonomous systems would be EIGRP 100 redistributing into EIGRP 200. Regardless of what protocol you redistribute into, you can still only do it from one of the sources just listed. When redistributing routes, the command redistribute- followed by the route source-is used within the protocol receiving the route. Redistribution is configured on the protocol for which the routes are destined, not the one from which they are sourced. No configuration needs to be done on the protocol providing the routes. Redistributing into RIP We'll start with RIP, because it has the simplest metric, and therefore the simplest configuration. A common problem when configuring routing protocols is the inclusion of static routes. Because the routes are static, they are, by definition, not dynamic. But if they're statically defined, why include them in a dynamic routing protocol at all? Figure 11-2 shows a simple network whe