From: Jonathan Greenwood II (gwood83@gmail.com)
Date: Tue Jul 15 2008 - 12:49:37 ART
Igor when you use the neighbor command you are sending RIP updates via
unicast by specifiying the IP Address of the neighboring router as opposed
to the multicast address 224.0.0.9 which all rip enabled interfaces listen
on. Passive interface with RIP doesn't allow updates to be sent out the
interface but an interface can still receive updates from my understanding.
To actually form the neighbor relationship the interface should not be
configured for passive interface. You could also peform RIP authentication
on both sides depending on the requirements/restrictions of the question.
HTH
Jonathan
On Tue, Jul 15, 2008 at 9:44 AM, Igor Manassypov <imanassypov@rogers.com>
wrote:
> Could someone please clarify rip's neighbor command mixed with a
> passive-interface? For example, if you are asked to make sure that routing
> updates are only sent to a particular router, I will configure a
> corresponding 'neighbor' entry under my rip process, but to satisfy the
> requirement that only that particular router gets updates I would also need
> to enable the passive interface. As soon as I do that, there are no more
> routing updates coming from that interface even though I have an explicit
> neighbor configured... If I do not use the passive interface, then other
> routers will get updates breaking the requirement...
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:55 ART