From: D. J. Jones (meganac@xxxxxxxxx)
Date: Thu Mar 28 2002 - 16:54:33 GMT-3
ip prefix-list cisco seq 10 deny 9.9.1.0/24
ip prefix-list cisco seq 20 permit 0.0.0.0/0 le 32
Remember that prefix lists are used to identify routes for matching and
filtering and unlike
access lists can be updated incrementally. They are not intended to be used
like an
extended access list using source/destination attributes etc.
hth..dj
----- Original Message -----
From: "Gregg Malcolm" <greggm@sbcglobal.net>
To: <ccielab@groupstudy.com>
Sent: Thursday, March 28, 2002 10:32 AM
Subject: Re: Prefix List Question
> Please disregard my incorrect statement about the host 0.0.0.0 host
0.0.0.0.
> Should be permit ip any any. Seems to work ok. So, I guess the question
is,
> how to do the following with prefix-lists :
> access-list 101 deny ip host 9.9.1.0 host 255.255.255.0
>
> access-list 101 permit ip any any
>
> Gregg
>
>
>
> ----- Original Message -----
> From: Gregg Malcolm
> To: ccielab@groupstudy.com
> Sent: Thursday, March 28, 2002 10:10 AM
> Subject: Prefix List Question
>
>
> Folks,
>
> Does anyone know if there is an equivalent to permit any (all) with IP
> prefix-lists ? Lets say that you were doing an outbound prefix list on a
BGP
> router with a bunch of major nets. Lets say you only wanted to deny one
of
> the major nets. Do you have to manually add the other major nets into
> prefix-list permits ?
>
> Or maybe a better solution would be to use an extended access list in
the ho
> 10.0.0.0 ho 255.0.0.0 format ? With the ACL format, would ho 0.0.0.0 ho
> 0.0.0.0 permit all prefixes ? 0's are don't care's, right ?
>
> Search of the archives didn't reveal anything regarding this.
>
> Thanks, Gregg
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:24 GMT-3