Wireshark Trace File Reporting Using Excel

If you have ever opened a large Wireshark capture file and thought, “There has to be an easier way to see what is happening here,” you are not alone. A packet capture contains an incredible amount of information, but sometimes the packet list itself makes it difficult to visualize a problem. One technique I like to demonstrate is taking data from a Wireshark trace file and turning it into an Excel graph. Instead of scrolling through thousands of packets, you can transform the data into a simple visual representation that makes changes in packet rate, traffic volume, delays, or other measurements much easier to spot.

How to Configure a Cisco Router as a DHCP Server

When I'm building an isolated network for a class, lab, or troubleshooting exercise, one of the first things I need is a DHCP server. Manually configuring an IP address on every device works, but it quickly becomes tedious and introduces opportunities for duplicate addresses, incorrect subnet masks, or simple typing mistakes. DHCP is particularly useful when the network contains laptops, smartphones, tablets, wireless devices, or other equipment that may be connected temporarily. A Cisco router can handle this job without requiring a separate DHCP server, which makes it a convenient option for small networks and lab environments.

Grappling with Tech (Paul Smith)

 

It is sometimes said that we don’t choose technology, it chooses us. It is certainly possible to live in today’s world without a cell phone, a computer, or a car but it would require individuality and resolve. Whether you are an early adopter, a late-comer, or a total Luddite, sooner or later technology will hunt you down.

Which port is he on ??

 I run into this quite often where the client isn't sure which port the client is connected to.

In many cases, I do not have access to their network management system, or the network is down or worse, the documentation is dated and inaccurate. I think every network analyst should know how to do basic tasks like this one.

Wireshark Time Column: How to Use Packet Timing for Network Troubleshooting (Chris Greer)

Hey Packet People!

When troubleshooting a network problem with Wireshark, it is easy to concentrate on packet addresses, protocols, and conversations while overlooking one of the most useful pieces of information on the screen: time. The Time column can tell you much more than simply when a packet was captured. With the right configuration, it can help reveal delays, gaps in communication, retransmissions, and the sequence of events that led to a problem. If you are trying to understand why an application feels slow or why a TCP conversation is taking longer than expected, packet timing can be a very useful clue.