Yarmouk University

Hijjawi Faculty for Engineering

Technology
Computer Engineering Department

CPE 563: Computer Networking

Laboratory

Task 2: Network Layer Traffic

Simulation Using Cisco Packet Tracer

Basic Information:

Haleemah Adoos
Student Name:

2020980219
Student ID:

3
Student Section Number:
Objective:
 Configure end-node network information using a GUI.
 Configure router network information using a GUI and CLI.
 Explore routing tables.
 Understand the use of Ethernet and IP addresses in a routed environment.

Background:
This lab you should learn how to configure the router in the two ways CLI and GUI.

Router Configuration Using CLI:

The router operating system is called the Internetwork operating system “IOS”, each release has different set
of features that support for a certain protocols, or added features.

1. To enter the CLI of the Router click on the router, select CLI tab.

Figure8: CLI of router.

Command Line modes:

 User Mode: Denoted by a greater than (>) sign after the router prompt (Router>), execute limited and
basic monitoring commands. Troubleshooting commands available in user mode.
 Privileged executive mode: Denoted by a pound (#) sign like this: Router#, commands are entered via
the Command Line Interface (CLI).
 Global configuration mode.
 Other specific configuration modes.
1. Interface mode
2. Line mode
3. Router mode
Figure9: command line modes 1.
 Figure10: command line modes 2.

Basic commands line:

 Configuring a router Name:
Router(config)#hostname NES413.

Figure11: hostname command.

 Configuring router passwords: Passwords restrict access to routers, the following two commands used
to establish authentication before accessing privileged EXEC mode.
o Enable Password: set a password to privileged mode.
Router(config)# enable password yourpassword
o Enable Secret: encrypted secret password to privileged mode.
Router(config)# enable secret yourpassword
 Console port is the port used to access the router and configure the router so we have to authenticate
the access of this port. Console password: limits device access using the console connection.
Router(config)# line console 0
 Router(config-line)# login
Router(config-line)# password yourpassword

Figure12: set password to authorize login to privileged mode.

 Configuring Ethernet interfaces:

Each connected interface (port) must have an IP address and subnet mask to route IP packets.
By default, interfaces are turned off, or disabled. To turn on or enable an interface, the command
no shutdown is entered.
 Configure Ethernet interfaces(port):
Router(config)#interface fa0/0
Router(config-if)#description CONNECTION FROM PC1 TO R1
Router(config-if)#ip address ipaddress subnetmask
Router(config-if)#no shutdown
 Figure13: Assign IP address and subnet mask to the fast ethernet port.

 To show the routing table of the router use the following command on global mode :
Router# show ip route

Figure14: Routing Table.

A Cisco network device contains two configuration files:
 The running configuration file - used during the current operation of the device.
 The startup configuration file - used as the backup configuration and is loaded when the device is
started.
 To save the configuration variables to the startup configuration file , enter the following command at
the privileged EXEC prompt:
Router#copy running-config startup-config.
 Finally to be able to show your overall configurations you make it you need to print

Router#show running-config.
Router Configuration Using GUI:
The end devices and router need to be configured for network access. The router will be configured in
the next task. Each device in a network must have its own unique IP address. These addresses could
come automatically from a DHCP server or could be “statically” assigned by the
operator/administrator. Due to the relatively small number of devices in our simulation, we will
statically assign the IP information. This will include an IP address, a subnet mask and a default router
or gateway on each machine.

Configuring end devices

Initially when you add the end device you should name it as the following. In the Packet Tracer
window, click on the icon for Server1 you add it. In the Server1 screen that opens, click on the Config
tab:(back to the topology to know what you should name each device):
 Figure2:set device display name.
In the Packet Tracer window, click on the icon for Server 1. In the Server1 screen that opens, click on
the Config tab:

Figure 3: Server Network Settings

In the Config tab for Server1, click on the Settings button (as shown above). In this window you can
specify the default Gateway for the end-node. Use the information in the Addressing table to fill in the
Router (Gateway) for Server1.
4. Still in the Server1 Config tab, click the button for the FastEthernet interface:

Figure 4: Server FastEthernet Settings

Configuring Routers

you will configure the IP information for the two network interfaces of the router in our simulation.
In the Packet Tracer window, click on the icon for Router 0. In the Router 0 screen that opens, click on
the Config tab.
 Figure5: Assign IP address.
Click the FastEthernet0/0 button as shown in Figure 4 above. This is the interface connected to the
network with Server1 and PC1 in it. In this screen you can configure both the IP address and subnet
mask for the first Ethernet interface for Router0. Use the Addressing Table on Page 1 to fill in the
correct address for FastEthernet0/0.
To activate the network interface on the router, click in the box next to the Port Status of On in the
upper right corner of the screen.

Lab Work
In this lab you have to create a new packet tracer project, note that in every packet tracer project you should
follow the following four steps to complete the project
Step 1: Topology Construction
 Open Packet Tracer.
 Add two PCs, two Switches, two Servers and one Router.
 Connect the devices as in the Figure 1.
 Figure1: lab work Topology.

Step2: Configure IP information (using GUI or CLI).

Every end nodes or router should have all its IP information, complete your work depending on the following table:

Machine Interface IP Address Subnet mask Gateway

Server1 Fast Ethernet 172.16.10.5 255.255.255.0 172.16.10.1
PC1 Fast Ethernet 172.16.10.10 255.255.255.0 172.16.10.1
Server2 Fast Ethernet 172.16.20.5 255.255.255.0 172.16.20.1
PC2 Fast Ethernet 172.16.20.10 255.255.255.0 172.16.20.1
Router0 Fast Ethernet 0/0 172.16.10.1 255.255.255.0
Fast Ethernet 0/1 172.16.20.1 255.255.255.0

Table1: Address Table.

1st. If we “somehow” know that the first three octets (numbers) in our IP addresses are the network ID, why do
the IP Address for Server 1 and the IP Address for PC1 and the configured Default Gateway need to have the
same first three octets? (Hint: look at the physical network structure.).

to enable them to communicate without needing routing between different networks.

2nd. If we “somehow” know that the first three octets (numbers) in our IP addresses are the network ID,
why do the IP Address for Server 1 and the IP Address for Server 2 have different numbers in at least one of
the first three octets? (Hint: look at the physical network structure.)

Because Server1 and Server2 are in different network subnets. And we do it to prevents direct communication without
a router.

3rd.Should the first three octets of the IP addresses that assigned for the two interfaces on Router0 be the same
or different? Why or why not? (Hint: look at the physical network structure.)

The first three octets should be different. Each interface on Router0 connects to a separate network, so they need
unique network IDs to correctly route traffic between Server1’s and Server2’s networks.
Step3: Test and simulation traffic

In this task you will use the ping program to test the connectivity in your simulated network environment.

 In the main Packet Tracer window, click the icon for PC1. In the PC1 dialog box, click the Desktop tab and then
click on the Command Prompt icon. A simulated Windows command prompt should appear.

4th.At the command prompt, type ipconfig and record the network configuration of PC1 below:
IP Address: 172.16.10.10
Subnet Mask: 255.255.255.0
Default Gateway: 172.16.10.1
5th.At the command prompt of PC1, use the ping command to send ping requests to the local PC1 address (e.g.,
ping 172.16.10.10) – Yes, you’re pinging yourself. What is the result of the command (e.g., did the ping
succeed):

Yes it did,

6th.At the command prompt of PC1, use the ping command to send ping requests to Server1 and the
FastEthernet0/0 interface of Router0 (use the Addressing Table if you need to recall the addresses for these
interfaces). What is the result of these commands (e.g., did the ping succeed):
Server1: yes since PC1 and Server1 are on the same subnet.
Router0-FastEthernet0/0: yes
7th.How was PC1 able to communicate with the interface on the router that is in the other network? In other
words, what allowed the packets to reach a network that PC1 isn’t on?\

The routing procedure done by the router enabled PC1 to communicate with the other subnet ports
using the default gateway .

 In the lower-right corner of the Packet tracer window, click the simulation icon (recall that it looks like a stopwatch)

Figure6: packet tracer simulation mode.

To make things a little easier, we will configure Packet Tracer to show only ICMP messages – this is the
protocol used by ping packets. Click the Edit Filters button as shown in the above figure. A list of protocols will
appear.

In the sub-window that appears, click the check box next to Show All/None. This will clear all protocols. Put a
check mark in the box next to ICMP -- this should be the only check mark in your filter. Now click anywhere
outside this sub-window (e.g., in the main Packet Tracer window). The list of Visible Events should now
contain only ICMP:

Figure7: Determined visible protocol events.

 With Packet Tracer in simulation mode, open the command prompt for PC1 (Click PC1 > Desktop >
Command Prompt) and type the command ping 172.16.20.5 This will cause PC1 to send one ping request to
Server2.

 Click the Capture/Forward button until the ICMP packet reaches Switch0 (one or two clicks).
 Click on the ICMP packet that has reached Switch0 then click on the Inbound PDU details tab.
8th. Fill in the following information about the inbound packet (PDU) at Switch0, also determine to which device
belongs this address:
Source Ethernet (MAC) Address:
Destination Ethernet (MAC) Address:
Source IP Address 172.16.10.10
Destination IP Address 172.16.20.5
 Close the packet details and click on the Capture/Forward button again. The packet should travel from Switch0
to Router0.
 Click on the ICMP packet that has reached Router0. On the OSI Model tab.

9th.Record the addresses shown at Layer 3 in both the “In Layers” and “Out Layers”, also determine to which
devices belong these addresses.
Source IP address in the “In Layers”: 172.16.10.10
Destination IP address in the “In Layers”: 172.16.20.5
Source IP address in the “Out Layers”: 172.16.10.10
Destination IP address in the “Out Layers”: 172.16.20.5
10th. Why are the addresses at the IP layer (Layer 3) the same (In and out)?

Because mac addresses change every time in the packet sending process but source and destination IP addresses
stay the same.

11th. Record the addresses shown at Layer 2 in both the “In Layers” and “Out Layers”,also determine to
which devices belong these addresses.
Source Ethernet address in the “In Layers”: 0060.4735.84b5
Destination Ethernet address in the “In Layers”: 0001.975b.1601
Source Ethernet address in the “Out Layers: 0001.975b.1601
Destination Ethernet address in the “Out Layers: 0090.0C84.6AEB
12th. Why are the addresses at the Ethernet layer (Layer 2) different (In and Out)

Because the mac address change every time.

 Continue processing the simulation and watch the packet travel to the destination and back.