lantech wrote: » Remember that just because a question doesn't specifically ask you to subnet doesn't mean you won't have to subnet. The same goes for on the job as well. You might have to do subnetting to help you isolate where the problem with the network is.
networker050184 wrote: » 172.16.0.0/16 is an easy one. You have sixteen network bits so its 172.16.0.0-172.16.255.255. It sounds like you are having issues with subnetting, not longest prefix match.
networker050184 wrote: » Because 172.16.4.3 does not fall into the 172.16.0.0/22 range. 172.16.0.0/22 = 172.16.0.0-172.16.3.255
ToLuTion wrote: » thanks for this but in the following example: Adding a little twist to it. what if sending a packet to the 172.16.1.1 address with the routes in routing table: 172.16.1.1/32 via serial 0/1/1 172.16.1.0/24 via serial 0/1/0 172.16.0.0/22 via serial 0/1/1 172.16.0.0/16 via serial 0/1/0 the route it would take would be? why is this? why does it not take the route ? if longer prefix length is better then 172.16.1.1/32 seems write but 172.16.1.0/24 seems correct also it will have the address 1720.16.1.1 in its network... kindly explain why and how your answer is...