Sure enough, the given scale shows the data.
If we're looking at a 50 kbps average traffic rate, we should see the y-axis scale from 50,000 to 500,000, or 500 bits. Next, we'll graph the data at 10 second intervals. That wireless card is handling slightly less traffic than a dial-up connection. Now to get a rate, divide that by the time interval of 1 second (that's our time resolution on this graph), for 50 kbps. The traffic is around the 50,000 bit tick, which means that the y-axis (amount of data) is 50,000 bits = 50 kilobits. Start with data at 1 second intervals, and set scale to 10,000 bits: Let's walk through how we can interpret the graphs to figure out about how much data the wireless card is seeing.īefore beginning, apply a moving average filter, to minimize the jumps in the order of magnitude of the measurements due to differences in sampling rates and resolutions. This will change depending on the time window you're looking at. When you use the Scale drop-down menu, it will scale the y-axis to go from 0 to that number. Now you can scale using orders of magnitude: Then the y-axis tick marks represent the number of bytes. The units of the graph are a little hard to decipher, but here's how it works: Here is the same pcap file first, the rather boring 1-second resolution:Īnd the much more interesting 10-minute resolution:
#Iograph windows series
The IO graph shows a time series of network traffic, which you can change the resolution and scale of, and filter. The first way to show IO information is the Wireshark IO Graph, in Statistics > IO Graph. Various ways of using Wireshark to see the amount of traffic on a network.
0 kommentar(er)
