RIP实验学习(二)
实验环境同 RIP实验学习(一)
实验目标一:R4上起6个loopback接口,地址分别为 10.101.1.1 ;10.101.2.1;。。。;10.101.6.1,精确汇总为一条路由发给所有rip邻居。
R4(config)#int loopback 1
R4(config-if)#ip summary-address rip  10.101.0.0 ?
 A.B.C.D  IP network mask
R4(config-if)#ip summary-address rip  10.101.0.0 255.255.248.0 ?
 <cr>
R4(config-if)#ip summary-address rip  10.101.0.0 255.255.248.0
R4(config)#int loopback 2
R4(config-if)#ip summary-address rip 10.101.0.0 255.255.248.0
R4(config-if)#exit
R4(config)#int loopback 3
R4(config-if)#ip summary-address rip 10.101.0.0 255.255.248.0
R4(config-if)#exit
R4(config)#int loopback 4
R4(config-if)#ip summary-address rip 10.101.0.0 255.255.248.0
R4(config-if)#exit
R4(config)#int loopback 5
R4(config-if)#ip summary-address rip 10.101.0.0 255.255.248.0
R4(config-if)#exit
R4(config)#int loopback 6
R4(config-if)#ip summary-address rip 10.101.0.0 255.255.248.0
R4(config-if)#end
以下是debug ip rip信息

*Mar 23 07:52:11.339: RIP: sending v2 update to 224.0.0.9 via Loopback1 (10.101.1.1)
*Mar 23 07:52:11.339: RIP: build update entries
*Mar 23 07:52:11.339:   1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:11.339:   2.2.2.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:11.343:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:11.343:   4.4.4.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:11.343:   10.101.0.0/21 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:11.343:   128.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:11.347:   128.1.2.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 23 07:52:11.347: RIP: ignored v2 packet from 10.101.1.1 (sourced from one of our addresses)
R4#
*Mar 23 07:52:12.947: RIP: sending v2 update to 224.0.0.9 via Loopback3 (10.101.3.1)
*Mar 23 07:52:12.947: RIP: build update entries
*Mar 23 07:52:12.947:   1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.947:   2.2.2.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.947:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.951:   4.4.4.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.951:   10.101.0.0/21 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.951:   128.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.951:   128.1.2.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 23 07:52:12.955: RIP: ignored v2 packet from 10.101.3.1 (sourced from one of our addresses)
R4#
*Mar 23 07:52:12.959: RIP: sending v2 update to 224.0.0.9 via Loopback4 (10.101.4.1)
*Mar 23 07:52:12.959: RIP: build update entries
*Mar 23 07:52:12.959:   1.1.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.959:   2.2.2.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.959:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.963:   4.4.4.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.963:   10.101.0.0/21 via 0.0.0.0, metric 1, tag 0
*Mar 23 07:52:12.963:   128.1.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar 23 07:52:12.963:   128.1.2.0/24 via 0.0.0.0, metric 3, tag 0
*Mar 23 07:52:12.963: RIP: ignored v2 packet from 10.101.4.1 (sourced from one of our addresses)
R4#
实验目标二:R3R和R4之间要求广播更新,且不得更改RIP版本
R3 s1/1 接口和R4 s1/0接口相连

R3(config)#int s1/1
R3(config-if)#ip rip send version 1
R3(config-if)#ip rip receive version  1 2
R3(config-if)#end

R4(config)#int s1/1
R4(config-if)#ip rip send version 1
R4(config-if)#ip rip receive version  1 2
R4(config-if)#end
debug ip rip 信息

*Mar 23 21:09:00.647: RIP: sending v1 update to 255.255.255.255 via Serial1/1 (4.4.4.1)  //发送RIP 1,广播类型
*Mar 23 21:09:00.647: RIP: build update entries
*Mar 23 21:09:00.647:   network 1.0.0.0 metric 2
*Mar 23 21:09:00.647:   network 2.0.0.0 metric 2
*Mar 23 21:09:00.647:   network 3.0.0.0 metric 1
*Mar 23 21:09:00.651:   subnet 4.4.4.0 metric 1
*Mar 23 21:09:00.651:   network 10.0.0.0 metric 2
*Mar 23 21:09:00.651:   network 128.1.0.0 metric 2
R3#
*Mar 23 21:09:03.675: RIP: received v1 update from 4.4.4.2 on Serial1/1  
*Mar 23 21:09:03.675:      1.0.0.0 in 1 hops
*Mar 23 21:09:03.679:      2.0.0.0 in 2 hops
*Mar 23 21:09:03.679:      3.0.0.0 in 2 hops
*Mar 23 21:09:03.679:      4.4.4.0 in 1 hops
*Mar 23 21:09:03.679:      10.0.0.0 in 1 hops
*Mar 23 21:09:03.679:      128.1.0.0 in 2 hops
R3#
*Mar 23 21:09:09.499: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (3.3.3.2)
*Mar 23 21:09:09.499: RIP: build update entries
*Mar 23 21:09:09.499:   1.0.0.0/8 via 0.0.0.0, metric 2, tag 0
*Mar 23 21:09:09.499:   1.1.1.0/24 via 3.3.3.1, metric 3, tag 0
*Mar 23 21:09:09.503:   2.0.0.0/8 via 0.0.0.0, metric 3, tag 0
*Mar 23 21:09:09.503:   2.2.2.0/24 via 3.3.3.1, metric 2, tag 0
*Mar 23 21:09:09.503:   3.0.0.0/8 via 3.3.3.1, metric 5, tag 0
*Mar 23 21:09:09.503:   3.3.3.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 21:09:09.503:   4.4.4.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 23 21:09:09.507:   10.0.0.0/8 via 0.0.0.0, metric 2, tag 0
R3#u a
*Mar 23 21:09:09.507:   10.101.1.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.507:   10.101.2.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.507:   10.101.3.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.511:   10.101.4.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.511:   10.101.5.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.511:   10.101.6.0/24 via 3.3.3.1, metric 4, tag 0
*Mar 23 21:09:09.511:   128.1.0.0/16 via 0.0.0.0, metric 3, tag 0
*Mar 23 21:09:09.511:   128.1.1.0/24 via 3.3.3.1, metric 3, tag 0
*Mar 23 21:09:09.515:   128.1.2.0/24 via 3.3.3.1, metric 2, tag 0
R3#u all
All possible debugging has been turned off
R3#

*Mar 23 21:08:30.379: RIP: received v1 update from 4.4.4.1 on Serial1/0
R4#
*Mar 23 21:08:30.379:      1.0.0.0 in 2 hops
*Mar 23 21:08:30.379:      2.0.0.0 in 2 hops
*Mar 23 21:08:30.383:      3.0.0.0 in 1 hops
*Mar 23 21:08:30.383:      4.4.4.0 in 1 hops
*Mar 23 21:08:30.383:      10.0.0.0 in 2 hops
*Mar 23 21:08:30.383:      128.1.0.0 in 2 hops
R4#
*Mar 23 21:08:33.955: RIP: sending v1 update to 255.255.255.255 via Serial1/0 (4.4.4.2)
*Mar 23 21:08:33.955: RIP: build update entries
*Mar 23 21:08:33.955:   network 1.0.0.0 metric 1
*Mar 23 21:08:33.955:   network 2.0.0.0 metric 2
*Mar 23 21:08:33.955:   network 3.0.0.0 metric 2
*Mar 23 21:08:33.959:   subnet 4.4.4.0 metric 1
*Mar 23 21:08:33.959:   network 10.0.0.0 metric 1
*Mar 23 21:08:33.959:   network 128.1.0.0 metric 2

实验目标三:为了全网安全,要求全网采用MD5认证,R3和R4之间使用了广播更新,不能使用验证
R1#conf t
R1(config)#key chain first-chain
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string cisco123
R1(config-keychain-key)#exit
R1(config-keychain)#exit
R1(config)#int s1/0
R1(config-if)#ip rip authentication mode md5
R1(config-if)#ip rip authentication key-chain first-chain
R1(config)#int s1/1
R1(config-if)#ip rip authentication mode md5
R1(config-if)#ip rip authentication key-chain first-chain
其他路由器以此类推,即可。