This screen will give you a breakdown of bandwidth by protocol. The first method of seeing bandwidth used is by selecting the menu items: Statistics > Protocol Hierarchy This will isolate the IP / TCP traffic of interest Once you identify a packet belonging to the network flow you are interested in, right click on it > conversation filter > ip / tcp. Apply display filters in wireshark to display only the traffic you are interested in. In my case I started downloading the ubuntu image from their website, in the background leaving wireshark running. Once the download completes, get back to wireshark.ģ. Start a packet capture (preferably without capture filters, just in case we miss some traffic) and start the download (or the service you are testing) Of course, this will test HTTP bandwidth, but since wireshark can sniff any protocol, you can use anything you want for testing.Ģ. Open a web-browser and navigate to a site from where you can download large iso images. In this quick article we explore three different ways of measuring the bandwidthġ. Wireshark has several ways of showing the bandwidth being used, each method displays the information with different granularity / clarity. But when it comes to granularity and detail, almost nothing beats wireshark. There are of course several ways of measuring bandwidth usage from a particular PC. Update: For easy bandwidth visualization from packet captures, check out a web-based pcap parser we wrote:

Wireshark http only filter