#250 the extra parameter "-y c" seems wrong for Latency

[Lenny Yu]

Please see the attach picture.
When I used this command: iperf -u -s -i 1 -e -y C
we could see the output information with comma as the extra "-y C", like below:
iperf -u -s -i 1 -e -y C
+0800:20230331095741.076,10.70.9.247,63385,10.30.9.76,5001,1,0.0-1.0,498330,3986640,0.357,0,339,0.000,5,0,0,349.011392
+0800:20230331095742.076,10.70.9.247,63385,10.30.9.76,5001,1,1.0-2.0,499800,3998400,0.240,0,340,0.000,4,0,0,340.531911
+0800:20230331095743.076,10.70.9.247,63385,10.30.9.76,5001,1,2.0-3.0,501270,4010160,0.260,0,341,0.000,4,0,0,339.912281
+0800:20230331095744.076,10.70.9.247,63385,10.30.9.76,5001,1,3.0-4.0,499800,3998400,0.320,0,340,0.000,3,0,0,339.875266
+0800:20230331095745.076,10.70.9.247,63385,10.30.9.76,5001,1,4.0-5.0,498330,3986640,0.423,0,339,0.000,2,0,0,340.196471

Compare with the output without "-y C",
Latency avg/min/max/stdev mapping to 0.000,5,0,0 these four value, but why are they different?

[Robert McMahon]

Thanks for reporting this - let me look into it.

[Jean Tourrilhes]

This is the format for UDP
time,srcaddress,srcport,dstaddr,dstport,transferid,istart-iend,bytes,speed,jitter,errors,datagrams,errpercent,outoforder,writecnt,writeerr,pps

0.000,5,0,0

That's errpercent,outoforder,writecnt,writeerr. I agree that writecnt & writeerr are suspect, but writecnt & writeerr look normal.

Regards,

Jean