Link 2 R3 21.1.1.20/30 22 SO/O R1.21 S0/2 R4 SO/1 SO/1 26 .29 .30 Link 1 21.1.1.28/30 .25 Link 3 21.1.1.24/30 8. Routers R1, R2, R3 and R4 are running RIPv2 with split horizon enabled and auto- summary disabled (no auto-summary) R1 has serial links to R2, R3 and R4 as shown. R2, R3 and R4 have links to other routers that are not shown. Router R1 has just powered up and its routing table is empty. R1 has just received the following RIPv2 packets from R2, R3 and R4. Note that these are all Cisco routers, so each of these routers incremented the hop counts before they sent these RIPv2 packets to R!l RIPv2 Packet from R2 RIPv2 Packet from R3 RIPv2 Packet from R4 Subnet 62.18.50.0/23 2 144.5.9.0/25 151.9.0.0/16 201.18.0.0/16 6 Subnet 62.18.50.0/23 5 88.0.0.0/8 144.5.9.0/25 3 151.9.0.0/16 5 Hops Hops Subnet Hops 62.18.50.0/23 1 88.0.0.0/8 144.5.9.0/256 201.18.0.0/16 8 (15 points) Show the contents of the R1 routing table, for each of the columns below, after it has processed these three RIPv2 packets. Be sure to include the directly connected Link 1, Link 2, and Link 3 subnets as well as the remote subnets learned through RIP. The "Code" values will either be C' or 'R'. The "Next Hop IP" values must be IP addresses a. Router R1 Routing Table Subnet Mask Outgoing Interface Next Hop IP Destination Metric (Hops) Code Subnet b. (10 points) After these changes to its routing table, Router R1 now sends a new RIPv2 message out interface SO/1 to Router R2. Show the contents of this message RIPv2 from R1 to R2 Subnet Hops c. (not required up to 3 points extra credit) Show what the contents of the RIPv2 message from R3 to R1 would have been if auto-summary were enabled