From: abdul_rahim@xxxxxxxxxxxxxx
Date: Fri Sep 29 2000 - 20:05:27 GMT-3
Thanks Mark I was just going thru this site as I read this email
Well I have a scenario say in which I want to deny only 203.250.15.0/30 and
permit all
So I made an th efollowing prefix-list,( Note I am applying using neighbor
.... prefix-list in )
ip prefix-list abc seq 1 deny 203.250.15.0/30
But how do I allow any
Thats whats the equivalent of permit any is it 0.0.0.0/0
Thanks in advance
Abdul
"Mark Lewis" <markl11@hotmail.com> on 09/29/2000 03:57:00 PM
To: abdul_rahim@ccsi.canon.com
ccielab@groupstudy.com
cc:
Subject: RE: question on extended access-lists for BG P route filtering
Ref. for you:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c/1c
prt1/1cbgp.htm
>From: abdul_rahim@ccsi.canon.com
>Reply-To: abdul_rahim@ccsi.canon.com
>To: "Mark Lewis" <markl11@hotmail.com>
>CC: ccielab@groupstudy.com
>Subject: RE: question on extended access-lists for BG P route filtering
>Date: Fri, 29 Sep 2000 14:36:39 -0700
>
>
>Whats a prefix-list and how can it be used in this scenario
>Any feedback would be highly appreciated
>Thanks
>abdul
>
>
>
>
>"Mark Lewis" <markl11@hotmail.com>@groupstudy.com on 09/29/2000 08:47:05
AM
>
>Please respond to "Mark Lewis" <markl11@hotmail.com>
>
>Sent by: nobody@groupstudy.com
>
>
>To: ccielab@groupstudy.com
>cc:
>Subject: RE: question on extended access-lists for BG P route filtering
>
>
>Yup, and you can use a prefix-list to do the same thing...
>
>Mark
>
> >From: smaljure@cibernetworks.com
> >Reply-To: smaljure@cibernetworks.com
> >To: jconnary@cisco.com, ccielab@groupstudy.com
> >Subject: RE: question on extended access-lists for BG P route filtering
> >Date: Fri, 29 Sep 2000 11:26:36 -0400
> >
> >Hi
> >The extended access-list normally has the interpretation of <<the
> >destination network or host>>
> >Within the context of BGP, we can use the extended access-list to
specify
> >the mask associated with the network to be filtered or controlled.
> >I do not know where it came from though. It works
> >Sanjay
> >
> >-----Original Message-----
> >From: Connary, Julie Ann [mailto:jconnary@cisco.com]
> >Sent: Friday, September 29, 2000 10:46 AM
> >To: ccielab@groupstudy.com
> >Subject: question on extended access-lists for BG P route filtering
> >
> >
> >Hi All,
> >
> >In Halabi's Internet routing Architecture book he has the following
>example
> >that confuses me (page 310):
> >
> >If you want to filter 172.16.0.0/16 such that only 172.16.0.0/16 and not
> >172.16.0.0/17, 172.16.0.0/18 ... are
> >also permitted you must use and extended access-list. Thus the standard
> >access-list of will not work:
> >
> >access-list 1 permit 172.16.0.0 0.0.255.255
> >
> >
> >He then goes on to defined an extended access list as:
> >
> >access-list access-list-number permit ip network-number
> >network-do-no-care-bits mask mask-do-not-care-bit.
> >
> >And gives the following example:
> >
> >access-list 101 permit ip 172.16.0.0 0.0.255.255 255.255.0.0 0.0.0.0
> >
> >
> >My question is, where did he get that definition of an extended
>access-list
> >that says the second
> >set of address/mask pairs is a mask/mask-wildcards pair? Is this
specific
> >to how BGP will
> >use the extended-access list vs. using the access-list in say an ACL? I
> >always understood the second pair
> >was the destination network or host.
> >
> >Julie Ann
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:10 GMT-3