Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
underdose said:
My results on same server with CISP 50/50 on Vuma:

7946862720.png


Obviously UL is sheit but little to no problem with the DL.
Also, why are we testing a single threaded connection? Can anyone remind me?
Click to expand...
If single thread is working, you don't need download accelerator etc, and single thread streams work a charm, just ask rain LTE.
 
Wasabee! said:
I agree that an OAN network (or respective ENNI) can be congested. This isn't always the fault of the OAN, as the ISP might not buy sufficient bandwidth on the OAN.

Actually it's very easy to see congestion, you just identify where your loss is. I don't mean to be rude, but the bold text I've highlighted shows me you are not very experienced with networks, again no offence. You don't need to do international speedtests, have a look at programs like WinMTR, MTR if on Linux, Pingplotter etc. They all identify loss which is a symptom of congestion.
Click to expand...
No offence taken. I have worked at an ISP at a much higher level than you know. I have a very good idea what I am talking about. It doesn't matter. You can have congestion without showing any packet loss. It makes it much harder to see where the congestion is. As an example. On your home network, max out the network on 2 pcs by copying files between them. Do a MTR, it will be 1 hop, but it will show 0% packet loss, even though you causing congestion.

So why am I not taking offence? Because I know most people don't really understand, including you.

I chose CISP as my isp brcause I know its the best ftth isp in sa. There is nothing wrong with their international, I use it every day without issue.
 
Tinuva said:
No offence taken. I have worked at an ISP at a much higher level than you know. I have a very good idea what I am talking about. It doesn't matter. You can have congestion without showing any packet loss. It makes it much harder to see where the congestion is. As an example. On your home network, max out the network on 2 pcs by copying files between them. Do a MTR, it will be 1 hop, but it will show 0% packet loss, even though you causing congestion.

So why am I not taking offence? Because I know most people don't really understand, including you.

I chose CISP as my isp brcause I know its the best ftth isp in sa. There is nothing wrong with their international, I use it every day without issue.
Click to expand...
I can agree with this 100% also coming from a higher level in a past ISP which was once great.

Cool ideas has a solid network, the issues are 90-99% of the time on these infrastructure providers side. I for one can watch twitch or do a international Speedtest anytime of the day and I will always get my 100Mbps.
 
Wasabee! said:
Well there is an easy way to find out if an end user doesn't know how to use or interpret a trace route.

If you don't have local issues ito loss, but have international issues, it's probably ISP. If the ISP tells you otherwise, imo they are lying.

If you have local issues ito loss aswell as have international issues, it could be your fibre provider which your ISP should resolve. A proper ISP has a good relationship with their suppliers and can work with them to resolve faults. The end user shouldn't have to know where the fault is as your commercial relationship is with the ISP.

So they should have some vendor management/relationship and resolve upstream issues whether it is their IPC (internet breakout) supplier or the layer 2 last mile provider like Vuma or Frogfoot.
Click to expand...

That there is what I am trying to ascertain.

Wasabee! said:
I agree that an OAN network (or respective ENNI) can be congested. This isn't always the fault of the OAN, as the ISP might not buy sufficient bandwidth on the OAN.

Actually it's very easy to see congestion, you just identify where your loss is. I don't mean to be rude, but the bold text I've highlighted shows me you are not very experienced with networks, again no offence. You don't need to do international speedtests, have a look at programs like WinMTR, MTR if on Linux, Pingplotter etc. They all identify loss which is a symptom of congestion.

Also fibre networks, especially GPON networks in SA due to their relative young age have so much spare capacity. That is on the access network. On distribution and transit on one cable you can have 144 fibres as an example. On each fibre you can multiplex with DWDM another few hundred channels ON EACH FIBRE. Each channel can be 100Gbps or more. So capacity on any good fibre network isn't a problem. Once again it comes down to design and commercials. Just like many ISPs save on international bandwidth, so to do they on OAN bandwidth. So often it might not be the fault that there isn't capacity available, the ISP might not want to buy more local capacity.

I'm not discrediting Cool Ideas, I'm just seeing a lot of people not be aware:

- That you can measure congestion with loss. Forget about slow speeds for now, first identify loss.
- How to identify loss (it seems everyone just likes to run speedtests).
- Based on where the loss is, what the probability of where the issue is (local or international).
- Then run speedtests after you have an idea where along the route the loss might be and use speedtests as another tool to confirm your assumption.

I'm not trying to make anyone look bad, I just want the correct party to take responsibility and not pass the buck by promoting or not correcting incorrect information.
Click to expand...
I agree.. I am trying to say the same thing... but the part highlighted in BOLD, is what p1sses me off, its a South African Business Mentality(TM).. I've seen it at many companies I've worked for and I detest it. It seems to be a sport in this country, to screw the customer over until he breaks and goes elsewhere.

I don't work with networks at these levels so excuse my ignroance. I never have, but I want to learn the ins-and-outs because maybe then, if we know what is going on we can take whomever is to blame, to task.

But yes, I see knowledgeable people in this thread. So here's the challenge. Show us how to prove who is to blame (I am starting to believe that CISP isn't to blame for these issues) and we will do the exercise and then, take the responsible party to task with the CPA or legal means
 
Wasabee! said:
1. Please explain how the open access network (OAN) is flaky?
Click to expand...

The ONT at my property does not like its ethernet port to be run at 100 or 10Mbps. If it is connected like that, I get very bad upload speeds, local or international, and packet loss. Connecting this same ONT to a Mikrotik, the issue goes away, because that unit has a Gigabit Ethernet port. It also seems to be a non-issue on a Routerboard with 10/100 ports. But I can assure you, using any other router I've tried (TP-LINK, Huawei, NETGEAR) the ONT runs packet loss and poor upload speeds on that Ethernet interface. I have tested this over and over and it does it, every single time so when I say that the ONT's firmware is crap I am sure about my facts.
 
Local:
1547185628570.png

International: :sick:
1547185708255.png

So in this scenario... how do I do tests to figure out where the problem lies? My thinking is since the local speed test is fine... it means my equipment and line to my house is OK?
 
ArtyLoop said:
So in this scenario... how do I do tests to figure out where the problem lies? My thinking is since the local speed test is fine... it means my equipment and line to my house is OK?
Click to expand...
Try these programs to local and international sites:

https://www.pingplotter.com/#

http://winmtr.net/

You can play around with the settings like changing to UDP/TCP, increasing transmission interval (more packets per second) etc.

If you really want to, you can order a second ISP on your fibre (assuming your ONT has multiple Ethernet access ports) and set that up as a second breakout. Then you can do A/B testing though that would be expensive as you have to duplicate your ISP costs just for testing.
 
Wasabee! said:
Try these programs to local and international sites:

https://www.pingplotter.com/#

http://winmtr.net/

You can play around with the settings like changing to UDP/TCP, increasing transmission interval (more packets per second) etc.

If you really want to, you can order a second ISP on your fibre (assuming your ONT has multiple Ethernet access ports) and set that up as a second breakout. Then you can do A/B testing though that would be expensive as you have to duplicate your ISP costs just for testing.
Click to expand...
I cannot do that, as I am on a tight budget and I am also on a sh1tty single port ONT

Secondly I don't have a Windows machine. What is the equivalent of WinMTR in Macintosh land?
 
Anyone experiencing slow and erratic download speeds on Xbox One? Trying to download a 7gb demo for over 3 hours now. The download maxes out at around 20 mb/s then drops down under 10 and then completely stops only to restart over and over again. A network test shows good results at around 90 mb/s, except between 7 and 11pm at night when it is below 10 mb/s. PlayStation 4 is fine as well as Netflix etc. Tried on 2 different routers.
Vuma 100/100 trenched. Edleen Kempton Park

Edit. Seemed to have fixed this by using dns 1.1.1.1 on the Xbox.
 
Last edited:
@PBCool : I logged a call yesterday regarding routing to Perth, no response as yet.

#COOL-20190110-198470
 
Today's iperf test results...

Microsoft Windows [Version 10.0.17763.253]
(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 51410 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.80 MBytes 15.1 Mbits/sec 0.617 ms 2290/2521 (91%)
[ 4] 1.00-2.00 sec 800 KBytes 6.56 Mbits/sec 0.472 ms 2342/2442 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.55 Mbits/sec 0.352 ms 2341/2441 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.56 Mbits/sec 0.380 ms 2342/2442 (96%)
[ 4] 4.00-5.00 sec 752 KBytes 6.16 Mbits/sec 0.547 ms 2347/2441 (96%)
[ 4] 5.00-6.00 sec 800 KBytes 6.55 Mbits/sec 0.617 ms 2341/2441 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.489 ms 2342/2442 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.55 Mbits/sec 0.584 ms 2341/2441 (96%)
[ 4] 8.00-9.00 sec 800 KBytes 6.55 Mbits/sec 0.623 ms 2342/2442 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.454 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.442 ms 23744/24885 (95%)
[ 4] Sent 24885 datagrams

iperf Done.

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 64456 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.473 ms 2282/2514 (91%)
[ 4] 1.00-2.00 sec 792 KBytes 6.49 Mbits/sec 0.667 ms 2342/2441 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.55 Mbits/sec 0.929 ms 2342/2442 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.55 Mbits/sec 0.527 ms 2341/2441 (96%)
[ 4] 4.00-5.00 sec 800 KBytes 6.56 Mbits/sec 0.252 ms 2342/2442 (96%)
[ 4] 5.00-6.00 sec 800 KBytes 6.55 Mbits/sec 0.452 ms 2341/2441 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.574 ms 2341/2441 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.56 Mbits/sec 0.495 ms 2342/2442 (96%)
[ 4] 8.00-9.00 sec 784 KBytes 6.41 Mbits/sec 0.686 ms 2343/2441 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.56 Mbits/sec 0.446 ms 2342/2442 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.662 ms 23756/24902 (95%)
[ 4] Sent 24902 datagrams

iperf Done.

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 49375 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.74 MBytes 14.6 Mbits/sec 0.504 ms 2306/2529 (91%)
[ 4] 1.00-2.00 sec 776 KBytes 6.36 Mbits/sec 0.912 ms 2319/2416 (96%)
[ 4] 2.00-3.00 sec 808 KBytes 6.61 Mbits/sec 0.594 ms 2365/2466 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.56 Mbits/sec 1.147 ms 2342/2442 (96%)
[ 4] 4.00-5.00 sec 800 KBytes 6.55 Mbits/sec 0.838 ms 2341/2441 (96%)
[ 4] 5.00-6.00 sec 792 KBytes 6.48 Mbits/sec 0.550 ms 2342/2441 (96%)
[ 4] 6.00-7.00 sec 792 KBytes 6.48 Mbits/sec 0.618 ms 2343/2442 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.56 Mbits/sec 0.864 ms 2341/2441 (96%)
[ 4] 8.00-9.00 sec 728 KBytes 5.96 Mbits/sec 0.710 ms 2327/2418 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.373 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.458 ms 23766/24892 (95%)
[ 4] Sent 24892 datagrams

iperf Done.

C:\WINDOWS\system32>
 
@Wasabee! What can you deduce from my iperf test results?

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

C:\WINDOWS\system32>iperf3.exe -R -u -b 160M -p 17001 -c trcvmh01.cisp.co.za
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
[ 4] local 192.168.1.105 port 56933 connected to 154.0.15.181 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.75 MBytes 14.7 Mbits/sec 0.802 ms 2309/2533 (91%)
[ 4] 1.00-2.00 sec 784 KBytes 6.42 Mbits/sec 0.826 ms 2322/2420 (96%)
[ 4] 2.00-3.00 sec 808 KBytes 6.62 Mbits/sec 0.383 ms 2362/2463 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.55 Mbits/sec 0.564 ms 2344/2444 (96%)
[ 4] 4.00-5.00 sec 792 KBytes 6.49 Mbits/sec 0.648 ms 2318/2417 (96%)
[ 4] 5.00-6.00 sec 808 KBytes 6.61 Mbits/sec 0.463 ms 2365/2466 (96%)
[ 4] 6.00-7.00 sec 784 KBytes 6.42 Mbits/sec 0.465 ms 2343/2441 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.56 Mbits/sec 0.446 ms 2342/2442 (96%)
[ 4] 8.00-9.00 sec 792 KBytes 6.48 Mbits/sec 0.604 ms 2342/2441 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.56 Mbits/sec 0.617 ms 2342/2442 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 192 MBytes 161 Mbits/sec 0.606 ms 23435/24557 (95%)
[ 4] Sent 24557 datagrams

iperf Done.

C:\WINDOWS\system32>iperf3.exe -R -u -b 160M -p 17001 -c lnms.cisp.co.za
Connecting to host lnms.cisp.co.za, port 17001
Reverse mode, remote host lnms.cisp.co.za is sending
[ 4] local 192.168.1.105 port 61785 connected to 154.0.1.254 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.80 MBytes 15.1 Mbits/sec 0.740 ms 2294/2525 (91%)
[ 4] 1.00-2.00 sec 776 KBytes 6.36 Mbits/sec 0.597 ms 2344/2441 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.56 Mbits/sec 0.896 ms 2343/2443 (96%)
[ 4] 3.00-4.00 sec 760 KBytes 6.23 Mbits/sec 1.420 ms 2345/2440 (96%)
[ 4] 4.00-5.00 sec 792 KBytes 6.48 Mbits/sec 0.964 ms 2343/2442 (96%)
[ 4] 5.00-6.00 sec 784 KBytes 6.42 Mbits/sec 0.592 ms 2343/2441 (96%)
[ 4] 6.00-7.00 sec 792 KBytes 6.49 Mbits/sec 0.981 ms 2343/2442 (96%)
[ 4] 7.00-8.00 sec 792 KBytes 6.49 Mbits/sec 0.707 ms 2342/2441 (96%)
[ 4] 8.00-9.00 sec 800 KBytes 6.55 Mbits/sec 0.576 ms 2342/2442 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.724 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 191 MBytes 161 Mbits/sec 0.724 ms 23380/24498 (95%)
[ 4] Sent 24498 datagrams

iperf Done.

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 51361 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.76 MBytes 14.7 Mbits/sec 0.532 ms 2282/2507 (91%)
[ 4] 1.00-2.00 sec 800 KBytes 6.55 Mbits/sec 0.617 ms 2341/2441 (96%)
[ 4] 2.00-3.00 sec 792 KBytes 6.49 Mbits/sec 0.515 ms 2343/2442 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.55 Mbits/sec 0.720 ms 2341/2441 (96%)
[ 4] 4.00-5.00 sec 800 KBytes 6.55 Mbits/sec 0.868 ms 2341/2441 (96%)
[ 4] 5.00-6.00 sec 792 KBytes 6.49 Mbits/sec 1.067 ms 2343/2442 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.702 ms 2341/2441 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.55 Mbits/sec 0.604 ms 2342/2442 (96%)
[ 4] 8.00-9.00 sec 808 KBytes 6.61 Mbits/sec 0.770 ms 2364/2465 (96%)
[ 4] 9.00-10.00 sec 792 KBytes 6.49 Mbits/sec 0.588 ms 2318/2417 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.527 ms 23754/24894 (95%)
[ 4] Sent 24894 datagrams

iperf Done.

C:\WINDOWS\system32>
 
sand_man said:
But 3 different destination servers and 3 consistently poor results, almost identical results? Isn't packet loss dynamic? Isn't it odd that the results are so consistent? @Wasabee! @ArtyLoop @PBCool @Tinuva
Click to expand...
Consistent packet loss in my limited experience with the likes of CrystalWeb and IS, and perhaps MWEB almost always is throttling/shaping!
 
For reference, Cape Town, Brackenfell, Vuma Trenched, 200/200

C:\iperf>iperf3.exe -R -u -b 160M -p 17001 -c trcvmh01.cisp.co.za
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
[ 4] local 192.168.88.252 port 55314 connected to 154.0.15.181 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 19.3 MBytes 162 Mbits/sec 0.163 ms 70/2538 (2.8%)
[ 4] 1.00-2.00 sec 19.1 MBytes 160 Mbits/sec 0.159 ms 0/2441 (0%)
[ 4] 2.00-3.00 sec 19.1 MBytes 160 Mbits/sec 0.167 ms 0/2440 (0%)
[ 4] 3.00-4.00 sec 19.1 MBytes 160 Mbits/sec 0.165 ms 0/2444 (0%)
[ 4] 4.00-5.00 sec 19.1 MBytes 160 Mbits/sec 0.144 ms 1/2441 (0.041%)
[ 4] 5.00-6.00 sec 19.1 MBytes 160 Mbits/sec 0.207 ms 0/2441 (0%)
[ 4] 6.00-7.00 sec 19.1 MBytes 160 Mbits/sec 0.211 ms 0/2441 (0%)
[ 4] 7.00-8.00 sec 19.1 MBytes 160 Mbits/sec 0.265 ms 0/2441 (0%)
[ 4] 8.00-9.00 sec 19.1 MBytes 160 Mbits/sec 0.114 ms 0/2442 (0%)
[ 4] 9.00-10.00 sec 19.1 MBytes 160 Mbits/sec 0.136 ms 0/2441 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 192 MBytes 161 Mbits/sec 0.140 ms 71/24513 (0.29%)
[ 4] Sent 24513 datagrams

iperf Done.

C:\iperf>iperf3.exe -R -u -b 160M -p 17001 -c lnms.cisp.co.za
Connecting to host lnms.cisp.co.za, port 17001
Reverse mode, remote host lnms.cisp.co.za is sending
[ 4] local 192.168.88.252 port 51128 connected to 154.0.1.254 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 19.3 MBytes 161 Mbits/sec 0.116 ms 70/2535 (2.8%)
[ 4] 1.00-2.00 sec 19.1 MBytes 160 Mbits/sec 0.105 ms 3/2443 (0.12%)
[ 4] 2.00-3.00 sec 19.0 MBytes 160 Mbits/sec 0.056 ms 3/2441 (0.12%)
[ 4] 3.00-4.00 sec 18.9 MBytes 159 Mbits/sec 0.086 ms 19/2441 (0.78%)
[ 4] 4.00-5.00 sec 19.0 MBytes 159 Mbits/sec 0.072 ms 9/2442 (0.37%)
[ 4] 5.00-6.00 sec 19.0 MBytes 159 Mbits/sec 0.108 ms 14/2440 (0.57%)
[ 4] 6.00-7.00 sec 18.9 MBytes 158 Mbits/sec 0.096 ms 25/2442 (1%)
[ 4] 7.00-8.00 sec 19.0 MBytes 160 Mbits/sec 0.099 ms 5/2442 (0.2%)
[ 4] 8.00-9.00 sec 19.0 MBytes 160 Mbits/sec 0.117 ms 3/2437 (0.12%)
[ 4] 9.00-10.00 sec 19.1 MBytes 160 Mbits/sec 0.107 ms 1/2441 (0.041%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 192 MBytes 161 Mbits/sec 0.136 ms 152/24558 (0.62%)
[ 4] Sent 24558 datagrams

iperf Done.

C:\iperf>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.88.252 port 49435 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 19.3 MBytes 162 Mbits/sec 0.093 ms 68/2536 (2.7%)
[ 4] 1.00-2.00 sec 19.1 MBytes 160 Mbits/sec 0.095 ms 2/2441 (0.082%)
[ 4] 2.00-3.00 sec 19.1 MBytes 160 Mbits/sec 0.140 ms 0/2442 (0%)
[ 4] 3.00-4.00 sec 19.1 MBytes 160 Mbits/sec 0.092 ms 0/2441 (0%)
[ 4] 4.00-5.00 sec 19.1 MBytes 160 Mbits/sec 0.090 ms 1/2442 (0.041%)
iperf3: OUT OF ORDER - incoming packet = 14243 and received packet = 14245 AND SP = 4
[ 4] 5.00-6.00 sec 19.1 MBytes 160 Mbits/sec 0.107 ms 2/2441 (0.082%)
[ 4] 6.00-7.00 sec 19.1 MBytes 160 Mbits/sec 0.097 ms 1/2441 (0.041%)
[ 4] 7.00-8.00 sec 19.1 MBytes 160 Mbits/sec 0.110 ms 0/2442 (0%)
[ 4] 8.00-9.00 sec 19.1 MBytes 160 Mbits/sec 0.082 ms 0/2441 (0%)
[ 4] 9.00-10.00 sec 19.1 MBytes 160 Mbits/sec 0.077 ms 0/2442 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 194 MBytes 163 Mbits/sec 0.194 ms 74/24862 (0.3%)
[ 4] Sent 24862 datagrams
[SUM] 0.0-10.0 sec 1 datagrams received out-of-order

iperf Done.
 
sand_man said:
Today's iperf test results...

Microsoft Windows [Version 10.0.17763.253]
(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 51410 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.80 MBytes 15.1 Mbits/sec 0.617 ms 2290/2521 (91%)
[ 4] 1.00-2.00 sec 800 KBytes 6.56 Mbits/sec 0.472 ms 2342/2442 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.55 Mbits/sec 0.352 ms 2341/2441 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.56 Mbits/sec 0.380 ms 2342/2442 (96%)
[ 4] 4.00-5.00 sec 752 KBytes 6.16 Mbits/sec 0.547 ms 2347/2441 (96%)
[ 4] 5.00-6.00 sec 800 KBytes 6.55 Mbits/sec 0.617 ms 2341/2441 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.489 ms 2342/2442 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.55 Mbits/sec 0.584 ms 2341/2441 (96%)
[ 4] 8.00-9.00 sec 800 KBytes 6.55 Mbits/sec 0.623 ms 2342/2442 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.454 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.442 ms 23744/24885 (95%)
[ 4] Sent 24885 datagrams

iperf Done.

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 64456 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.473 ms 2282/2514 (91%)
[ 4] 1.00-2.00 sec 792 KBytes 6.49 Mbits/sec 0.667 ms 2342/2441 (96%)
[ 4] 2.00-3.00 sec 800 KBytes 6.55 Mbits/sec 0.929 ms 2342/2442 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.55 Mbits/sec 0.527 ms 2341/2441 (96%)
[ 4] 4.00-5.00 sec 800 KBytes 6.56 Mbits/sec 0.252 ms 2342/2442 (96%)
[ 4] 5.00-6.00 sec 800 KBytes 6.55 Mbits/sec 0.452 ms 2341/2441 (96%)
[ 4] 6.00-7.00 sec 800 KBytes 6.55 Mbits/sec 0.574 ms 2341/2441 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.56 Mbits/sec 0.495 ms 2342/2442 (96%)
[ 4] 8.00-9.00 sec 784 KBytes 6.41 Mbits/sec 0.686 ms 2343/2441 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.56 Mbits/sec 0.446 ms 2342/2442 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.662 ms 23756/24902 (95%)
[ 4] Sent 24902 datagrams

iperf Done.

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 49375 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 1.74 MBytes 14.6 Mbits/sec 0.504 ms 2306/2529 (91%)
[ 4] 1.00-2.00 sec 776 KBytes 6.36 Mbits/sec 0.912 ms 2319/2416 (96%)
[ 4] 2.00-3.00 sec 808 KBytes 6.61 Mbits/sec 0.594 ms 2365/2466 (96%)
[ 4] 3.00-4.00 sec 800 KBytes 6.56 Mbits/sec 1.147 ms 2342/2442 (96%)
[ 4] 4.00-5.00 sec 800 KBytes 6.55 Mbits/sec 0.838 ms 2341/2441 (96%)
[ 4] 5.00-6.00 sec 792 KBytes 6.48 Mbits/sec 0.550 ms 2342/2441 (96%)
[ 4] 6.00-7.00 sec 792 KBytes 6.48 Mbits/sec 0.618 ms 2343/2442 (96%)
[ 4] 7.00-8.00 sec 800 KBytes 6.56 Mbits/sec 0.864 ms 2341/2441 (96%)
[ 4] 8.00-9.00 sec 728 KBytes 5.96 Mbits/sec 0.710 ms 2327/2418 (96%)
[ 4] 9.00-10.00 sec 800 KBytes 6.55 Mbits/sec 0.373 ms 2341/2441 (96%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 195 MBytes 163 Mbits/sec 0.458 ms 23766/24892 (95%)
[ 4] Sent 24892 datagrams

iperf Done.

C:\WINDOWS\system32>
Click to expand...
Lets start counting the days.
Tomorrow will look like Day xx results.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X