k. Still, R3 needs to be able to get to the network. To add 50.50.50.0/24 to the advertisements sent out by R1, we must redistribute connected networks into RIP using the redistribute connected command on R1: router rip version 2 redisribute connected metric 1 network 10.0.0.0 no auto-summary Chapter 11: Redistribution While sending useless broadcasts may seem trivial, remember that RIP sends broadcasts that include the entire routing table. Only 25 desti- nations can be included in a single RIP update packet. On a network with 200 routes, each update will be composed of eight large broad- cast packets, each of which will need to be processed by every device on the network. That's potentially 12k of data every 30 seconds. If that's not enough proof for you, consider this: RIP updates are clas- sified as control packets (IP precedence 6 or DSCP 48). That means that they have a higher precedence than voice RTP packets, which are classified as express forwarding packets (IP precedence 5 or DSCP 40). To put it simply, RIP updates can easily affect voice quality on VOIP- enabled networks. Now R3 can see the 50.50.50.0/24 network in its routing table because it's been advertised across the network by RIP: R3# sho ip route [text removed] Gateway of last resort is not set 192.192.192.0/30 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. This behavior can be disabled with the no redistribute igrp autonomous-system command: router eigrp 100 no redistribute igrp 100 Redistributing routes into EIGRP is done the same way as it is with RIP. It only looks harder because the metri