Lines Matching refs:to
8 known bugs and issues. After spending some time trying to fix
11 tool as simple as possible, so others could contribute to the code
12 base. For this reason, it was decided to make the tool single
20 problems with iperf2, and added a number of new features similar to
35 …If you want to use multiple iperf3 streams use the method described `here <https://fasterdata.es.n…
37 I’m trying to use iperf3 on Windows, but having trouble. What should I do?
41 Some people are using Cygwin to run iperf3 in Windows, but not all
60 as of this writing, there do not appear to be any static
64 --disable-shared`` These options are necessary to disable the
67 --enable-static-bin`` is another, shorter way to accomplish
69 necessary to pass the ``--without-sctp`` flag at configure
75 the last two steps are needed to produce a static executable.
78 This problem has been noted by users attempting to build iperf3 for
81 effort to most effort:
85 the ``--enable-profiling`` flag to ``configure`` to build
89 passed to ``configure`` to disable the building of profiled
94 you are willing to accept the error exit from the make process
96 not need to do anything.
104 If you edit it to look like this, it will disable the build of the profiled iperf3::
108 #. Similar to item 2 above, but more permanent...if you edit
118 Makefiles to make the exclusion of the profiled iperf3 executable
124 3.1.5. Second, try adding the flag ``-w2M`` to increase the socket
125 buffer sizes. That seems to make a big difference on some hosts.
127 iperf3 UDP does not seem to work at bandwidths less than 100Kbps. Why?
128 …You'll need to reduce the default packet length to get UDP rates of less that 100Kbps. Try ``-l100…
130 TCP throughput drops to (almost) zero during a test, what's going on?
131 A drop in throughput to almost zero, except maybe for the first
132 reported interval(s), may be related to problems in NIC TCP Offload,
133 which is used to offload TCP functionality to the NIC (see
135 Offload is to save main CPU performance, mainly in the areas of
149 but since the packets don’t get to the server, no ack is received
152 packet by re-segmenting it, and in these cases data will get to the
157 The recommended solution in such a case is to disable TSO/LSO, at
171 * Reduce the sending length to a small value that should not require
173 may also help to reduce the MTU by using the iperf3 ``-M`` option,
177 ``-l`` value set to 2 times the MSS and then 4 times, 6 times,
179 reduced more. It may help to increase the testing time beyond the
180 default 10 seconds to better see the behavior (iperf3 ``-t``
184 On Linux, run this command to see the available congestion control
197 I'm using the --fq-rate flag, but it does not seem to be working. Why?
198 You need to add 'net.core.default_qdisc = fq' to /etc/sysctl.conf for that option to work.
200 I'm having trouble getting iperf3 to work on Windows, Android, etc. Where can I get help?
203 I managed to get a Windows executable built, but why do I get a BSOD on Windows 7?
204 There seems to be a bug in Windows 7 where running iperf3 from a
216 denial of service attack. We don't want iperf3 to be an attack tool.
218 I'm trying to use iperf3 to test a 40G/100G link...What do I need to know?
225 iperf3 uses a control connection between the client and server to
233 The ``-F`` option to iperf3 is not a file transfer utility. It's a
234 way of testing the end-to-end performance of a file transfer,
236 mimic an actual file transfer, the data stored to disk may not be
238 rounded up to the next larger multiple of the transfer block size,
243 I have a question regarding iperf3...what's the best way to get help?