Re: Question about UDP side of IPerf
Well I do not really have a workaround per say. First you must realize
that Iperf is designed to listen to either UDP or TCP traffic not BOTH.
Therefore you will need 2 processes running if you want to be able to test
both UDP and TCP throughput. However as you have noticed that is hard to
do since Iperf uses a service name of Iperf Service regardless if it is
UDP or TCP. The way to get this to work for you would be to modify the
service.h and service.c files in the src/ directory to have to different
names one for TCP and one for UDP. (eg Iperf UDP Service) This would allow
both services to be active at the same time with (potentially) different
options. If you can not compile the source yourself then let me know and I
can make the neccessary changes and recompile a special version by the end
of next week or so.
Kevin
On Tue, 17 Jun 2003 Andy.Ogan --at-- state.sd.us wrote:
> Greetings!
>
> After finding the IPerf software, I was excited as ever at the possibilities
> of this tool, but I've run into one snag... maybe someone has a
> workaround...
>
> What our plan for IPerf is is to install the IPerf software as a service in
> our Windows 2000/XP environment. Our Network Technologies staff can then
> use the software to test out the new backbone speeds, speeds to remote
> sites, and test links after users make the broad complaint of "everything is
> slow!" I have gotten the IPerf software to install as a service under the
> windows platform, made it Automatic at startup, and everything on the TCP
> side works great! UDP is a problem though...
>
> When attempting to complete the following command "iperf -c (dest. IP) -u" I
> get one of the following errors:
> read failed: Connection reset by peer
> or
> recvfrom failed: Interrupted function call.
>
> Sometimes both errors!
>
> If I go to the remote machine, stop all Iperf services, and start a service
> via iperf.exe -s -D -u, then UDP works, but of course, TCP does not.
>
> Now, when setting up the service under Windows, the only thing that will run
> is iperf.exe, no extra parameters afterwards. If I start the service
> manually, I can input those parameters, but when the service is set to
> automatic, it will not save those service parameters, and therefore the UDP
> side fails.
>
> What I am hoping for is that there is a way to start IPerf with both TCP and
> UDP (for jitter, very important to the project) running. The difficult part
> has been having this be completely automatic so that testing can be done
> with no input required by the remote end. Is there a way to have both TCP
> and UDP services running simultaneously under Windows with automatic
> startup?
>
> Thanks in advance!
>
>
>
>
> Andy Ogan
>
>
> Network Technologies
>
>
> State of South Dakota - BIT
>
>
> Pierre, South Dakota
>
>
>
>