From: hong tony (aamercado31@xxxxxxxxx)
Date: Thu May 16 2002 - 18:01:06 GMT-3
HI
passive interface stops the router from sending
updates to a particular neighbor, but continues to
listen and use routing updates from that neighbor.
This implies that lo0, e0, s0, and s1 is passive but
E1 is active, rip updates will continue via e1
regarding the 170 network only given the nature of rip
(see below):
http://www.cisco.com/warp/customer/105/54.html
BTW, you dont need to passive s1 or e0 which is
explained on link above
hth
--- Ludwig Morales <lud.morales@codetel.net.do> wrote:
> Pie ChartsHi everybody!!
>
> Is there any obscure rule about passive interfaces
> en RIP that allows the
> rip proccess to keep advertising my loopback address
> even when made passive
> or is there other way to do this (this is fat kids
> lab 401).
> I've rebooted, reloaded, prayed and done all kinds
> of things.
> Help me out here pleaseeeee!!!
>
> version 12.1
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname R4
> !
> ip subnet-zero
> no ip domain-lookup
> !
> !
> !
> !
> !
> !
> interface Loopback4
> ip address 170.10.5.4 255.255.255.0
> !
> interface Ethernet0
> ip address 170.10.128.4 255.255.255.192
> ip ospf priority 0
> !
> interface Ethernet1
> ip address 170.10.3.4 255.255.255.0
> !
> interface Serial0
> no ip address
> shutdown
> !
> interface Serial1
> ip address 192.19.15.2 255.255.255.0
> !
> router ospf 100
> router-id 4.4.4.4
> log-adjacency-changes
> area 2 virtual-link 5.5.5.5
> network 170.10.5.0 0.0.0.255 area 3
> network 170.10.128.0 0.0.0.255 area 2
> !
> router rip
> passive-interface Ethernet0
> passive-interface Loopback4
> passive-interface Serial0
> passive-interface Serial1
> network 170.10.0.0
> !
> ip classless
> ip http server
> !
> !
> !
> line con 0
> line aux 0
> line vty 0 4
> !
> end
>
> R4#
> 01:46:50: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:46:50: RIP: build update entries
> 01:46:50: subnet 170.10.5.0 metric 1
> 01:47:19: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:47:19: RIP: build update entries
> 01:47:19: subnet 170.10.5.0 metric 1
> 01:47:48: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:47:48: RIP: build update entries
> 01:47:48: subnet 170.10.5.0 metric 1
> 01:48:15: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:48:15: RIP: build update entries
> 01:48:15: subnet 170.10.5.0 metric 1
> 01:48:43: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:48:43: RIP: build update entries
> 01:48:43: subnet 170.10.5.0 metric 1
> 01:49:11: RIP: sending v1 update to 255.255.255.255
> via Ethernet1
> (170.10.3.4)
> 01:49:11: RIP: build update entries
> 01:49:11: subnet 170.10.5.0 metric 1
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:58 GMT-3