TELE10025 Assignment 2
Student Name: _________________________________
Part 1 (5 marks) Using ipconfig, ping and tracert
Please perform tasks outlined below, and fill in your screenshots / answers into the following
tables. Submit these results only, and please delete all instructions following these tables.
Output#1a (cropped screenshot)
Output#1b (cropped screenshot)
Questions 1c
Item Value
Hostname of your PC
How did your PC get its IP address (for the
physical interface)- Automatic or manual?
MAC address of you active interface
IP address of your active interface
Your default gateway
Output#1d (cropped screenshot)
Output#1e (cropped screenshot)
Answer for #1f
Answer for #1e
INSTRUCTIONS (please delete before submission)
Assuming you are using a Microsoft Windows-based computer, open your Command window
(StartRuncmd). (For MacOS and Linux computers, you can open a “terminal” window.)
(a) Type ‘ipconfig |more’ in the command window prompt. That straight line in front of
more is called ‘pipe’ and is usually grouped with the \ i.e. back-slash key.
(For MacOS and Linux computers, you need to use ifconfig instead.)
This is the summary information about all the adapters (both physical and virtual) installed
in your PC. Look for the Ethernet NIC information, even tough it may not display any
information if you are not connected to the Ethernet. Take a screenshot of the output the
‘ipconfig’ command, and place in Output#1a.
Important: Make sure to take a clean, clear screen (Alt+ PrintScreen) capture of the command
window. Crop your image to show only the relevant information.
Figure 1-1: Output of the command ‘ipconfig’
(b) Now type ‘ipconfig /all |more’ to get more detailed information about the
adapters. The result will be something similar to figure below.
(For MacOS and Linux computers, please look up the appropriate ifconfig flag to
perform this task.)
Look for your Ethernet NIC info, take a screenshot of your own (and remember to crop to
keep only the relevant info) and provide in Output#1b.
Figure 1-2: Output of the command ‘ipconfig /all’
(c) There are several questions in table 1c. You can find the information from your ipconfig /all
output. Please fill out answers in table 1c.
(d) Check the connectivity between your PC and Google’s DNS server. Use the ‘ping’ utility
command to test the connectivity. Ping is the application portion of ICMP, and would
provide a user-friendly readout.
Type ‘ping target_ip_address ’ at command prompt. Here the target_ip_address is the IP
address 8.8.8.8. If properly connected, you will response similar to the figure below:
Figure 1-3: Output of ping
Please take a screenshot of your own (and remember to crop to keep only the relevant info)
and provide in Output#1d.
(e) Check the connectivity between your PC and Google’s DNS server in more details. Let’s use
the traceroute utility (called tracert in Windows and traceroute in MacOS and Linux)
Type tracert target_ip_address’ at command prompt using 8.8.8.8 again.
(For MacOS and Linux computers, you need to use traceroute command instead.)
You will response similar to the figure below. Please take a screenshot of your own (and
remember to crop to keep only the relevant info) and provide in Output#1e.
Figure 1-4: Output of traceroute
Please do a few searches with your favourite search engine to answer two questions.
(f) What are the different IP addresses shown in your Traceroute result? Please list your
sources using any referencing method (even a simple URL listing will be fine).
(g) In the traceroute/tracert output, you will likely see some devices not wanting to
respond (in the figure D this was highlighted in red circle). What would make devices
refusing to answer? Please list your sources using any referencing method (even a
simple URL listing will be fine).
Part 2 (7 marks): Investigate PDU
Please perform tasks outlined below, and fill in your screenshots / answers into the following
tables. Submit these results only, and please delete all instructions following these tables.
Table 2a
Source & Destination addresses
Your IP address (Source)
Google DNS server IP (Destination) 142.77.1.1
Output 2b (cropped screenshot)
Table 2c
Item Value
1 Layer 2 protocol name
2 Frame size (byte)
3 Time (of the single packet
capture)
4 Layer 3 protocol name
5 Protocol value inside layer 3 (i.e.
the value in ‘Protocol’ column)
6 Destination MAC address
7 Source MAC address
8 Destination IP address (verify it is indeed 142.77.1.1)
9 Source IP address
10 Data (see the ASCII values in
lower pane)
INSTRUCTIONS (please delete before submission)
Installing Wireshark software
If you already have a recent version of Wireshark on your PC, skip this task and go to (2b).
Otherwise download the latest stable version of Wireshark from www.wireshark.org
Install Wireshark by accepting default
settings.
Re-boot your computer after installation.
Figure 2-1 Wireshark Install
Navigate functions of Wireshark
Start Wireshark, and pay attention to your active interface (NIC) where there are packet traffics.
In the example below the active interface is WiFi:
Figure 2-2 Wireshark startup interface
Wireshark can capture packets (using WinPCap driver) that flow through the NICs of the PC.
Double click on the NIC you want Wireshark to “sniff” (i.e. capturing packets) to see the screen
below:
Stop button
Serial number
Timestamp
List of all
captured packets
Source IP address
Destination IP address
Upper layer protocol
Protocol-wise
formatting of the
selected packet
Hex and ASCII
values of the
packet content
Figure 2-3: Wireshark capturing live packets
Investigate Capture Window
Please examine your own Wireshark capture window (similar to Figure 2-3). The captured
datagrams are displayed with Timestamp (capture instance) on upper pane. This list keeps on
increasing as the capture continues. To stop the capture, press red colour ‘Stop’ button.
(The “Time” as displayed is the number of seconds elapsed since you began capturing.)
The middle pane contains protocol-wise detailed breakdown of the content of the selected PDU
in the upper pane. Click on the different layers to see additional info:
Figure 2-4: PDU of different layers
The bottom pane contains the whole content of the selected packet in ‘raw’ Hex and ASCII
formats. Note that some ASCII values are shown as just dots (‘.’), as there is no printable
character shape for some ASCII values.
Figure 2-5
Investigate the panes, toolbar buttons and columns and their meaning in the main capture
window.
Stop and re-start Capture & Analyze Captured Packets
Stop the live capturing (if it is running). Re-start the capturing (ignore the Saving message).
From the command prompt (as you did in Part 1), use ipconfig /all on Windows or
ifconfig on MacOS or Linux to find your own IP address (i.e. source), and let’s ping to a
Verizon Business web server at 142.77.1.1 IP address as the destination:
Table 2a: Source & Destination addresses
Your IP address (Source)
Google DNS server IP (Destination) 142.77.1.1
Use CMD (or terminal in MacOS/Linux) to ping 142.77.1.1. Observe the Ping (ICMP Request, and
if successful the ICMP Reply) packets are appearing in the capture window of Wireshark. Stop
the capture once your own pinging is done.
PLEASE NOTE: in a busy Wi-Fi environment, you may be seeing multiple entries. You MUST find
your own ping (Echo Request).
In an Ethernet environment, you should only be seeing your own pinging.
Use the filter bar to only view “icmp” related packets:
Figure 2-6: Filtering for ICMP packets
IMPORTANT:
Please examine only one (1) single ICMP Request packet sent from your computer (i.e. the
source should be your IP address, and destination would be 142.77.1.1. Please fill up table 2b
and 2c.
Table 2b: Please paste a single screenshot, crop and display any portion your observed ICMP
Request packet.
Make sure you explore the middle pane by expanding different sections to look for relevant
information:
Figure 2-7
For Table 2c, section 10 “Data” information can be found by examining ICMP section:
Figure 2-8
Part 3 (8 marks): IPv4 address
Please find the PDF document “Subnetting Examples” in SLATE course material section,
and be comfortable with at least one method.
Use any method to solve the sample question in Deck 4.2:
Host with an address 192.168.100.100 has a subnet mask of:
- 255.255.255.0 (and CIDR of /24)
- 255.255.255.128 (/25)
- 255.255.255.192 (/26)
For each of the three CIDR, please find (a) the Network ID, and (b) the Broadcast
addresses.
You can type or write out your work, using any of the methods outlined in “Subnetting
Examples” PDF.
If you are hand-writing out your answers, please take clear photos and incorporate the
photos into this document to upload. Separate photos or unclear photos will not be
marked.
