It sorta makes sense but not sure. My answers are from an iperf 2 perspective.
Currently, there is no way from the command line to add a header to the UDP payload. It would have to be done in source code or by something like linux tc or ip tables. The iperf client doesn't require an iperf server for it to send packets. It just needs arp to be resolved. So a VB can receive traffic from client (or transmit) only. Yes, I think you can get the measurements from the second computer assuming the packet payload has what's expected for it to make the computations. Bob On Fri, Jun 7, 2019 at 9:22 AM Christian Sánchez <crisanc...@gmail.com> wrote: > Hi, > Probably the topic is not very helpful...Let me explain my situation in > more detail: I need to modify the UDP payload generated by Iperf, so I can > add an additional header to it. My idea is to run an Iperf client in a > computer, and use this client to send traffic to a virtual box in the same > computer. In the virtual box I would be running a script using a raw socket > to receive the data. After receiving it, and adding the header, I send it > to another Iperf server (in another computer), which would receive the data > after having removed the header. > My questions: > I don't have a clear understanding of the working details of Iperf, does > what I have explained above make sense at all to you? > Can I expect to get traffic in the VB from the client even when I'm not > running any server in the VB? > If by any chance I finally get traffic in the second computer, can I > expect it to perform correct measures from the traffic generated by the > client? > > Cheers > Christian > _______________________________________________ > Iperf-users mailing list > Iperf-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/iperf-users >
_______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
