On 06/03/2015 11:55 PM, Petter Adsen wrote:
On Wed, 03 Jun 2015 09:41:49 -0700
Gary Roach <gary719_li...@verizon.net> wrote:
On 05/25/2015 11:16 PM, Petter Adsen wrote:
iperf will use either TCP or UDP. :)
Petter
Well, I'm back
I used iperf3 as follows:
iperf3 -c iperf.scottlinux.com
The program just hangs. I also tried it with the -R switch with the same
result. I then set up one the other computers on my internal net as a
server (iperf3 -s) and got the following results:
<snip>
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 1.02 GBytes 878 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 1.02 GBytes 877 Mbits/sec
receiver
iperf Done.
My local network seems to be working fine (I tried the -R switch as
well. Same good results). Needless to say, I'm using a 100 Mbyte/second
network.
Seems good.
I am behind a verizon M1424WR rev. I router firewall that has been free
of any "known" transmission trouble before. Could the firewall be the
problem or has scottlinux.com shut down their iperf3 server.
Well, it's not shut down, as I just tried it and it works fine here.
Maybe it was down, though, and you should try again?
If it still doesn't work, then check your firewall. It shouldn't give
you any problems, as you are simply trying to establish a connection to
port 5201 on a remote machine, but check. Enable firewall logging, if
possible, and see if anything gets blocked. Verify that you can reach
the webserver running on the same host.
Also try with UDP ("-u -b 0").
Petter
Well all of a sudden iperf.scottlinux.com works The send and receive
with TCP packets is about the same. Below is a typical example:
root@xxxxxxxxxx# iperf3 -c iperf.scottlinux.com -R -V
iperf 3.0.7
Linux xxxxxxxxxx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1
(2015-04-24) x86_64 GNU/Linux
Time: Thu, 04 Jun 2015 23:42:13 GMT
Connecting to host iperf.scottlinux.com, port 5201
Reverse mode, remote host iperf.scottlinux.com is sending
Cookie: xxxxxxxxxx.1433461333.668186.036751
TCP MSS: 1448 (default)
[ 4] local 192.168.1.7 port 49461 connected to 173.230.156.66 port 5201
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0
seconds, 10 second test
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 3.20 MBytes 26.8 Mbits/sec
[ 4] 1.00-2.00 sec 3.24 MBytes 27.2 Mbits/sec
[ 4] 2.00-3.00 sec 3.22 MBytes 27.0 Mbits/sec
[ 4] 3.00-4.00 sec 3.23 MBytes 27.1 Mbits/sec
[ 4] 4.00-5.00 sec 3.22 MBytes 27.0 Mbits/sec
[ 4] 5.00-6.00 sec 3.16 MBytes 26.5 Mbits/sec
[ 4] 6.00-7.00 sec 3.21 MBytes 26.9 Mbits/sec
[ 4] 7.00-8.00 sec 3.20 MBytes 26.8 Mbits/sec
[ 4] 8.00-9.00 sec 3.23 MBytes 27.1 Mbits/sec
[ 4] 9.00-10.00 sec 3.22 MBytes 27.0 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 32.4 MBytes 27.2 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 32.2 MBytes 27.0 Mbits/sec
receiver
CPU Utilization: local/receiver 3.8% (0.6%u/3.2%s), remote/sender 0.1%
(0.0%u/0.1%s)
iperf Done.
As you can see, I'm getting about half of the 50Mbits/sec for which I
contracted. But this is way better than my actual speed. I ran the same
test with udp packets and got:
root@xxxxxxx# iperf3 -c iperf.scottlinux.com -R -u -V
iperf 3.0.7
Linux xxxxxxxxx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1
(2015-04-24) x86_64 GNU/Linux
Time: Thu, 04 Jun 2015 23:35:07 GMT
Connecting to host iperf.scottlinux.com, port 5201
Reverse mode, remote host iperf.scottlinux.com is sending
Cookie: xxxxxxxxxx.1433460907.576325.688abe
[ 4] local 192.168.1.7 port 60092 connected to 173.230.156.66 port 5201
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 0
seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total
Datagrams
[ 4] 0.00-1.00 sec 136 KBytes 1.11 Mbits/sec 1.587 ms 0/17 (0%)
[ 4] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 0.902 ms 0/16 (0%)
[ 4] 2.00-3.00 sec 128 KBytes 1.05 Mbits/sec 0.650 ms 0/16 (0%)
[ 4] 3.00-4.00 sec 128 KBytes 1.05 Mbits/sec 0.565 ms 0/16 (0%)
[ 4] 4.00-5.00 sec 128 KBytes 1.05 Mbits/sec 0.533 ms 0/16 (0%)
[ 4] 5.00-6.00 sec 128 KBytes 1.05 Mbits/sec 0.598 ms 0/16 (0%)
[ 4] 6.00-7.00 sec 128 KBytes 1.05 Mbits/sec 0.580 ms 0/16 (0%)
[ 4] 7.00-8.00 sec 128 KBytes 1.05 Mbits/sec 0.577 ms 0/16 (0%)
[ 4] 8.00-9.00 sec 128 KBytes 1.05 Mbits/sec 0.774 ms 0/16 (0%)
[ 4] 9.00-10.00 sec 128 KBytes 1.05 Mbits/sec 0.660 ms 0/16 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total
Datagrams
[ 4] 0.00-10.00 sec 1.26 MBytes 1.06 Mbits/sec 0.660 ms 0/161 (0%)
[ 4] Sent 161 datagrams
CPU Utilization: local/receiver 0.3% (0.0%u/0.3%s), remote/sender 0.1%
(0.0%u/0.1%s)
iperf Done.
Now I'm really confused. I thought UDP packets were going through at
full speed and TCP plackets were slow. This data says just the opposite.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5570e2f5.7010...@verizon.net
