RE: RIP Concept

From: Lora Ganeva (lganeva@mobiltel.bg)
Date: Sat Dec 15 2007 - 19:23:52 ART


Hi,

When the requirement says like this they expect from you to redistribute
connected network into RIP protocol:(
You can also put a distribute list to filter incoming updates.

Rgrds,
Lora

________________________________

From: nobody@groupstudy.com on behalf of subodh.rawat@wipro.com
Sent: Sat 12/15/2007 11:31 PM
To: mzsaeed@gmail.com; ccielab@groupstudy.com
Subject: RE: RIP Concept

Probaby you need to manually define neighbor with other segment(s).
Or you could block udp 520 traffic on e0/0.

HTH
Subodh

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Mohammad Saeed
Sent: Saturday, December 15, 2007 11:23 PM
To: Cisco certification
Subject: RIP Concept

Hello,

I have confusion. If I configure R1 with passive-interface default, RIP
updates will not be sent out the any interfaces. Now if eth0/0 has ip
192.168.1.1 and I issue network 192.168.1.0 statement, eth0/0 will start
receiving the RIP updates but will not send the RIP updates. But if
requirement says that R1 shall not peer with neighbor router on its
eth0/0, what does that mean? Does that mean that this router shall not
receive or send RIP Updates OR shall receive but shall not send updates?
Because as far as I know RIP really doesn't establish any formal
"PEERING" with its neighbors like EIGRP OR OSPF.....

Regards,

Mohammad Saeed



This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST