qinhan620 / iperf

Automatically exported from code.google.com/p/iperf
0 stars 0 forks source link

using --server and --udp gives parameter error #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. iperf3 -s -u
2.
3.

What is the expected output? What do you see instead?
crotwell$ bin/iperf3 -s -u
parameter error: Some option you are trying to set is client only

What version of the product are you using? On what operating system?
3.0b4
linux

Please provide any additional information below.
Same problem with variations on --server and --udp

Docs seem to indicate that -u can be used with -s

Original issue reported on code.google.com by pcrotw...@gmail.com on 31 Aug 2010 at 8:27

GoogleCodeExporter commented 8 years ago
The -u flag isn't needed on the server end with iperf3.  The client negotiates 
with the server to determine UDP or TCP testing.  Probably this should just 
generate a warning rather than an error.

Action item for developers: make this a warning instead of an error and clarify 
man page.

Original comment by jdugan.e...@gmail.com on 1 Sep 2010 at 1:11

GoogleCodeExporter commented 8 years ago
Makes sense to me.

Original comment by richih.m...@gmail.com on 8 Apr 2011 at 10:25

GoogleCodeExporter commented 8 years ago

Original comment by jdu...@es.net on 10 Sep 2012 at 4:32

GoogleCodeExporter commented 8 years ago

Original comment by bltier...@es.net on 24 Feb 2013 at 3:25

GoogleCodeExporter commented 8 years ago
I don't actually agree that this should be a warning, it should be an error 
like all theother bad combinations of parameters. Perhaps with improved wording.

But as it stands, it is a warning now so I'm marking this Fixed.

Original comment by jef.posk...@gmail.com on 12 Mar 2013 at 8:00

GoogleCodeExporter commented 8 years ago
This is still broken though, if attempting to test with multicast (can't get -s 
and -u simultaneously)

Original comment by The.Jame...@gmail.com on 30 Jul 2015 at 6:47