udp_flood test not working

[luisglass]

Have I misconfigured something here? I've setup a new netperf server and with the latest version of flent, and I'm not able to run the udp_flood test.

flent udp_flood -H netperf
Starting Flent 2.1.1+git using Python 3.12.3.
Starting udp_flood test. Expected run time: 70 seconds.
**ERROR: Parse error in IperfCsvRunner: list index out of range**
Data file written to ./udp_flood-2024-05-09T155614.839021.flent.gz

Summary of udp_flood test run from 2024-05-09 22:56:14.839021

                           avg       median       99th %          # data pts
 Ping (ms) ICMP :        72.57        72.70        73.90 ms              349

However, when I run the iperf client command directly, it appears to work:

iperf --enhanced --reportstyle C --format m --client netperf --time 30 --interval 0.2   --udp --bandwidth 100M
-0700:20240509154620.629,192.168.15.36,59746,x.x.x.x,5001,1,0.0-0.2,2623950,104957475,0.000,0,1785,0.000,0,1784,0,8927.633652  

Using this command on the server to listen:

iperf -s -i 1 -u
------------------------------------------------------------
Server listening on UDP port 5001
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  1] local 172.31.12.255 port 5001 connected with 50.46.240.224 port 59746
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  1] 0.0000-1.0000 sec  6.15 MBytes  51.6 Mbits/sec   0.206 ms 4319/8708 (50%)
[  1] 1.0000-2.0000 sec  9.54 MBytes  80.0 Mbits/sec   0.157 ms 2326/9128 (25%)
[  1] 2.0000-3.0000 sec  11.9 MBytes   100 Mbits/sec   0.171 ms 406/8917 (4.6%)

[tohojo]

luisglass ***@***.***> writes:

Have I misconfigured something here? I've setup a new netperf server and with the latest version of flent, and I'm not able to run the udp_flood test. ``` flent udp_flood -H netperf Starting Flent 2.1.1+git using Python 3.12.3. Starting udp_flood test. Expected run time: 70 seconds. **ERROR: Parse error in IperfCsvRunner: list index out of range**

Please attach a debug log for when this is happening (run with --log-file); what version of iperf are you using for this?