Need a real fix to incorrect write error codes
A means to measure network responsiveness and throughput
Brought to you by:
rjmcmahon
Per the error below did this commit. Needs a proper fix.
rjmcmahon@rpi5-34:/usr/local/src/iperf2-code $ iperf -c 10.19.85.66 -i 1 -e -w 4M
------------------------------------------------------------
Client connecting to 10.19.85.66, TCP port 5001 with pid 70749 (1/0 flows/load)
Write buffer size: 131072 Byte
TCP congestion control using cubic
TOS defaults to 0x0 (dscp=0,ecn=0) (Nagle on)
TCP window size: 8.00 MByte (WARNING: requested 4.00 MByte)
------------------------------------------------------------
[ 1] local 10.19.85.56%eth1 port 35730 connected with 10.19.85.66 port 5001 (icwnd/mss/irtt=14/1448/276) (ct=0.31 ms) on 2025-03-13 14:17:12.595 (PDT)
[ ID] Interval Transfer Bandwidth Write/Err Rtry InF(pkts)/Cwnd(pkts)/RTT(var) NetPwr
[ 1] 0.00-1.00 sec 238 MBytes 2.00 Gbits/sec 1906/0 0 475K(336)/719K(509)/2047(22) us 121980
[ 1] 1.00-2.00 sec 232 MBytes 1.95 Gbits/sec 1859/0 10 431K(305)/562K(398)/1830(43) us 133149
Program error: invalid client packet->err_readwrite 0
[ 1] 2.00-3.00 sec 232 MBytes 1.95 Gbits/sec 1858/0 8 412K(292)/499K(353)/1801(54) us 135220
[ 1] 3.00-4.00 sec 232 MBytes 1.95 Gbits/sec 1860/0 0 393K(278)/514K(364)/1890(14) us 128991
[ 1] 4.00-5.00 sec 230 MBytes 1.93 Gbits/sec 1840/0 0 417K(295)/530K(375)/1796(19) us 134283
[ 1] 5.00-6.00 sec 233 MBytes 1.95 Gbits/sec 1863/0 8 381K(270)/501K(355)/1789(34) us 136494