One - lab report example

One

February Lab Report This lab report focuses on a thorough analysis of the lab activity done using wireshark and wget applications in the examination of a packet trace in a particular computer network. Its aim is to aid in filtering and analyzing network packets thus playing a huge role in making it easy to understand the characteristics of different network protocols such as the HTTP and TCP.
The lab simply entails fetching a web URL from a web server to my computer, which is basically, acting as the client. This is then followed by starting up wireshark and beginning a packet capture using the filter of the Transmission Control Protocol Port (TCP Port 80) number eighty. Upon a thorough analysis of the lab, the following is what was found out (Sanders 2007).
It is vital to note that, I firstly noticed that, the number of packets captured was dependent on the size of a particular URL. That is, the smaller the URL the lower the number of packets and the bigger the URL, the higher the number of packets. Additionally, I perceived that the first two packets in the beginning of trace are in most cases made up of equal size while the third one is of the smallest value compared to the other two. Furthermore, I noted that when the value (200 OK) appears in a trace result, then, it means that the fetch operation of a particular URL or website site must has been successfully executed (Sanders 2007).
Lastly but certainly not the least, regarding the lengths of the network packets, the following is what was captured. The first one is of the length 76 units. The second one was of the same size at the first one, which is 76 units. The third one is of the length, 64 units (Sanders 2007).
Works cited
Sanders, Chris. Practical Packet Analysis: Using Wireshark to Solve Real-World Network Problems. San Francisco: No Starch Press, 2007. Print.