QA Cafe has launched a new free online service for viewing packet sniffer capture files.
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.
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.
One of the features I've seen in newer small network routers is the inclusion of a packet sniffer/capture/trace tool within the diagnostic menus of the device. Routers I've recently tested with this functionality include the SonicWall TZ190W, D-Link DFLCPG310, and Netgear's newly released FVX538 and FVS336G.
In each case, these devices have the ability to capture packets on a specific WAN port and/or on the LAN interface. Some of these routers have more sophisticated filtering capabilities than the other, but they all seem to have the same basic functionality of capturing packets.
Updated - Our first look at the performance of NETGEAR's RAX80 and ASUS' RT-AX88U shows little benefit functioning as AC routers.
Updated: The first draft 11ax routers are almost here. Take a little time to know what you might be buying into.
Updated - 160 MHz channel bandwidth is an essential feature of 802.11ax. We take a look at whether it means trouble for your 11ac network.
Ever wonder what happens behind the scenes when Wi-Fi devices roam, or more likely don't? We'll show you why the "seamless" roaming Wi-Fi gear makers promise is still as elusive as a Yeti.
