434
edits
Howto:Record, analyze and replay multiplayer flights with network tools: Difference between revisions
Jump to navigation
Jump to search
Howto:Record, analyze and replay multiplayer flights with network tools (view source)
Revision as of 18:47, 25 March 2020
, 25 March 2020→tcprewrite magic: added core affinity and nice to the replay
m (Hooray moved page Howto:Record, analyze and replay flights with network tools to Howto:Record, analyze and replay multiplayer flights with network tools: this is multiplayer specific, right ?) |
(→tcprewrite magic: added core affinity and nice to the replay) |
||
| Line 97: | Line 97: | ||
Be sure to use the correct name for the network interface. ifconfig/ipconfig is your friend here! | Be sure to use the correct name for the network interface. ifconfig/ipconfig is your friend here! | ||
Tcpreplay works fine this way if we don't need a very good time flow sync, as it end being late, dépending on the cpu usage mostly. I didn't notice this issue at first, but this became evident using lag statistics available recently in next, so to keep a good sync between tcpreplay and flightgear, using a core affinity, setting a priority higher and preferably on a not overloaded PC/CPU core makes things better, so we got something like that on linux: | |||
taskset 02 nice -n -15 tcpreplay -x 1.000065 -K -i enp0s10 /rab/refuel/test.pcapng | |||
The "-x" option ensure a good time sync over the replay (find yourself the best value for your config :) ), i just need to adjust the time offset for the mp clock, to have replayed planes in sync with my session, considered as "real time" buddys. | |||
=== Give it a try === | === Give it a try === | ||