We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 644 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

466 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. If I remember well, the same thing if we put and insteadof 192.168… Because 172.17 … Is another major network… Right??

  2. Hi Francesco,

    Those two networks are from the class B range so yes, they would be summarized to

    192.168.X.0/24 is no problem btw…this is a class C network.


  3. Hi Rene ,

    Is “Discontiguous Network” issue is due mainly classfull routing lookup ? , because it will do look up only classfull manner , like router has to do a look up for destination network /24 , as the 1st octate is belongs to class A range it wont check further the the mask part , if network not existing it will drop it ?

    Can you guide on “Discontiguous Network” and its solution aprroach .


  4. Hello Sameer

    For the explanation, I will use the subnets used in the lesson.

    The problem with classful networks is that if there is a destination of this will be installed in the routing table as since 172.16.X.X is a class B network. This works fine as long as all destinations of are to be routed via the same interface.

    However, if you have a case such as this, discontiguous networks with classful routing presents a problem:


    ... Continue reading in our forum

  5. Thank you Laz!!

14 more replies! Ask a question or join the discussion by visiting our Community Forum