Network Analysis using Wireshark: A Comparative Study of Two Websites
VerifiedAdded on 2025/05/03
|6
|356
|464
AI Summary
Desklib provides solved assignments and past papers for students.

Network Analysis using Wireshark
Part 1:
The below details are for: http://www.lightfm.com.au
1. Capture Time
2019-05-27 09:29:10
2. Captured packets.
Ethernet -------------- 281 Packets
IPV4 ---------------------281 Packet.
TCP -------------------------281 Packet.
TLS------------------------- 208 Packet
Total packets lost 0.
IP address of the client and server is: 192.168.0.16, 54.66.253.179
First packet:
2019-05-27 10:39:23
Total packets lost are zero.
Part 1:
The below details are for: http://www.lightfm.com.au
1. Capture Time
2019-05-27 09:29:10
2. Captured packets.
Ethernet -------------- 281 Packets
IPV4 ---------------------281 Packet.
TCP -------------------------281 Packet.
TLS------------------------- 208 Packet
Total packets lost 0.
IP address of the client and server is: 192.168.0.16, 54.66.253.179
First packet:
2019-05-27 10:39:23
Total packets lost are zero.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Client and server IP address are as follows: 192.1168.0.16 and 72.247.218.200
Part 2:
The below details are for: http://www.lightfm.com.au
1. Throughput
As per above graph, We can see that we are getting maximum throughput which 13000 bits/s output
of 40 streams which indicates we are not loosing any packets.
2. Round Trip Time
The average round trip time for the below graph is 184ms which indicates a bit latency as we are
connecting to this website throough the internet link.
Part 2:
The below details are for: http://www.lightfm.com.au
1. Throughput
As per above graph, We can see that we are getting maximum throughput which 13000 bits/s output
of 40 streams which indicates we are not loosing any packets.
2. Round Trip Time
The average round trip time for the below graph is 184ms which indicates a bit latency as we are
connecting to this website throough the internet link.

3. Packet Loss
From the below graph we are seeing that few packets are getting lost which has retransmitted again
as TCP is a connection oriented protocol.
The below details are for: http:// iview.abc.net.au
The below graph looks good as we are seeing few delays which is due to the minimal timestamps.
2. Round Trip Time
The maximum round trip time for the below graph is 48 ms.
From the below graph we are seeing that few packets are getting lost which has retransmitted again
as TCP is a connection oriented protocol.
The below details are for: http:// iview.abc.net.au
The below graph looks good as we are seeing few delays which is due to the minimal timestamps.
2. Round Trip Time
The maximum round trip time for the below graph is 48 ms.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3. Packet Loss
Few packets are lost and they will be retransmitted again due to Connection oriented protocol.
As per both the throughput graph, We ran first graph for 10 minutes and the other one is for 1
minutes, However first graphs throughput is higher compared to second one as my internet speed
was faster and other point is it is tcp oriented streaming which is having retransmission capability
due to which lost packets are retransmitted again via SACK flag.
Part 4:
I have downloaded Ethereal.
I am not getting TCP stream graph in Ethereal. Not able to collect throughput, RTT, Packet loss graph
from this tool as I am not getting any feature to collect all this.
Otherwise everything looks similar to Wireshark.
Few packets are lost and they will be retransmitted again due to Connection oriented protocol.
As per both the throughput graph, We ran first graph for 10 minutes and the other one is for 1
minutes, However first graphs throughput is higher compared to second one as my internet speed
was faster and other point is it is tcp oriented streaming which is having retransmission capability
due to which lost packets are retransmitted again via SACK flag.
Part 4:
I have downloaded Ethereal.
I am not getting TCP stream graph in Ethereal. Not able to collect throughput, RTT, Packet loss graph
from this tool as I am not getting any feature to collect all this.
Otherwise everything looks similar to Wireshark.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Everything looks similar to Wireshark.
4. Statistics generation:
Below graph is the only thing which I am able to generate from this tool which is quite different than
Wireshark.
4. Statistics generation:
Below graph is the only thing which I am able to generate from this tool which is quite different than
Wireshark.

⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 6
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.