work in its routing table because it's been ad- vertised across the network by RIP: R3#sho ip route [text removed] Gateway of last resort is not set 192.192.192.0/3 is subnetted, 1 subnets 192.192.192.4 is directly connected, Serialo/o 50.0.0.0/24 is subnetted, 1 subnets 50.50.50.0 [120/2] via 10.20.20.1, 00:00:05, Ethernet1/0 10.0.0.0/24 is subnetted, 2 subnets 10.10.10.0 [120/1] via 10.20.20.1, 00:00:24, Ethernet1/0 10.20.20.0 is directly connected, Ethernet1/0 192.168.1.0/29 is subnetted, 1 subnets 192.168.1.0 [120/2] via 10.20.20.1, 00:00:24, Ethernet1/0 Redistributing into EIGRP EIGRP was designed to automatically redistribute IGRP routes from the same ASN. You can disable this behavior with the no redistribute igrp autonomous-system command: router eigrp 100 no redistribute igrp 100 You redistribute routes into EIGRP in the same way as you do with RIP. It only looks harder because the metric in EIGRP is more complicated than that in RIP; whereas RIP only uses hop count as a metric, EIGRP uses the combined bandwidth and delay values from all the links in the path. In fact, EIGRP uses more than just these two measure- ments, but, by default, the other metrics are disabled. However, with redistribution, you must specify them, SO let's take a look at what they should be. As with RIP, you can use the default-metric command to specify the metric of redis- tributed routes, or you can specify the metric on each redistribute command line. Chapter 11: Redistribution Here are the arguments required for the default-metric command in EIGRP, and the allowed ranges of values: Bandwidth in Kbps: 1-4,294,967,295 Delay in 10-microsecond units: 0-4,294,967,295 Reliability metric, where 255 is 100 percent reliable: 0-255 Effective bandwidth metric (loading), where 255 is 100 percent loaded: 1-255 Maximum Transmission Unit (MTU) metric of the path: 1-4,294,967,295 How you configure these values will depend largely on your needs at the time. Re- member that redistributed routes are external routes, SO they will always have a hig