 | 1 | initial version |
You can do this with Wireshark in general. But as you talk about UDP traffic things are getting a little bit more complicated.
When you want to analyze at UDP traffic packet loss and jitter I recommend you to use special capture hardware with precise HW time stamping less than 100 microsec better less than 100 ns (If we talk about speeds >= 1 Gbit/s).
The easiest way is to do a multiple point capture and compare the number of captured packets and timings.
Harder approach: If you have to do it with a single point capture you need for determining packet loss in a UDP stream you a sequence number at application level to to see if a packet is missing. Or you can try to guess a packet loss by looking at the IP.ID or if the traffic it constantly by the timing of the packets, but this guessing approach is not pretty much reliable.
If you have considered this, you can capture your traffic and do somme analysis in Wireshark. - For example have a look at the delta time - IO Graph maximum delta and minimum delta - Analyze the (Application) Sequence Numbers, if present
Different approach: If you just want to proof the quality of your network, you can try an active measurement by some traffic generation tools like: perf, ostinato, flowgrind But here I also suggest some professional equipment to perform such tests.
| | 2 | No.2 Revision |
You can do this with Wireshark in general. But as you talk about UDP traffic things are getting a little bit more complicated.
When you want to analyze at UDP traffic packet loss and jitter I recommend you to use special capture hardware with precise HW time stamping less than 100 microsec better less than 100 ns (If we talk about speeds >= 1 Gbit/s).
The easiest way is to do a multiple point capture and compare the number of captured packets and timings.
Harder approach:
If you have to do it with a single point capture you need need, for determining packet loss in a an UDP stream you stream, a sequence number at application level to to see if a packet is missing. Or you can try to guess a packet loss by looking at the IP.ID or if the traffic it constantly when the traffic has a constant packet rate by the timing of the packets, but this guessing approach is not pretty much reliable.
If you have considered this, you can capture your traffic and do somme analysis in Wireshark. - For example have a look at the delta time - IO Graph maximum delta and minimum delta - Analyze the (Application) Sequence Numbers, if present
Different approach:
If you just want to proof the quality of your network, you can try an active measurement by some traffic generation tools like: perf, ostinato, flowgrind
But here I also suggest some professional equipment to perform such tests.
