Lab 4.3: Packet Tracer, 2 Router Lab - savannahc502/SavC-TechJournal-NET215 GitHub Wiki

Information on this page may be paraphrased or copied from Champlain College materials. Avoid coping as you may be committing plagiarism. This is for note-taking and academic purposes only.

Lab 4-3: Packet Tracer - 2 Router Lab

Saving Router Configurations and Navigating CLI

Use the same file from lab 4-2 and create the 30.30.30.0/24 network.

Set up 2 PCs:

  • PC5: 30.30.30.105, 30.30.30.1 DG, NM 255.255.255.0
  • PC6: 30.30.30.106, 30.30.30.1 DG, NM 255.255.255.0

Add a 2950-24 switch and connect using straight-through cables to the PCs.

image

image

  • Set up an 1841 router with an IP address on Fa0/0 of 30.30.30.1 --> this is the default gateway.
  • In the CLI, type enable to get to the router# (root) line (you may need to type exit beforehand).
  • Type copy run start to save the changes (this is important so during restart, the router configurations save).

Adding Serial Connections Between Routers

Add Serial Ports to Routers

  • Make sure you saved the configurations first
  • Select the Physical Tab on the router
  • Click the Power Button to Off (see diagram below)
  • Drag a WIC-1T interface card into the left slot (Slot 1)
  • Turn the power back On
  • Do this for both routers you're connecting

image

  • In the serial0/1/0 configuration table, configure the IPv4 address to 1.1.1.1 with a subnet of 255.255.255.252 (this subnet allows only two devices on the network).
  • Configure router one the same, with an IPv4 address of 1.1.1.2
  • Connect routers with the serial cable (right lightning bolt)

image

  • The PCs on the different networks will not be able to communicate until the routing tables are configured on Router 1 and Router 0. To do this, we will use RIP, which will allow the routers to broadcast their routing tables to the entire network -- all receiving routers will update their tables accordingly.
  • In the configuration tab, go to RIP and add the missing networks for the respective routers
  • Note that for now, the router will assume a network of 255.0.0.0 -- for the scope of this lab, this is okay.
  • copy start run for both routers again
  • should be all set