|
最早不使用passive-interface 的 r1 show run
r1#show run Building configuration...
Current configuration : 971 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname r1 ! boot-start-marker boot-end-marker ! enable secret 5 $1$77i9$FcYUjXWx7jM2/Boj6DVJg/ ! no aaa new-model ip subnet-zero ! ! no ip domain lookup ip host r2 172.16.1.2 ! ip cef ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0 description link to r2 f 0/0 ip address 172.16.1.1 255.255.255.0 duplex half ! interface Ethernet1/0 description link to sw ip address 172.16.2.1 255.255.255.0 duplex half ! interface Ethernet1/1 description link to sw ip address 192.168.3.1 255.255.255.0 duplex half ! interface Ethernet1/2 no ip address shutdown duplex half ! interface Ethernet1/3 no ip address shutdown duplex half ! router rip network 172.16.0.0 // 因为 rip 宣告的是主网段.所以连接交换的端口也被加入到rip 宣告中去了.这样就使的在一个没有路由信息的线路上定期的发送路由信息.浪费带宽也不安全. ip classless no ip http server ! ! ! ! ! ! ! ! ! gatekeeper shutdown ! banner motd ^CWelcome to r1^C ! line con 0 stopbits 1 line aux 0 line vty 0 4 no login ! ! end
r1#
r1# *Jan 24 13:01:16.995: RIP: sending v1 update to 255.255.255.255 via Ethernet1/0 (172.16.2.1) *Jan 24 13:01:16.995: RIP: build update entries *Jan 24 13:01:16.999: subnet 172.16.1.0 metric 1 *Jan 24 13:01:16.999: subnet 172.16.4.0 metric 2 *Jan 24 13:01:16.999: subnet 172.16.5.0 metric 2 *Jan 24 13:01:19.251: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (172.16.1.1) *Jan 24 13:01:19.251: RIP: build update entries *Jan 24 13:01:19.255: subnet 172.16.2.0 metric 1 *Jan 24 13:01:22.079: RIP: received v1 update from 172.16.1.2 on FastEthernet0/0 *Jan 24 13:01:22.083: 172.16.4.0 in 1 hops *Jan 24 13:01:22.083: 172.16.5.0 in 1 hops *Jan 24 13:01:43.447: RIP: sending v1 update to 255.255.255.255 via Ethernet1/0 (172.16.2.1) *Jan 24 13:01:43.447: RIP: build update entries *Jan 24 13:01:43.451: subnet 172.16.1.0 metric 1 *Jan 24 13:01:43.451: subnet 172.16.4.0 metric 2 *Jan 24 13:01:43.451: subnet 172.16.5.0 metric 2 *Jan 24 13:01:44.303: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on Ethernet1/0 (not full duplex), with Router FastEthernet0/0 (full duplex). *Jan 24 13:01:45.815: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (172.16.1.1) *Jan 24 13:01:45.815: RIP: build update entries *Jan 24 13:01:45.819: subnet 172.16.2.0 metric 1
debug rip 可以看出正在向 e 1/0 这个末梢网络发送路由信息
r1#show run Building configuration...
Current configuration : 1033 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname r1 ! boot-start-marker boot-end-marker ! enable secret 5 $1$77i9$FcYUjXWx7jM2/Boj6DVJg/ ! no aaa new-model ip subnet-zero ! ! no ip domain lookup ip host r2 172.16.1.2 ! ip cef ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! interface FastEthernet0/0 description link to r2 f 0/0 ip address 172.16.1.1 255.255.255.0 duplex half ! interface Ethernet1/0 description link to sw ip address 172.16.2.1 255.255.255.0 duplex half ! interface Ethernet1/1 description link to sw ip address 192.168.3.1 255.255.255.0 duplex half ! interface Ethernet1/2 no ip address shutdown duplex half ! interface Ethernet1/3 no ip address shutdown duplex half ! router rip passive-interface Ethernet1/0 //关闭这两个端口的路由信息发送 passive-interface Ethernet1/1 network 172.16.0.0 ! ip classless no ip http server ! ! ! ! ! ! ! ! ! gatekeeper shutdown ! banner motd ^CWelcome to r1^C ! line con 0 stopbits 1 line aux 0 line vty 0 4 no login ! ! end
再 debug rip
*Jan 24 13:03:47.351: RIP: received v1 update from 172.16.1.2 on FastEthernet0/0 *Jan 24 13:03:47.355: 172.16.4.0 in 1 hops *Jan 24 13:03:47.355: 172.16.5.0 in 1 hops *Jan 24 13:04:05.379: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (172.16.1.1) *Jan 24 13:04:05.379: RIP: build update entries *Jan 24 13:04:05.383: subnet 172.16.2.0 metric 1 *Jan 24 13:04:12.863: RIP: received v1 update from 172.16.1.2 on FastEthernet0/0 *Jan 24 13:04:12.867: 172.16.4.0 in 1 hops *Jan 24 13:04:12.867: 172.16.5.0 in 1 hops
这里debug 太短了.呵呵.不过效果是可以看出来的.30秒的广播中并没有包含 E 口.
本文出自 51CTO.COM技术博客 |