Thanks Edison, that is what I was thinking as well .

Rgds.

D.

One more thing to add here , a standard access list Ie

"access-list 1 permit 10.10.0.0 0.0.31.255" will permit the /19 aggregate as well as the more specific /24 networks.

In my case "deny 155.195.128.0 0.0.0.255" is denying /24 as well as the more specific networks.

If I replace deny 155.195.128.0 0.0.0.255 by ip prefix-list deny 155.195.128.0/24 , then I will "only" match on the /24 subnets and not on the more specific networks anymore ...............

Don't forget A standard access list looks at the network address only and can not check the length of the network mask.

So I was thinking of using:

ip prefix-list deny 155.195.128.0/25

!

ip prefix-list deny 155.195.128.0/25 ge 26 (deny all masks with a length greater than 26 bits routes with a prefix of 155.195.128.0/25)

What do you think ?

Rgds.

D.

No one ?????

Thanks.

D.

If you want the same effect as that access-list statement, you can do

ip prefix-list deny 155.195.128.0/24 le 32

That would deny 155.195.128/24 and any of its more specific subnets, i.e. with any prefix length between 24 and 32 inclusive.

As for those subnets you want to allow, as long as they appear as "permits" in the prefix-list above the deny, then they will be allowed.

Kevin Dorrell

Luxembourg

--- Please disregard ---

Note to myself:

"It is sometimes wiser to keep your mouth shut and risk that someone thinks you a fool, than to open it and remove all doubt."