CS331 · Computer Networks · Prince Sultan University

Every packet, hop by hop, layer by layer.

A Wireshark lab that reads real packets off a MacBook's Wi-Fi, from the Ethernet header to the round-trip time. Then two Cisco Packet Tracer builds: a subnetted two-LAN network joined by one router, and a web server reached from a client's browser.

TTL 128 → 127 at R1 /24 → 4 × /26
R1 · console router
10
ICMP packets behind one ping -c 4
78.52ms
Round trip on the wire, vs 121.913 ms in ping
62hosts
Per /26, four subnets carved from one /24
TTL 127
Exactly one router between the two LANs
00 · Abstract

The IP address says where a packet is going. The MAC address says where it goes next.

The coursework looks at one network from two sides. First by watching it: a Wireshark capture on macOS, read through six display filters. A single ping produced ten ICMP packets, and the first echo request was framed for the router's MAC, not Google's.

Then by building one. In Packet Tracer, 199.19.30.0/24 was split into four /26 subnets, and a Cisco 2901 router joined two of them. The first ping failed with 100% loss because the two switch uplinks were on swapped router ports. After re-cabling, replies came back with TTL=127: one hop.

01 · Three projects

One lab to read the wire, two projects to build it.

Each has its own pages, screenshots and presentation.

lab / 01

Wireshark Packet Capture and Display Filtering

Live capture on a MacBook Air's en0, six display filters, then one ping traced from the Ethernet header to its RTT.

L2 EthernetL3 IP · ICMPL7 HTTP · DNS
Filters
6
ICMP
10
Wire RTT
78.52ms
Frame 228 went to the gateway's MAC, addressed to Google's IP.
project / 01

Switch and Router Network Design

A Cisco 2901 and two 2960 switches in Packet Tracer. 199.19.30.0/24 subnetted to /26, a web page served across the router.

L1 CablingL2 SwitchingL3 RoutingL7 HTTP
Subnets
4
Devices
8
Reply TTL
127
First ping: 100% loss. The uplinks were on swapped router ports.
project / 02

Web Server Configuration

Group project. A Packet Tracer server with HTTP and HTTPS on and a page for the group, opened from a client's browser by IP.

L3 AddressingL7 HTTP · HTTPS
Type
Group
Marks
2.5
Status
WIP
In progress. No DNS server: the page is reached by IP address.
02 · Ping lab

Ping across R1, then swap the cables and try again.

The Project 1 network, simulated. Pick a source and a destination, and choose whether the switch uplinks are cabled to the right router ports. Watch which pings survive and what TTL comes back.

C:\> ping · project 1 topology
source
destination
uplinks
Reply TTL
127
Router hops
1
Replies
4 / 4

          
Pick a source and destination to send four echo requests.
Hosts start at TTL 128 R1 replies with 255 Simulated
03 · The capture

One ping, ten ICMP packets.

These are the real frames from wireshark_ping.pcapng. Apply the same filters used in the lab and watch the count change: 10 in total, 6 from the Mac, 4 from Google. The two red rows are not part of the ping. They are port unreachable messages the Mac sent for UDP that arrived on closed ports.

icmp displayed 10 / 10
No.TimeSourceDestinationTTLInfo
22810.013828192.168.1.229172.217.17.3564Echo (ping) request
23010.092348172.217.17.35192.168.1.229114Echo (ping) reply
23710.984633192.168.1.229172.217.17.3564Echo (ping) request
23811.074491172.217.17.35192.168.1.229114Echo (ping) reply
29611.986483192.168.1.229172.217.17.3564Echo (ping) request
30012.077758172.217.17.35192.168.1.229114Echo (ping) reply
32112.608500192.168.1.229192.168.1.164Port unreachable
35012.993154192.168.1.229172.217.17.3564Echo (ping) request
35913.097548172.217.17.35192.168.1.229114Echo (ping) reply
41915.664519192.168.1.229198.41.192.6764Port unreachable
round trip · wire vs ping, ms Wiresharkping
echo 1seq=0
78.52121.913
+43.39
echo 2seq=1
89.858
+2.13
echo 3seq=2
91.275
+1.39
echo 4seq=3
104.394
+2.09
04 · Two clocks

The wire took 78.52 ms. The app counted 121.913.

Wireshark stamps a packet when it passes the network interface. ping reads the clock inside the program, so it also counts the kernel, socket buffers and the time it takes to be scheduled. That overhead was about 43 ms on the first echo and only 1 to 2 ms on the other three.

CS331 · Data Communications and Computer Networks

Open a presentation, or download the network.

Each project has an animated deck. Use the arrow keys, click or swipe to move through it.