Hey Vignesh,
On Jul 17, 2012, at 4:59 AM, vignesh venkateswaran wrote:
> I tried your suggestion. I guess you are right. This was the output when I
> added -i 2 to the client side command.
>
> root@OpenWrt:/# iperf -c 192.168.1.20 -i 2 -o root/tcp.txt
> ---
I tried your suggestion. I guess you are right. This was the output when I
added -i 2 to the client side command.
root@OpenWrt:/# iperf -c 192.168.1.20 -i 2 -o root/tcp.txt
Client connecting to 192.168.1.20, TCP port 5001
TCP window size
I tried your suggestion. I guess you are right. This was the output when I
added -i 2 to the client side command.
root@OpenWrt:/# iperf -c 192.168.1.20 -i 2 -o root/tcp.txt
Client connecting to 192.168.1.20, TCP port 5001
TCP window size
Hi Vignesh,
The way iperf works is the client makes a tcp connection to the server, and
sends 10 seconds worth of data. However, the client-side kernel is buffering
that data up, and sending it, and, in the case of loss, resending it. If you
have a very lossy connection, it may take far more th
I am using Iperf 2.0.4 on linux 2.6.32.10 loaded in two Mikrotik
Routerboards 411AR.
I tried to run iperf in these two boards through serial connections from
the
boards to my laptop via minicom and measure the 802.11 performance.
When I run iperf tcp test setting one board as server and another as
