From: Jim Newton (jnewton@xxxxxxxxxxxxxxx)
Date: Wed Feb 20 2002 - 20:03:04 GMT-3
Did you try just using an extended ipx access list and putting in eigrp for
the socket? I haven't tried it, but was wondering if it would have worked.
Access-list 900 permit any any eigrp any eigrp (or whatever your source and
destination would be)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Ahmed
Mamoor Amimi
Sent: Wednesday, February 20, 2002 4:56 PM
To: Wade Edwards
Cc: ccielab@groupstudy.com
Subject: Re: protocol # for eigrp
nope its not..... i found it and it is :
34238 85BE Cisco Enhanced Interior Routing Protocol (EIGRP)
342383 =decimal
85BE =HEX
I was talking about the socket.
I just applied the access-list with 85BE and it worked. and i have also
applied ur # but it didnt worked as by router debug
is saying something like :
6:05:14: IPX: Se0:C.2222.1111.1111->C.ffff.ffff.ffff ln= 70 tc=00 pt=00
ds=85BE ss=85BE, *denied (in)*
If u can see in this that source-socket and destination-socket is 85BE and
denying.
My source was :
http://www.isi.edu/in-notes/rfc1700.txt
-Mamoor
----- Original Message -----
From: Wade Edwards <wade.edwards@powerupnetworks.com>
To: Ahmed Mamoor Amimi <mamoor@ieee.org>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, February 21, 2002 3:37 AM
Subject: RE: protocol # for eigrp
> 88 is EIGRP
> 89 is OSPF
>
> -----Original Message-----
> From: Ahmed Mamoor Amimi [mailto:mamoor@ieee.org]
> Sent: Wednesday, February 20, 2002 4:25 PM
> To: ccielab@groupstudy.com
> Subject: protocol # for eigrp
>
> Can anyone tell me what is the protocol # for eigrp
>
> my accesslist IPX is demanding me to give protocol # of eigrp so it can
> be
> allowed.
>
>
> -Mamoor
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:29 GMT-3