![]() Then (on the main menu) you can click on Statistics, then down to Flow Graph. In this case, I wanted to check the connection from start to finish, so I picked the first SYN packet. Firstly, you should locate the start of the connection. It is pretty simple to bring up the flow graph. The flow graph feature shows a sender and a receiver view of the packet flow. For this example, I used the filter ip.addr=192.168.250.102 and clicked Apply.įrom there, you can do the next trick, which is to look at the flow graph of a TCP connection. Once you filter on an IP address, you can then extract just the TCP packets directed to and from that IP address. It is necessary to extract the IP address of the sending host, otherwise you will get flooded with other packets that are not part of the specific connection you are checking. ![]() In this example, we confine ourselves to a small network with no packet loss to speak of. In a future post I will cover using the utilities tc and iptables to simulate packet loss. This capture is the same type of capture I used in the post “ Using jperf and Wireshark to troubleshoot network issues“. ![]() To begin with, I ran a jperf session between a client and a server and used Wireshark to capture the packets. ![]() This can assist you in seeing whether there are any issues on the network such as dropped frames, timeouts or dropped connections. This post is about another nice feature of Wireshark, namely, the flow graph. ![]() I posted a few weeks ago about using Wireshark to inspect packets on your network. Scott Reeves demonstrates the flow graph feature of the Wireshark tool, which can help you check connections between client server, finding timeouts, re-transmitted frames, or dropped connections. Using the flow graph feature on Wireshark ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |