Step $4$: Protocol Overhead

Estimate the download protocol overhead, or percentage of the download bytes taken up by protocol overhead. To do this, consider HTTP data $($headers and message$)$ to be useful data for the network to carry, and lower layer headers $($TCP$,$ IP$,$ and Ethernet$)$ to be the overhead. We would like this overhead to be small, so that most bits are used to carry content that applications care about. To work this out, first look at only the packets in the download direction for a single web fetch. You might sort on the Destination column to find them. The packets should start with a short TCP packet described as a SYN ACK, which is the beginning of a connection. They will be followed by mostly longer packets in the middle $($of roughly $1$ to $1\mathrm{.}5KB),$ of which the last one is an HTTP packet. This is the main portion of the download. And they will likely end with a short TCP packet that is part of ending the connection. For each packet, you can inspect how much overhead it has in the form of Ethernet $/$ IP $/$ TCP headers, and how much useful HTTP data it carries in the TCP payload. You may also look at the HTTP packet in Wireshark to learn how much data is in the TCP payloads over all download packets.

Turn$-$in: Your estimate of download protocol overhead as defined above. Tell us whether you find this overhead to be significant.

$"$Wi$-$Fi $($tcp port $80)$File Edit View Go Capture Analyze StatisticsApplya display fiter $...$