Wireshark/Traffic Analysis - Revision history

Admin: /* Total Packet Traffic Statistics */

2016-01-20T04:56:15Z

Total Packet Traffic Statistics

← Older revision		Revision as of 04:56, 20 January 2016
Line 60:		Line 60:
	* MBit/s (0.016 Mbps, or 16 kbps)		* MBit/s (0.016 Mbps, or 16 kbps)

			[[Image:WiresharkTrafficSummary.png\|500px]]

Admin: /* Traffic */

2016-01-20T04:54:42Z

Traffic

← Older revision		Revision as of 04:54, 20 January 2016
Line 1:		Line 1:
	=Traffic=		=Traffic Graphs=

	Various ways of using Wireshark to see the amount of traffic on a network.		Various ways of using Wireshark to see the amount of traffic on a network.
Line 44:		Line 44:

	[[Image:Wireshark_iograph3.png\|500px]]		[[Image:Wireshark_iograph3.png\|500px]]


	=WLAN Traffic Statistics=		=WLAN Traffic Statistics=

Admin: /* WLAN Traffic Statistics */

2016-01-20T04:54:14Z

WLAN Traffic Statistics

← Older revision		Revision as of 04:54, 20 January 2016
Line 51:		Line 51:

	[[Image:Wireshark_WLANTraffic.png\|500px]]		[[Image:Wireshark_WLANTraffic.png\|500px]]


			=Total Packet Traffic Statistics=

			You can see packet traffic from the top-level summary of the pcap file: Statistics > Summary will bring up the summary of the pcap file. There, you can see the following:
			* average packets per second (23.7 in my case)
			* total number of packets (364,000)
			* average packet size (82 bytes)
			* MBit/s (0.016 Mbps, or 16 kbps)






	{{WiresharkFlag}}		{{WiresharkFlag}}

Admin: /* WLAN Traffic Statistics */

2016-01-20T04:50:33Z

WLAN Traffic Statistics

← Older revision		Revision as of 04:50, 20 January 2016
Line 48:		Line 48:
	=WLAN Traffic Statistics=		=WLAN Traffic Statistics=

	If you pick Statistics > WLAN Traffic, you'll get a breakdown of traffic by conversation. You can sort by percentage~~, showing that nearly half the traffic is due to just a few stations~~:		If you pick Statistics > WLAN Traffic, you'll get a breakdown of traffic by conversation. You can sort by percentage:

	[[Image:Wireshark_WLANTraffic.png\|500px]]		[[Image:Wireshark_WLANTraffic.png\|500px]]

Admin: /* WLAN Traffic Statistics */

2016-01-20T04:50:15Z

WLAN Traffic Statistics

← Older revision		Revision as of 04:50, 20 January 2016
Line 48:		Line 48:
	=WLAN Traffic Statistics=		=WLAN Traffic Statistics=

	If you pick Statistics > WLAN Traffic, you'll get a breakdown of traffic by conversation:		If you pick Statistics > WLAN Traffic, you'll get a breakdown of traffic by conversation. You can sort by percentage, showing that nearly half the traffic is due to just a few stations:

	[[Image:Wireshark_WLANTraffic.png\|500px]]		[[Image:Wireshark_WLANTraffic.png\|500px]]

Admin: /* adsf */

2016-01-20T04:48:26Z

adsf

← Older revision		Revision as of 04:48, 20 January 2016
Line 46:		Line 46:


	=~~adsf~~=		=WLAN Traffic Statistics=

	~~==asdfasdf==~~		If you pick Statistics > WLAN Traffic, you'll get a breakdown of traffic by conversation:

			[[Image:Wireshark_WLANTraffic.png\|500px]]



	{{WiresharkFlag}}		{{WiresharkFlag}}

Admin at 04:42, 20 January 2016

2016-01-20T04:42:57Z

← Older revision	Revision as of 04:42, 20 January 2016
Line 46:	Line 46:


		=adsf=

		==asdfasdf==

Admin at 04:34, 20 January 2016

2016-01-20T04:34:03Z

← Older revision		Revision as of 04:34, 20 January 2016
Line 44:		Line 44:

	[[Image:Wireshark_iograph3.png\|500px]]		[[Image:Wireshark_iograph3.png\|500px]]







	{{WiresharkFlag}}		{{WiresharkFlag}}

Admin: /* IO Graph Units */

2016-01-20T03:44:39Z

IO Graph Units

← Older revision		Revision as of 03:44, 20 January 2016
Line 21:		Line 21:
	The units of the graph are a little hard to decipher, but here's how it works:		The units of the graph are a little hard to decipher, but here's how it works:

	Set the Y Axis unit to "Bits/Tick". Then the y-axis tick marks represent the number of bytes. Now you can scale using orders of magnitude: ~~1e3 bites~~ = kilobit, ~~1e6~~ bits = megabit~~, etc.~~		Set the Y Axis unit to "Bits/Tick". Then the y-axis tick marks represent the number of bytes. Now you can scale using orders of magnitude:
			* 1,000 bits = 1 kilobit
	~~(Also, 1 byte = 8 bits)~~		* 1,000,000 bits = 1 megabit

	When you use the Scale drop-down menu, it will scale the y-axis to go from 0 to that number. 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. This will change depending on the time window you're looking at.
Line 31:		Line 31:
	Before 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.		Before 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.

	Start with data at 1 second intervals, and set scale to 10,000:		Start with data at 1 second intervals, and set scale to 10,000 bits:

	[[Image:Wireshark_iograph1.png\|500px]]		[[Image:Wireshark_iograph1.png\|500px]]

	The traffic is around the 50,000 tick, which means 50 kilobits. ~~That~~'s ~~50 kilobits per 1 second~~, or 50 kbps. That wireless card is handling slightly less traffic than a dial-up connection.		The traffic is around the 50,000 bit tick, which means that the y-axis (amount of data) is 50,000 bits = 50 kilobits. 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. That wireless card is handling slightly less traffic than a dial-up connection.

	Next, we'll graph the data at 10 second intervals. 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. Sure enough, the given scale shows the data.		Next, we'll graph the data at 10 second intervals. 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. Sure enough, the given scale shows the data.

Admin at 03:42, 20 January 2016

2016-01-20T03:42:29Z

← Older revision		Revision as of 03:42, 20 January 2016
Line 44:		Line 44:

	[[Image:Wireshark_iograph3.png\|500px]]		[[Image:Wireshark_iograph3.png\|500px]]


			{{WiresharkFlag}}