Custom transmit pattern

[GoogleCodeExporter]

Explaination of new feature:
Is there any way to implement a feature where iperf loops a 
pattern given in a file rather than just sending the file content once, as in 
Iperf2 with the "-F" option.

Justification of new feature
I'm working with systems that are able to compress packets and I believe this 
could be a useful feature of Iperf.

Original issue reported on code.google.com by rob...@gmail.com on 25 Mar 2011 at 2:05

[GoogleCodeExporter]

The current implementation uses random data.  However I can see the utility of 
being able to define a specific pattern.  This seems like a useful feature, but 
probably won't go in until 3.1.

Original comment by jdu...@es.net on 29 Mar 2011 at 12:56

• Added labels: Milestone-3.1a1

[GoogleCodeExporter]

Original comment by bltier...@es.net on 12 Mar 2013 at 10:48

[GoogleCodeExporter]

Now that we have the -F flag to send a specified file, this change may no 
longer be needed.  However there is one difference - -F stops the test after a 
single run through the file, while this one would rewind the file and send it 
again until the regular termination conditions are met.

Original comment by jef.posk...@gmail.com on 19 Oct 2013 at 2:50

[GoogleCodeExporter]

since the -F option takes care of this, closing this. Let us know if you 
disagree.

Original comment by bltier...@es.net on 18 Dec 2013 at 9:12

• Changed state: Fixed