In my last two posts on this subject, I’ve covered some of the basics and
tools used to perform packet captures, highlighting the well known software
from Wireshark. In this installment, I’m going to show how I used Wireshark
packet captures to solve a real network problem.

Those of you wondering about the maximum throughput achieved in our Wireless Chart testing, can wonder no more. We’ve added a set of Maximum Throughput Benchmark charts to the current set of Average Throughput Charts. Just go to the Wireless Charts, and use the Select Benchmark dropdown to access the new charts. Enjoy!

If you’re looking for a cheap way to upgrade to draft 802.11n wireless and
want to do it the Linksys way, keep an eye peeled for sales.

We’ve learned that Linksys will be discontinuing its least-expensive WRT150N
when current inventory runs out. This will leave the WRT160N, which was
introduced in January as Linksys’ only entry-level draft 802.11n router.

SmallNetBuilder is fortunate to have a talented and faithful audience. Our best contributors have always come from our readers, and I’m always looking to tap that vast wealth of experience.

But good people also tend to be busy people who don’t have the hours that it takes to research and prepare they kind of in-depth articles and reviews that we do. On the other hand, you do have the time to visit SmallNetBuilder regularly and I’d like to have fresh stuff for you to read each time you visit.

Using packet papture software like Wireshark is a useful troubleshooting technique that can be used to examine packets and gather details to help find the root of a problem. In my previous post, I talked a little bit about how to use Wireshark and walked through some steps to run a simple packet capture from a PC. This time, I’m going to go a bit deeper into the how to for doing packet captures.