Router on a stick

Posted by June 21, 2011 in Network Services

Scenario:

You are Sam the network engineer who is responsible for all routing within your company. Two of your colleagues called John and Hadley are having trouble reaching each other, their routers do not have any routing capabilities and they are located in different vlans. It’s up to you to help them restore connectivity by becoming a router on a stick.

Goal:

  • All IP addresses have been preconfigured as specified in the topology picture.
  • Do not configure any routing protocol or use static routes.
  • You are allowed to create additional interfaces and IP addresses on router Sam.
  • Ensure router John and Hadley can ping each other.

It took me 1000s of hours reading books and doing labs, making mistakes over and over again until I mastered all the protocols for CCNA.

Would you like to be a master of networking too? In a short time without having to read 900 page books or google the answers to your questions and browsing through forums?

I collected all my knowledge and created a single ebook for you that has everything you need to know to become a master of CCNA.

You will learn all the secrets about routing, VLANs, trunks, router on a stick and more.

Does this sound interesting to you? Take a look here and let me show you how to Master CCNA!

IOS:

c3725-adventerprisek9-mz.124-15.T7.bin

Topology:

Router on a stick

Video Solution:

Configuration Files

You need to register to download the GNS3 topology file. (Registration is free!)

Once you are logged in you will find the configuration files right here.

Opt In Image
Do you want your CCNA or CCNP Certificate?

The How to Master series helps you to understand complex topics like spanning-tree, VLANs, trunks, OSPF, EIGRP, BGP and more.

Written by René Molenaar - CCIE #41726

Master CCNA and CCNP Today!

You May Also Like

No Picture

VRRP (Virtual Router Redundancy Protocol)

No Picture

IP Event Dampening

About the Author: Rene Molenaar

René - CCIE #41726 is the creator of GNS3Vault.com where he shares CCNA, CCNP and CCIE R&S labs. He also blogs about networking on http://networklessons.com

18 Comments

    1. Once you are logged in the attachments will appear at the bottom of each article.

  2. I have downloaded a topology but when i try to open it GNS3 is giving me following error:

    Local IOS image /data/GNS3/IOS/C3725-AD.BIN cannot be found for hyperviso localhost:7200

    any idea?
    I do have IOS image for 3725 in GNS3

    thanks for ur help

  3. Hi,
    I tried to do this lab according to your video, and everything seems fine but i am not able to ping any router no matter from which router i am sending ping packets. After that I built the topology and than I just copy/pasted your cfg files but it does not work. In the end I tried to copy the whole project, I edited the .NET file in Wordpad according to your video about that but it does not find the image no matter that location path I am writing is correct. The error is: "Exception Detected, stopping importation…". What should I do?Thanks!

    1. I would try to create a new project yourself, save it and open the .NET file in wordpad.

      Then open up my .NET file in wordpad as well and take a close look at the differences. Edit my .NET file so it’s the same and it *should* open without any issues.

      Not sure why your pings are failing, I would have to see your topology & configs.

  4. Hi Rene,
    In your topology Router Hadley interface f0/0 shows IP address 192.168.3.2

    The router interface is actually preconfigured with 192.168.3.1

    Not a big deal, but you won’t get ping replies from 192.168.3.2 unless you change the IP address of the router interface or ping 192.168.3.1 instead.

    Thanks for the great lab 🙂

  5. My solution was a little bit different than your’s. I ended up over engineering things by creating trunks everywhere.

    Your solution was rather elegant and I liked your explanation in the accompanying video.

    Looking forward to doing the rest of the labs (this was my first) !

    1. Glad to hear you like it! We only require a trunk between the switch and the router on the right side. The devices on the left side are normally computers and the only need to be within a single VLAN 🙂

  7. if you cant get the ios for this it wont work no matter what.

    and i looked in your cfg files and there are none listed as stated for your fix

  9. I did exactly the same as your conf but i can’t ping from both routers Hadley and John

    i can only ping from sam to both routers

  10. Hi Rene,

    I have tried to build the same lab in cisco packet tracer 6.1 and all the configurations are correct.

    I have checked some documentation as well and every one did the same thing and it worked for them.

    I can only think that there is some packet tracer ? is it possible or am i missing something?

    1. Packet tracer certainly has some bugs. If you cannot get router on a stick working then I can’t imagine packet tracer being very reliable.

  11. thanks for this lab.

    question: this inter-vlan solution is really bad. I wonder sometimes why they want us to know this instead of layer 3 switching. what would be a modern application of this? or do you think that it is just an introductory step into layer 3 switching?

  12. Thanks Rene for this interesting lab…I didn’t have any problem implementing the whole scenario…I’ve just started studying with your labs and for me it’s a great idea to implement an scenario in order to analize and discover.
    Let me give you a suggestion please…. I always like to use the “wireshark capture” to see the packets exchanged between the elements of the scenario…so I suggest you to include at the end of every lab a brief wireshark capture of the packets…for example in this scenario I saw that in the interface between Sam and the switch the packets have the TAG 802.1q (vlan 2 y 3) while in the interfaces between Jhon/Hadley and the switch the packets are untagged (without tag 802.1q)….thanks Rene…see you…juanjose 😉

Comments are closed.