This usually shows up as slow application performance and/or packet loss to the user _update – this will graph the size of the TCP window throughout your transfer. A few retransmissions are OK, excessive retransmissions are bad. A high number of duplicate ACKs is a sign of possible high latency between TCP endpoints – Displays all retransmissions in the capture. Packet loss can lead to duplicate ACKs, which leads to retransmissions _ack – displays packets that were acknowledged more than one time. _segment – Indicates we’ve seen a gap in sequence numbers in the capture. Here are some filters that are commonly used. You can always apply common troubleshooting filters to troubleshoot slow downloads/uploads or other application type problems. Its mostly useful for troubleshooting seeing spikes and dips in your traffic, btw, to look into the traffic closer you can click on any point on the graph and it will focus on that packet and display the information in the background packet list window. In default the x-axis is the tick interval per second, and y-axis is the packets per tick (per second). Wireshark IO Graphs will show you the overall traffic seen in a capture file which is usually measured in rate per second in bytes or packets (which you can always change if you prefer bits/bytes per second).
0 kommentar(er)
