434
edits
(pilot individual file) |
|||
Line 34: | Line 34: | ||
With only wireshark, we can now extract only some pilot(s), keep only a time interval of traffic, or see some traffic properties.<br> | With only wireshark, we can now extract only some pilot(s), keep only a time interval of traffic, or see some traffic properties.<br> | ||
With the help of tcpreplay/tcprewrite, we can sent the mp traffic back to a running FG session. | With the help of tcpreplay/tcprewrite, we can sent the mp traffic back to a running FG session. | ||
==pilot individual file== | |||
In Wireshark, it is possible to extract each pilot flight individually, the filter to use looks like: | |||
frame contains "callsign" | |||
and to exclude a pilot: | |||
!frame contains "callsign" | |||
This way you can have each pilot flight separated, and if needed, you can merge again 2 or more pilots in a file, eg you have recorded a diamond formation, and you want to practice the left wingman position, either you remove the existing one for the .cap, or you merge the 3 others again, after having done individual .cap.<br> | |||
Wireshark come with mergecap, to merge multiple .cap file, and taking care the chronological order is respected.<br> | |||
The provided editcap can be used too, if you need to add a time offset to a plane, to address latency recorded issue. | |||
It's sometimes difficult to have lot of matching shedules, when you are training in an aerobatic team, and we have here a good way to train with other mp pilots without being connected. You can even practice by file exchange, the leader make a flight, send the .cap to the second, wich add his flight, then pass to the 3 etc... | |||
==udp packets loss/jitter== | ==udp packets loss/jitter== |
edits