I am not confident that ip classless will help this issue. ip classless has to do with how we interpret the content of the routing table and not to do with how interfaces are configured. It is more likely that the ip subnet-zero command might be the solution for the symptom described.

I would ask for some clarification from Gulshan. When you attempt to configure the router with 202.54.10.1 does it give error message saying invalid mask? If so it is a symptom of attempting to configure an address that falls into subnet zero (which your example does). If you configure the router with ip subnet-zero and then attempt to configure the interface it should work ok.

Restriction on the use of subnet zero was common many releases of IOS ago. But those restrictions are not common in more recent versions of code. It sounds like your router is running code which enforces this restriction by default.

HTH

Rick

Rick is right (once again), I just tried it:

MKE-MPLS-Test(config)#no ip subnet-zero

MKE-MPLS-Test(config)#int fa0

MKE-MPLS-Test(config-if)#ip add 202.54.10.1 255.255.255.252

Bad mask /30 for address 202.54.10.1

MKE-MPLS-Test(config-if)#exit

MKE-MPLS-Test(config)#ip subnet-zero

MKE-MPLS-Test(config)#int fa0

MKE-MPLS-Test(config-if)#ip add 202.54.10.1 255.255.255.252

MKE-MPLS-Test(config-if)#

Points well earned.

Collin

Thanks for the compliment (and for the rating).

It is an interesting error message - why does it say bad mask when the mask is perfectly ok?

What it is really saying is that the mask puts the address in an incorrect place.

HTH

Rick

I was reading too fast... I thought ip subnet-zero until I saw .10 which I thought was the last octet.