There have been more than a few times where I had to illustrate that ARP was an issue.
When a suspected ARP issue, or you just need to understand how often a device ARP’s, or you need a good challenge when using your favorite packet analyzer, this is a great exercise.
There are many things you can do to improve DNS performance. One of the more common techniques is to configure a device as a local DNS server, cache or relay for those scenarios where you might have slow/high latency internet connections.
Back in the day when we had hard drives with limited disk space and we needed to capture for long periods of time, we used packet slicing.
Packet slicing in Wireshark is one of those features that doesn’t get much love, but once you use it, you wonder how you ever captured packets without it. The basic idea is simple: instead of grabbing the entire packet payload, you only capture the first N bytes. For many troubleshooting and analysis tasks, that’s more than enough to see headers, flags, and protocol behavior without hauling around a ton of unnecessary data.
My wife and I recently joined some of the last homeowners to contribute to the $11 billion robot vacuum industry. Since I am usually the one who does the vacuuming, I liked the idea of completing this chore with the simple push of a button. It was an exciting day when I took our new Roomba out of the box, placed it on it’s little charging dock (which we located in the laundry room for our convenience), and then stood back and pressed “Clean” on my iPhone app.
In past articles I covered how to search for HTTP login credentials. After some feedback, I wanted to cover another approach used to find login credentials. Just want to start with a simple statement.
