Status
Not open for further replies.
Almost 3 months now....

Microsoft Windows [Version 10.0.17763.195]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>iperf3.exe -R -u -b 160M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.1.105 port 57473 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.81 MBytes 15.2 Mbits/sec 0.231 ms 2292/2524 (91%)
[ 4] 1.00-2.00 sec 792 KBytes 6.49 Mbits/sec 0.262 ms 2342/2441 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.55 Mbits/sec 0.154 ms 2342/2442 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.56 Mbits/sec 0.114 ms 2341/2441 (96%)
[ 4] 4.00-5.00 sec 792 KBytes 6.49 Mbits/sec 0.272 ms 2342/2441 (96%)
[ 4] 5.00-6.00 sec 800 KBytes 6.55 Mbits/sec 0.221 ms 2342/2442 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.390 ms 2341/2441 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.55 Mbits/sec 0.938 ms 2342/2442 (96%)
[ 4] 8.00-9.00 sec 800 KBytes 6.56 Mbits/sec 0.352 ms 2341/2441 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.243 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.439 ms 23741/24887 (95%)
[ 4] Sent 24887 datagrams

iperf Done.

C:\WINDOWS\system32>iperf3.exe -u -b 160M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
[ 4] local 192.168.1.105 port 57808 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 18.3 MBytes 153 Mbits/sec 2337
[ 4] 1.00-2.00 sec 19.0 MBytes 160 Mbits/sec 2437
[ 4] 2.00-3.00 sec 19.2 MBytes 161 Mbits/sec 2461
[ 4] 3.00-4.00 sec 18.8 MBytes 158 Mbits/sec 2405
[ 4] 4.00-5.00 sec 19.1 MBytes 160 Mbits/sec 2439
[ 4] 5.00-6.00 sec 19.2 MBytes 161 Mbits/sec 2459
[ 4] 6.00-7.00 sec 18.9 MBytes 158 Mbits/sec 2418
[ 4] 7.00-8.00 sec 19.4 MBytes 163 Mbits/sec 2483
[ 4] 8.00-9.00 sec 18.7 MBytes 157 Mbits/sec 2399
[ 4] 9.00-10.00 sec 19.7 MBytes 165 Mbits/sec 2523
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 190 MBytes 160 Mbits/sec 1.088 ms 21121/24351 (87%)
[ 4] Sent 24351 datagrams

iperf Done.

C:\WINDOWS\system32>iperf3.exe -R -b 160M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.1.105 port 59654 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 827 KBytes 6.77 Mbits/sec
[ 4] 1.00-2.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 2.00-3.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 3.00-4.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 4.00-5.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 5.00-6.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 6.00-7.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 7.00-8.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 8.00-9.00 sec 1.20 MBytes 10.1 Mbits/sec
[ 4] 9.00-10.00 sec 1.20 MBytes 10.1 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 13.0 MBytes 10.9 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 11.9 MBytes 9.97 Mbits/sec receiver

iperf Done.

C:\WINDOWS\system32>iperf3.exe -b 160M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
[ 4] local 192.168.1.105 port 59672 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 384 KBytes 3.15 Mbits/sec
[ 4] 1.00-2.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 2.00-3.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 3.00-4.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 4.00-5.00 sec 1.25 MBytes 10.5 Mbits/sec
[ 4] 5.00-6.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 6.00-7.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 7.00-8.00 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 8.00-9.00 sec 1.25 MBytes 10.5 Mbits/sec
[ 4] 9.00-10.00 sec 1.50 MBytes 12.6 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 13.4 MBytes 11.2 Mbits/sec sender
[ 4] 0.00-10.00 sec 13.4 MBytes 11.2 Mbits/sec receiver

iperf Done.

C:\WINDOWS\system32>
Disgusting.
EDIT: Network is Vuma hey?
 
Yeah, look the iperf packet loss doesn't reflect real world performance so I'm not too bothered. If it was accurate my line would be totally unusable?
I was talking about a lack of an answer for 3 months, what if you had a real problem?
 
What's the point of an iperf test then?

That is the new question.

Hopefully this one doesn't get ignored until it goes away.
iperf is UDP packet testing correct?
Because even on a perfectly performing line there is loss and issues (my results looked the same as if I was using Telkom LTE).

I am willing to dig deeper, to answer your question truthfully.
 
iperf is UDP packet testing correct?
Because even on a perfectly performing line there is loss and issues (my results looked the same as if I was using Telkom LTE).

I am willing to dig deeper, to answer your question truthfully.
I'm pretty sure my results are false though! I consistently get the same result! And by same I mean almost identical!!
 
You lucky , my frogfoot international single thread download speed issue is at 6 months end of this month. Still only answer I get is we are waiting for a response from frogfoot...
 
I will do an indepth bit of personal research about what iperf does because at this point I am not knowledgeable
Just to get you started

It's a simple, yet powerful tool that can provide visibility on network performance metrics such as bandwidth, latency (delay), jitter, and packet loss. ... When testingbandwidth performance with Iperf, what we're actually testing is maximum TCP bandwidth at the transport layer (L4).
 
You lucky , my frogfoot international single thread download speed issue is at 6 months end of this month. Still only answer I get is we are waiting for a response from frogfoot...
So we have escalated this as far as the CTO now, so we are working on changing our NNI to start with from there we will work backwards. I appreciate the patience as this is super frustrating as the customer as well as the provider I assure you.
 
This is the problem.

The customer has no way of chasing the network provider, we can't even phone them.

Great way for no-one to own the problem.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X