From: Mohamed Saeed (mohamed_saeed2@rayacorp.com)
Date: Thu Dec 14 2006 - 02:39:50 ART
Hi Salman
Actually, R1 (the router with ACL applied) loses its neighborship with
R2, that is R2 is not in the list displayed with the "sh ip eigrp nei"
on R1. What makes me thinking over is that I see R1 as a neighbor on R2.
The access list has not to do with the EIGRP hello multicast packets, so
I was expecting to have bidirectional EIGRP peering with route updates
prevented from R2 to R1. What I got is a unidirectional peering !
Kind Regards
________________________________
From: Salman Abbas [mailto:dukelondon@gmail.com]
Sent: Thursday, December 14, 2006 7:25 AM
To: Mohamed Saeed
Cc: ccielab@groupstudy.com
Subject: Re: EIGRP Neighborship - Unidirectional ?
Hi Saeed,
This behaviour is absolutely normal. The access-list prevents routes
from being advertised from one neighbor to another but it doesn't block
EIGRP hello packets. The neighbor relationship will not get affected by
the ACL.
HTH,
Salman
On 12/14/06, Mohamed Saeed <mohamed_saeed2@rayacorp.com> wrote:
Hi All,
I have a setup in which R1 and R2 are EIGRP neighbors. An access list is
configured at R1 to drop inbound EIGRP packets received from R2. On R1,
I could not see R2 as a neighbor (certainly because of the access list).
However, on R2 I could see R1 as a neighbor and I could get EIGRP
routes.
Appreciate if someone could explain this behavior.
Kind Regards
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:38 ART