From: Sean C (Upp_and_Upp@hotmail.com)
Date: Thu Dec 09 2004 - 13:21:20 GMT-3
No one wants to make this complicated, but everyone wants to get this right.
If this task is asking for the minimum number of prefix statements, sure we
can name that tune in 3 lines (2 denys and a permit all). But, assuming
this task is like most other tasks, and the minimum number of statements are
expected - can anyone solve this in 2 lines?
Andrew's answer, while close, doesn't block the required prefixes - thus
incorrect (unless I configured his solution wrong). Your answer, while it
would work, requires 3 lines. If this task is indeed solvable in 2 lines,
your solution would be incorrect also.
Is there a solution that works with only 2 prefix lines?
----- Original Message -----
From: "Lee Donald" <Lee.Donald@t-systems.co.uk>
To: "Sean C" <Upp_and_Upp@hotmail.com>; "Edwards, Andrew M"
<andrew.m.edwards@boeing.com>; <Zimia123@aol.com>; <ccielab@groupstudy.com>
Sent: Thursday, December 09, 2004 9:57 AM
Subject: RE: prefix list
> Does this need to be so complicated?
> Why not use a single line for each prefix list entry? What are the
> requirements of the question?
>
> -----Original Message-----
> From: Sean C [mailto:Upp_and_Upp@hotmail.com]
> Sent: 09 December 2004 14:45
> To: Edwards, Andrew M; Zimia123@aol.com; ccielab@groupstudy.com
> Subject: Re: prefix list
>
> You sure on that?
>
> If I'm receiving prefixes 197.68.20,21& 22.0/24, and apply a prefix to
block
> in only 21&22 (and still allow 20):
>
> ip prefix-list 1 se 10 deny 197.68.21.0/23 ge 24 le 24
> ip prefix-list 1 seq 20 permit 0.0.0.0/0 le 32
>
> 1st, the prefix list goes to 20
> R3#sh ip pref
> ip prefix-list 1: 2 entries
> seq 10 deny 197.68.20.0/23 ge 24 le 24
> seq 20 permit 0.0.0.0/0 le 32
>
> And I end up blocking only 20 and 21 - not 21 and 22.
> R3#sho ip bgp
> Network Next Hop Metric LocPrf Weight Path
> *> 197.68.22.0 23.23.23.2 0 0 1 i
>
> ----- Original Message -----
> From: "Edwards, Andrew M" <andrew.m.edwards@boeing.com>
> To: <Zimia123@aol.com>; <ccielab@groupstudy.com>
> Sent: Wednesday, December 08, 2004 4:57 PM
> Subject: RE: prefix list
>
>
> > Yep...
> >
> > Router bgp xxx
> > Neighbor w.x.y.z route-map BGP_IN in
> >
> > Route-map block BGP_IN
> > Match ip prefix-list test
> >
> > ip prefix-list test seq 5 deny 197.68.20.0/23 ge 24 le 24
> > ip prefix-list test seq 10 permit 0.0.0.0/0 le 32
> >
> >
> > Andy
> >
> > -----Original Message-----
> > From: Zimia123@aol.com [mailto:Zimia123@aol.com]
> > Sent: Wednesday, December 08, 2004 12:33 PM
> > To: ccielab@groupstudy.com
> > Subject: prefix list
> >
> >
> > say i would like to stop 197.68.21.0/24 and 197.68.22.0/24 from entering
> > my
> > AS in bgp using prefix-list but allow all the other networks. any
> > examples ? thanks
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.807 / Virus Database: 549 - Release Date: 12/7/2004
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.807 / Virus Database: 549 - Release Date: 12/7/2004
This archive was generated by hypermail 2.1.4 : Mon Jan 03 2005 - 10:31:25 GMT-3