To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
Had to troubleshoot a slow WLAN/LAN. Telnet sessions from wireless clients to an AS400 were excruciatingly slow for the users. Needsless to say chapter 10 of this book was on the money. TCP retransmissions from both the wireless clients and two different servers show the problem to be near the wlan controller and/or Cisco WAN appliance. Great book to add to the toolbox.
Not only well written but the author goes into understandable detail about the "how's and why's" of the filters used and how to eventually get what you need out of the packets on virtually any OS.
Of all the tools available Wireshark is perhaps one of the best and multi-platform. Until you start to understand it, it's one gigantic maze but as you go through step by step and put it all together the puzzle will in the end come together for you. And you will have your "aha" moments too.
The structure of the book is very well laid out but you will need to have a fairly decent understanding of TCP/IP to really grasp the concept of what you'll be working with. I'd start there first and THEN work your way into understanding Wireshark afterwards.
This book is easy to follow along because the packet captures can be downloaded for free and viewed in Wireshark. This makes the book interactive as the reader can take closer looks at the packet captures referenced. A great resource for learning not just Wireshark but also basics of networking and cyber security.
I think this is a good book for a beginner or novice who would really benefit from examining some common use cases for traffic analysis. I feel the uses cases however are pretty simple and straight-forward and would not benefit a benefit a person who already has a year-plus of analysis under their belt. Don't expect this book to elaborate on the the protocol specifications for the protocols in the use cases. So if you are looking at a DNS example, understand how DNS works (via the RFC) before expecting to be able hit-the-ground running diagnosing DNS problems.