From: Adam Crisp (adam.crisp@totalise.co.uk)
Date: Tue Dec 10 2002 - 11:07:45 GMT-3
RE: eigrp neighbor commandI can add.
There are two easy ways of blocking RIP RECEIVED UPDATES fom unwanted =
sources.
1. use the distance 255 command and reset the distance for the unicast =
neighbors
2. use a distribute list with an EXTENDED access list, the source part =
of the access-list being the allowed neighbour.
Adam
-----Original Message-----
From: Geralt Omhof [mailto:geralt@OmnIT.nl]
Sent: 10 December 2002 14:09
To: Adam Crisp; Tran Tien Phong; Jay Greenberg
Cc: Ram Shummoogum; eward15@juno.com; ccielab@groupstudy.com
Subject: RE: eigrp neighbor command
RIP: with passive interface you block the SENDING of broadcast route =
updates. The router still receives them though. With the neighbor =
command you can unicast routing updates to specific routers.
EIGRP: with passive interface you block the RECEIVING AND SENDING of =
route updates. It prevents the sending of hello packets. Because no =
hello packets are received by a neighbor, there will be no neighbor =
relationship established, therefor no routing updates will be exchanged. =
The neighbor command will not work in this case and it should not be =
used. To be able to do the same as with RIP when you use =
"passive-interface" and "neighbor", you should use "distribute-list" =
with EIGRP. Please someone correct me if I'm wrong.... Check this at:
http://www.cisco.com/warp/public/103/16.html
and
http://www.cisco.com/warp/public/103/eigrpfaq.shtml#Q10
Regards,
Geralt
-----Original Message-----=20
From: Adam Crisp [mailto:adam.crisp@totalise.co.uk]=20
Sent: Tue 12/10/2002 1:46 PM=20
To: Tran Tien Phong; Jay Greenberg=20
Cc: Ram Shummoogum; eward15@juno.com; ccielab@groupstudy.com=20
Subject: RE: eigrp neighbor command
with RIP, you can use "passive interface" to block =
broadcast/multicast, and
use the neighbous command to unicast.
I assume the same is true of EIGRP.
Adam
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf =
Of
Tran Tien Phong
Sent: 10 December 2002 12:33
To: Jay Greenberg
Cc: Ram Shummoogum; eward15@juno.com; ccielab@groupstudy.com
Subject: RE: eigrp neighbor command
If passive interface was specified, RIP and EIGRP will not send any
routing updates via the passive interface, even neighbor command =
used
-----Original Message-----
From: Jay Greenberg [mailto:groupstudylist@execulink.com]
Sent: Tuesday, December 10, 2002 7:20 PM
To: Tran Tien Phong
Cc: Ram Shummoogum; eward15@juno.com; ccielab@groupstudy.com
Subject: RE: eigrp neighbor command
Event with passive-ineterface?
On Mon, 2002-12-09 at 23:54, Tran Tien Phong wrote:
> For RIP, although you configure neighbor command, RIP updates =
still
sent to multicast address 224.0.0.9. You need to define an =
access-list
to prevent this
>
> -----Original Message-----
> From: Ram Shummoogum [mailto:rshummoo@ca.ibm.com]
> Sent: Tue 12/10/2002 8:21 AM
> To: eward15@juno.com
> Cc: ccielab@groupstudy.com
> Subject: Re:eigrp neighbor command
>
>
>
> This is true for RIP but I am not sure about EIGRP. I know =
for a
fact that
> in EIGRP the passive-interface will prevent the formation of
neighbors.
>
> Rgds,
> RAM
>
>
>
> eward15@juno.com@groupstudy.com on 12/09/2002 07:52:52 PM
>
> Please respond to eward15@juno.com
>
> Sent by: nobody@groupstudy.com
>
>
> To: ccielab@groupstudy.com
> cc:
> Subject: Re:eigrp neighbor command
>
>
> I believe the neighbor command is used to send routing
annoucements as
> unicast packets instead of multicast or broadcast cast =
packets.
For
> instance, there may be 5 routers on a segment but only two =
of
them are
> using the same routing protocol. Instead of needlessly =
sending
updates to
> the other routers, you could use a passive-interface to =
block
the
> broadcasts/multicasts on the interface and instead send a
directed unicast.
> Someone please correct me if I am wrong.
>
> Eugene Ward
>
>
>
>
> =
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:42 GMT-3