Re: prefix-list 128.0.0.0/2 ge 17 not matching net 192.1.1.0/24

Hi,
Its because you have 128.0.0.0/2, this makes your pool of routes
128.0.0.0 - 191.255.255.255

Try changing to 128.0.0.0/1 ge 17 and see the output.

Cheers!

On 4/25/10, Ladee Geek <ladeegeek_at_gmail.com> wrote:
> for the life of me I cannot determine why the prefix noted above is not
> matching the prefix 192.1.1.0/24.
>
>
> The topology is r3 and r5 as eBGP peers. R5 originating 128, 191, and 192
> routes. R5 with the prefix permit 128.0.0.0/2 ge17 attached to the R3
> neighbor statement. That prefix statement is not permitting the 192 route.
>
>
>
> R3 before the prefix-list
>
>
>
> Network Next Hop Metric LocPrf Weight Path
>
> *> 128.1.1.0/24 10.1.35.5 0 0 35 i
>
> *> 191.1.1.0/24 10.1.35.5 0 0 35 i
>
> *> 192.1.1.0 10.1.35.5 0 0 35 i
>
>
>
> R3 after the prefix-list
>
>
>
> Network Next Hop Metric LocPrf Weight Path
>
> *> 128.1.1.0/24 10.1.35.5 0 0 35 i
>
> *> 191.1.1.0/24 10.1.35.5 0 0 35 i
>
>
>
>
>
> R5 Loopbacks
>
>
>
> Loopback128 128.1.1.5/24
>
> Loopback191 191.1.1.5 /24
>
> Loopback192 192.1.1.5/24
>
>
> --
> r/
> LG
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Best Regards,
Tolulope.
Blogs and organic groups at http://www.ccie.net