RE: SV: Re: Re: RIP secrets

From: vivek chauhan (vivcw@hotmail.com)
Date: Fri Nov 25 2005 - 20:29:39 GMT-3


Hi Ad,

along with passive interface command (which will not send the upates to
the r2), You can use distribute-list gateway command and just deny the
router r2 which is attached to the frame relay interface to restrict the
receiving of rip packets.

vivek

  --------------------------------------------------------------------

  From: Anderson Nery Vilas Boas <andervb@yahoo.dk>
  Reply-To: Anderson Nery Vilas Boas <andervb@yahoo.dk>
  To: Ed Lui <edwlui@gmail.com>, ccielab@groupstudy.com
  Subject: SV: Re: Re: RIP secrets
  Date: Fri, 25 Nov 2005 23:26:54 +0100 (CET)
>That is the question:
>
> -r1 cannot receive or send uptates to r2 expect on frame -relay
>link"
>
> the problem is , to not send is easy , just passive interface.
  But how make the other interfaces do not receive if all networks are
  include in rip process by the net command?
>
>Ed Lui <edwlui@gmail.com> skrev:
> Pete,
>
>No sure if I understand the question correctly. I think the question
>is " -r1 cannot receive or send uptates to r2 expect on frame -relay
>link"
>
>He did not mention if the interface needs to be included in the
>routing protocol. Anyway, I would use passive interface and md5
>authentication if it is rip 2.
>
>Would that work ?
>
>Ed Lui
>
>On 11/25/05, Peter McCreesh
>wrote:
> > Hi Ed,
> > you could use the neighbor command to determine what interface is
  used and
> > make all interfaces passive including the FR. This will mean all
  updates are
> > unicast between the neighbors and the passive interface will
  ensure that no
> > broadcasts are sent.
> >
> > HTH,
> >
> > Pete
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:07 GMT-3