在Windows网络上测量字节流量

与Wireshark这样的数据包嗅探器可以做的最有用的事情之一是了解谁以及谁负责网络在网络上的通信流量的份额。您可能有兴趣了解哪些计算机似乎始于更多的流量。您可能希望测试某些过程和用户​​操作以了解带宽方面的更“昂贵”。（例如，我有点惊讶地看到我自己的网络，即在网络共享上导航到一个关于2000个SMB数据包的网络共享的简单行为。）有几种技术对于这种东西方便，和they’re both on the Wireshark “Statistics” menu. First, start a capture so that you have some data to work on, then stop it and choose Statistics > Summary. The resulting dialog box gives you relevant capture details in the top half and some useful performance details in the bottom half, such as the average packet size, average number of packets per second, and average bytes per second (or Mbits if you prefer). With appropriate capture filters, this kind of information can help you see firsthand the network impact of user actions such as opening a share, copying a file over the network, opening an intranet or Internet page, and so forth. You can then take information like that and use it for capacity planning, network performance optimization, baselining, and troubleshooting. Another item on the Statistics menu is “Conversations.” The dialog box comes up by default to the Ethernet tab, but if you’re interested in where network traffic is being generated on your LAN, click the IPv4 tab and view the byte traffic by conversations between IP addresses. You can click the “Bytes” column heading to sort the report so that the largest bandwidth conversations appear at the top. The “Bytes A -> B” and “Bytes A<-B” headings show bandwidth usage by direction. To save yourself some NSLOOKUP queries, make sure that your Wireshark capture options include the “Enable network name resolution” flag so that you can see hostnames in place of IP addresses when viewing the conversations traffic report. Then, stroll over to the top bandwidth users and politely ask them to stop using your corporate file servers to back up their MP3 collections! Play around with these statistics screens after performing some typical operations on your own network. You might be surprised how much traffic seemingly simple operations can generate. And you might be surprised at who the bandwidth hogs are!