使用RIP协议处理不连续的子网和VLSM(二)
Term_Server> 1
[Resuming connection 1 to R1 ... ]
R1#conft
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router rip
R1(config-router)#ver 2
R1 (config-router)#no auto-summary
R1(config-rotuer)#end
R1#
R1#sh ip prot
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 5 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoingupdatefilter list for all interfaces is
Incomingupdatefilter list for all interfaces is
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triigered RIP Key-chain
Ethemet0 2 2
Serial0 2 2
Serial1 2 2
Automatic network summarization is not in effect
Routing for Networks:
172.16.0.0
172.18.0.0
Routing Information Sources:
Gateway DistanceLast Update
172.16.123.6 120 00:00:06
172.16.123.2 120 00:00:04
Distance: (default is 120)
R1#sh ip route rip
172.16.0.0/30 is subnetted, 3 subnets
R 172.16.123.8 [120/1] via 172.16.123.2, 00:00:06, Serial0
[120/1] via 172.16.123.6, 00:00:22, Serial1
172.18.0.0/16 is variably subnetted, 3 subnets, 2 masks
R 172.18,2,0/28 [120/1] via 172.16.123.2,00:00:06,SerialO
R 172.18J.O/24 [120/1] via 172.16.123.6, 00:00:22, Serial1
第3段：配置 passive interface
R1#debug ip rip
RIP protocol debugging is on
R1#
02:59:47: RIP: received v2updatefrom 172.16.123.6 on Serial1
02:59:47: 172.16.123.8/30 via 0.0.0.0 in 1 hops
02:59:47: 172.18.2.0/28 via 0.0.0.0 in 1 hops
02:59:47: 172.18.3.0/24 via 0.0.0.0 in 1 hops
R1#
02:59:51: RIP: sending v2updateto 224.0.0.9 via Ethernet 0(172.18.1.1)
02:59:51: RIP: buildupdateentries
02:59:51: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.16.123.4/30 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.16.123.8/30 via 0.0.0,0, metric 2, tag 0
02:59:51: 172.18.2.0/28 via 0.0.0.0, metric 2,tab 0
02:59:51: 172.183.0/24 via0.0.0.0,metric 2,tag 0
02:59:51: RIP: sendiag v2updateto 224.0.:0.9viaSaialC-172.15.t23.1)
02:59:51: RIP: buildupdateentries
02:59:51: 172.16.123.4/30 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.18.1.0/28 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.18.3.0/24 via 0.0.0.0, metric 2, tag 0
R1#
02:59:51: RIP: sending v2updateto 224.0.0.9 via Serial1(172.16.123.5)
02:59:51: RIP: buildupdateentries
02:59:51: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.18.1.0/28 via 0.0.0.0, metric 1, tag 0
02:59:51: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0
R1#u all
All possible debugging has been turned off
R1#conft
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router rip
R1(config-router)passive-interface ?
Ethernet IEEE 802.3
Null Null interface
SerialSerial
defaultSuppres s routing updates. on all interfaces
R1 (config-router)passive-interface e0
R1(config-router)#passive-interface s0
R1(config-router#^Z
R1#debugiprip
RIP protocol debugging is on
R1#
03:00:54: RIP: received v2updatefrom 172.16.123.2 on Serial0
03:00:54: 172.16.123.8/30 via 0.0.0.0 in 1 hops
03:00:54: 172.18.2.0/28 via 0.0.0.0 in 1 hops
03:00:54: 172.18.3.0/24 via 0.0.0.0 in 2 hops
R1#
3:00:56:RIP:sending v2 flashupdateto 224.0.0.9 via Serial1(172.16.123.5)
03:00:56: RIP: build flashupdateentries
03:00:56: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0
R1#
03:01:12:RIP:received v2updatefrom 172.16.123.6 on Serial1
03:01:12: 172.16.123.8/30 via0.0.0.0 in 1 hops
03:01:12: 172.18.2.0/28 via 0.0.0.0 in 2 hops
03:01:12: 172.18.3.0/24 via 0.0.0.0 in 1 hops
R1#
03:01:17:RIP:sending v2 flashupdateto 224.0.0.9 via Serial1(172.16.123.5)
03:01:17: RIP: buildupdateentries
03:01:17: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0
03:01:17: 172.18.1.0/28 via 0.0.0.0,. metric 1,tag 0
03:01:17: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0
R1#
03:01:23:RIP:received v2updatefrom 172.16.123.2 on Serial1
03:01:23: 172.16.123.8/30 via 0.0.0.0 in 1 hops
03:01:23: 172.18.2.0/28 via 0.0.0.0 in 1 hops
03:01:23: 172.18.3.0/24 via 0.0.0.0 in 2 hops
R1#conft
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router rip
R1 (config-router)#passive-mterface default
R1(config-router#^Z
R1#
Term_Server>2
[Resuming connection 2 to R2 ... ]
R2#cle ip route *
R2#
Term_Server>3
[Resuming connection 3 to R3 ... ]
R3#cle ip route *
R3#
Term_Server>1
[Resuming connection 1 to R1... ]
R1#sh ip route rip
172.16.0.0/30 is subnetted,3 subnets
R 172.16.123.8[120/1]via 172.16.123.2,00:00:09,Serial1
[120/1]via 172.16.123.6,00:00:17,Serial0
172.18.0.0/16 is variably subnetted,3 subnets,2 masks
R 172.18.2.0/28[120/1] via 172.16.123.2,00:00:17,Serial0
R 172.18.3.0/24[120/1] via 172.16.123.6,00:00:09,Serial1
R1#
Term_Server>2
[Resuming connection 2 to R2...]
R2#
R2#sh ip route rip
172.16.0.0/30 is subnetted,3 subnets
R 172.16.123.4[120/1]via 172.16.123.10,00:00:24,Serial1
172.18.0.0/16 is variably subnetted,2 subnets,2 masks
R 172.18.3.0/24[120/1] via 172.16.123.10,00:00:24,Serial1
R2#
Term_Server>3
[Resuming connection 3 to R3...]
R3#sh ip route rip
172.16.0.0/30 is subnetted,3 subnets
R 172.16.123.0120/1] via 172.16.123.9,00:00:26,Serial1
172.18.0.0/16 is variably subnetted,2 subnets,2 masks
R 172.18.2.0/28[120/1] via 172.16.123.9,00:00:26,Serial1