iperf used to work well for weeks (using Win 10 connected WiFi with AVM Fritz!Box 7590 router), but all of sudden it stopped working two days ago, for no apparent reason.
The problem is that iperf does not give me any hint on what could be wrong. I call it with the following command:
Client connecting to ###.###.###.###, TCP port 4711
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
[ 1] local ###.###.###.### port 49854 connected with ###.###.###.### port 4711
[ 1] tcp write failed
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-6.20 sec 11.7 GBytes 16.2 Gbits/sec
So I tried some things on my own: restarted router, computer, checked firewall, virus scanner, router settings ... but without success.
How can I get more information about the reason for the tcp write fail?
(I wonder that iperf does not output any error details, such as e.g. a timeout or something like that. Instead, it seems to continue and outputs ridiculous high transfer rates whic are far beyond the physical possibilities of my system. Is that intended behaviour or a bug?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
iperf used to work well for weeks (using Win 10 connected WiFi with AVM Fritz!Box 7590 router), but all of sudden it stopped working two days ago, for no apparent reason.
The problem is that iperf does not give me any hint on what could be wrong. I call it with the following command:
And here's the output:
So I tried some things on my own: restarted router, computer, checked firewall, virus scanner, router settings ... but without success.
How can I get more information about the reason for the tcp write fail?
(I wonder that iperf does not output any error details, such as e.g. a timeout or something like that. Instead, it seems to continue and outputs ridiculous high transfer rates whic are far beyond the physical possibilities of my system. Is that intended behaviour or a bug?)
Can you file a ticket for this? Iperf should pr int the error code but it currently doesn't.