Ray Wang

Any update on this ticket, Bob? -Ray

Yes, it does even after 20 secs.

Client launched with UDP and -R hangs if server not running

Thanks. Once I synced the clock between the client and the server, the latency is showing some numbers instead of dashes. However with the isoch setting, there is still a large number of packets shown under miss/slip which seems a bit weird. I will file a ticket for investigation.

Thanks. After compiling the latest master, isochronous seems working and the output shows the expected result. There are two questions regarding the output: (1) Latency reported by the client shows dashes for avg/min/max/stdev. Is it expected? (2) As an example, when the following isochronous setting is used, large numbers of missed and slipped packets are reported on the server side. Are those numbers looking ok? --isochronous=148437:76m,0 (Here we assume packet size is 64 bytes, traffic load is...

Thanks. After compiling the latest master, isochronous seems working and the output shows the expected result. There are two questions regarding the output: (1) Latency reported by the client shows dashes for avg/min/max/stdev. Is it expected? (2) As an example, when the following isochronous setting is used, large numbers of missed and slipped packets are reported on the server side. Are those numbers looking ok? --isochronous=148437:76m,0 (Here we assume packet size is 64 bytes, traffic load is...

Thanks. After compiling the latest master, isochronous seems working and the output shows the expected result. There are two questions regarding the output: (1) Latency reported by the client shows dashes for avg/min/max/stdev. Is it expected? (2) As an example, when the following isochronous setting is used, large numbers of missed and slipped packets are reported on the server side. Are those numbers looking ok? --isochronous=148437:76m,0 (Here we assume packet size is 64 bytes, traffic load is...

iperf v2.1.4 issue with burst-period and burst-size for UDP