From: Skinner, Stephen (Stephen.Skinner@rbs.co.uk)
Date: Thu Aug 10 2006 - 05:12:31 ART
Hello,
ASAIK,
You cannot use a prefix-list in this fashion , you must use an ACL.
The reason for this is because you cannot express the subnet mask in the
prefix-list.
Please correct me guys if I am wrong.
Stephen Skinner
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]
Sent: 09 August 2006 18:57
To: Aaron Pilcher
Cc: Cisco certification
Subject: Re: ACL 2 Prefix-list
*** WARNING : This message originates from the Internet ***
Hi Aron,
Thanks for your feedback, you are very gentle.
But I'm looking for a prefix-list that matches this routes only
R1(config)#access-list 1 permit 200.1.4.0 0.0.17.0
R1#show ip route list 1
C 200.1.4.0/24
C 200.1.5.0/24
C 200.1.21.0/24
like the access-list does, but for this routes only:
200.1.1.0
200.1.4.0
200.1.5.0
200.1.21.0
200.1.22.0
Thanks
Patri.
On 8/9/06, Aaron Pilcher <apilcher@itgcs.com> wrote:
>
> Wouldn't a 200.1.0.0 0.0.23.0 be more of an appropriate ACL?
>
> That said....
>
> 200.1.0.0/19 ge 32
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Patricia Loreal
> Sent: Wednesday, August 09, 2006 9:10 AM
> To: Cisco certification
> Subject: ACL 2 Prefix-list
>
> Hello Dear Group,
>
> Using this access-list access-list (1) permit 200.1.4.0 0.0.17.0 for
> matching this routes:
>
> 200.1.1.0
> 200.1.4.0
> 200.1.5.0
> 200.1.21.0
> 200.1.22.0
>
> How can I convert the output generated by ACL (1) into 1 Prefix-list
> statment
>
> Thank you very much .!.!.
> Kindest Regard
> Patri.
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:56 ART