Web Squad ISP

Status
Not open for further replies.
websquadza said:
Not that easy, if something your side is causing TCP retransmits, your speed will be inversely proportional to the distance (latency). Basically, the higher the latency, the lower your speed. TCP always performs slower with higher latency, that's expected. Add packet loss or retransmits, and you have an exponential degradation of the line (like we're seeing here). Think of it this way - if every TCP packet needs an acknowledgement - at <3ms, the retransmits are barely visible. At 20ms, they start becoming noticeable and at 150ms- good luck.

This can be caused by TCP issues in your environment (even faulty drivers), a bad NIC, a bad router, a bad line (though you don't show immediate loss on your MTRs - there may still be an issue (which is why iperfs exist).

Getting FNOs to admit issues is like pulling a needle through your eye. So first start by eliminating everything local: NIC and PC: test another PC. Router: bypass and test to CPE. Swap cables etc.

It's not present on the rest of the network, so it's not AEX or NNI.

JHB NAP Iperf: iperf3 -4 -V -t 10 -O 3 -u -b 180M -l 1440 -c iperf.jb1.napafrica.net
CPT NAP Iperf: iperf3 -4 -V -t 10 -O 3 -u -b 180M -l 1440 -c iperf.ct1.napafrica.net

It's also worth whipping out wireshark and monitoring your lan interface for any TCP issues (usually quite quick and easy to pick up issues that way).
Click to expand...


JHB
CYGWIN_NT-10.0 IvanPC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Wed, 03 Jun 2020 17:35:17 GMT
Connecting to host iperf.jb1.napafrica.net, port 5201
Cookie: IvanPC.1591205717.179098.611f1a98719
[ 4] local 192.168.5.66 port 53199 connected to 196.10.98.214 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 20.1 MBytes 169 Mbits/sec 14643 (omitted)
[ 4] 1.00-2.00 sec 21.5 MBytes 180 Mbits/sec 15644 (omitted)
[ 4] 2.00-3.00 sec 21.5 MBytes 180 Mbits/sec 15636 (omitted)
[ 4] 0.00-1.00 sec 21.5 MBytes 180 Mbits/sec 15633
[ 4] 1.00-2.00 sec 22.8 MBytes 191 Mbits/sec 16578
[ 4] 2.00-3.00 sec 20.1 MBytes 169 Mbits/sec 14639
[ 4] 3.00-4.00 sec 21.4 MBytes 180 Mbits/sec 15618
[ 4] 4.00-5.00 sec 21.4 MBytes 180 Mbits/sec 15604
[ 4] 5.00-6.00 sec 21.6 MBytes 181 Mbits/sec 15728
[ 4] 6.00-7.00 sec 21.3 MBytes 179 Mbits/sec 15523
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 15620
[ 4] 8.00-9.00 sec 21.4 MBytes 180 Mbits/sec 15603
[ 4] 9.00-10.00 sec 21.5 MBytes 180 Mbits/sec 15646
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 214 MBytes 180 Mbits/sec 0.030 ms 1/156192 (0.00064%)
[ 4] Sent 156192 datagrams


CapeTown
CYGWIN_NT-10.0 IvanPC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Wed, 03 Jun 2020 17:36:15 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Cookie: IvanPC.1591205775.050188.6149e1a1383
[ 4] local 192.168.5.66 port 54145 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 20.0 MBytes 168 Mbits/sec 14597 (omitted)
[ 4] 1.00-2.00 sec 21.2 MBytes 178 Mbits/sec 15459 (omitted)
[ 4] 2.00-3.00 sec 21.6 MBytes 182 Mbits/sec 15755 (omitted)
[ 4] 0.00-1.00 sec 21.5 MBytes 180 Mbits/sec 15635
[ 4] 1.00-2.00 sec 21.5 MBytes 181 Mbits/sec 15673
[ 4] 2.00-3.00 sec 21.4 MBytes 180 Mbits/sec 15606
[ 4] 3.00-4.00 sec 21.4 MBytes 180 Mbits/sec 15617
[ 4] 4.00-5.00 sec 21.5 MBytes 180 Mbits/sec 15642
[ 4] 5.00-6.00 sec 21.5 MBytes 180 Mbits/sec 15622
[ 4] 6.00-7.00 sec 21.4 MBytes 179 Mbits/sec 15582
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 15649
[ 4] 8.00-9.00 sec 21.5 MBytes 180 Mbits/sec 15650
[ 4] 9.00-10.00 sec 21.4 MBytes 180 Mbits/sec 15598
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 215 MBytes 180 Mbits/sec 0.036 ms 1/156274 (0.00064%)
[ 4] Sent 156274 datagrams
CPU Utilization: local/sender 28.2% (6.5%u/21.7%s), remote/receiver 0.6% (0.1%u/0.5%s)

iperf Done.

just finished loading up a fresh pc, going to try from it now as well
 
ijacobs3 said:
JHB
CYGWIN_NT-10.0 IvanPC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Wed, 03 Jun 2020 17:35:17 GMT
Connecting to host iperf.jb1.napafrica.net, port 5201
Cookie: IvanPC.1591205717.179098.611f1a98719
[ 4] local 192.168.5.66 port 53199 connected to 196.10.98.214 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 20.1 MBytes 169 Mbits/sec 14643 (omitted)
[ 4] 1.00-2.00 sec 21.5 MBytes 180 Mbits/sec 15644 (omitted)
[ 4] 2.00-3.00 sec 21.5 MBytes 180 Mbits/sec 15636 (omitted)
[ 4] 0.00-1.00 sec 21.5 MBytes 180 Mbits/sec 15633
[ 4] 1.00-2.00 sec 22.8 MBytes 191 Mbits/sec 16578
[ 4] 2.00-3.00 sec 20.1 MBytes 169 Mbits/sec 14639
[ 4] 3.00-4.00 sec 21.4 MBytes 180 Mbits/sec 15618
[ 4] 4.00-5.00 sec 21.4 MBytes 180 Mbits/sec 15604
[ 4] 5.00-6.00 sec 21.6 MBytes 181 Mbits/sec 15728
[ 4] 6.00-7.00 sec 21.3 MBytes 179 Mbits/sec 15523
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 15620
[ 4] 8.00-9.00 sec 21.4 MBytes 180 Mbits/sec 15603
[ 4] 9.00-10.00 sec 21.5 MBytes 180 Mbits/sec 15646
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 214 MBytes 180 Mbits/sec 0.030 ms 1/156192 (0.00064%)
[ 4] Sent 156192 datagrams


CapeTown
CYGWIN_NT-10.0 IvanPC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Wed, 03 Jun 2020 17:36:15 GMT
Connecting to host iperf.ct1.napafrica.net, port 5201
Cookie: IvanPC.1591205775.050188.6149e1a1383
[ 4] local 192.168.5.66 port 54145 connected to 196.10.99.34 port 5201
Starting Test: protocol: UDP, 1 streams, 1440 byte blocks, omitting 3 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 20.0 MBytes 168 Mbits/sec 14597 (omitted)
[ 4] 1.00-2.00 sec 21.2 MBytes 178 Mbits/sec 15459 (omitted)
[ 4] 2.00-3.00 sec 21.6 MBytes 182 Mbits/sec 15755 (omitted)
[ 4] 0.00-1.00 sec 21.5 MBytes 180 Mbits/sec 15635
[ 4] 1.00-2.00 sec 21.5 MBytes 181 Mbits/sec 15673
[ 4] 2.00-3.00 sec 21.4 MBytes 180 Mbits/sec 15606
[ 4] 3.00-4.00 sec 21.4 MBytes 180 Mbits/sec 15617
[ 4] 4.00-5.00 sec 21.5 MBytes 180 Mbits/sec 15642
[ 4] 5.00-6.00 sec 21.5 MBytes 180 Mbits/sec 15622
[ 4] 6.00-7.00 sec 21.4 MBytes 179 Mbits/sec 15582
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 15649
[ 4] 8.00-9.00 sec 21.5 MBytes 180 Mbits/sec 15650
[ 4] 9.00-10.00 sec 21.4 MBytes 180 Mbits/sec 15598
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 215 MBytes 180 Mbits/sec 0.036 ms 1/156274 (0.00064%)
[ 4] Sent 156274 datagrams
CPU Utilization: local/sender 28.2% (6.5%u/21.7%s), remote/receiver 0.6% (0.1%u/0.5%s)

iperf Done.

just finished loading up a fresh pc, going to try from it now as well
Click to expand...

Both iperfs look good - let's see what the new pc results are like.
 
websquadza said:
Both iperfs look good - let's see what the new pc results are like.
Click to expand...

Okay, now time to see why my pc is being full of ****

The fresh one ( so fresh there isn’t even a adblocker on)

Cape Town
8311bf8ed953e4cb50aa93037ad0337c.jpg

London
6ab76b2b530e61d8e3196915b3d896d3.jpg





Thanks for the input :)
 
ijacobs3 said:
Okay, now time to see why my pc is being full of ****

The fresh one ( so fresh there isn’t even a adblocker on)

Cape Town
8311bf8ed953e4cb50aa93037ad0337c.jpg

London
6ab76b2b530e61d8e3196915b3d896d3.jpg





Thanks for the input :)
Click to expand...

Looking much better. Try reload all the network drivers, often does the trick. Also confirm your router's MTU is set to 1500 on the ethernet port please. What router are you using?
 
websquadza said:
Looking much better. Try reload all the network drivers, often does the trick. Also confirm your router's MTU is set to 1500 on the ethernet port please. What router are you using?
Click to expand...
Going to try reload now :)

It is the netgear one that Mybroadband bestowed upon me, Netgear nighthawk xr300

MTU is on 1500

1591207142459.png
 
on WiFi to London! Hooolyyyy crap

I’ve reinstalled the network card drivers, but still getting the same results, got one more thing to try, otherwise tomorrow I’ll go grab a new card

9173ea6e47dd768c6a1f4e1193aa9937.jpg
 
@ijacobs3 Looks similar to a tcp scaling issue, although probably not. What does it say when you run in cmd: netsh int tcp show global
 
hmmm, ok , the wifi adapter i tested on the fresh machine with, gives me the same cabled result :( , might be windows reload time
 
Loppas said:
@ijacobs3 Looks similar to a tcp scaling issue, although probably not. What does it say when you run in cmd: netsh int tcp show global
Click to expand...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : disabled
Receive Window Auto-Tuning Level : disabled
Add-On Congestion Control Provider : default
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 1000
Receive Segment Coalescing State : enabled
Non Sack Rtt Resiliency : disabled
Max SYN Retransmissions : 4
Fast Open : enabled
Fast Open Fallback : enabled
HyStart : enabled
Pacing Profile : off
 
ijacobs3 said:
TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : disabled
Receive Window Auto-Tuning Level : disabled
Add-On Congestion Control Provider : default
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 1000
Receive Segment Coalescing State : enabled
Non Sack Rtt Resiliency : disabled
Max SYN Retransmissions : 4
Fast Open : enabled
Fast Open Fallback : enabled
HyStart : enabled
Pacing Profile : off
Click to expand...

"Receive Window Auto-Tuning Level : disabled"

There's your problem right there. Enter this: netsh int tcp set global autotuninglevel=normal

Edit:
I encountered this issue recently, it was caused by hamachi disabling the auto tuning when i installed it and as a result windows no longer did any scaling on the packets and i experienced heavily degraded speeds with increased latency. By default it should be set to normal.
 
Last edited:
Loppas said:
"Receive Window Auto-Tuning Level : disabled"

There's your problem right there. Enter this: netsh int tcp set global autotuninglevel=normal

Edit:
I encountered this issue recently, it was caused by hamachi disabling the auto tuning when i installed it and as a result windows no longer did any scaling on the packets and i experienced heavily degraded speeds with increased latency. By default it should be set to normal.
Click to expand...

Thank you

:)

9547491444.png


not quiet the speed on wifi, but certainly much much better :)
 
  • Love
Reactions: Yuu
Loppas said:
"Receive Window Auto-Tuning Level : disabled"

There's your problem right there. Enter this: netsh int tcp set global autotuninglevel=normal

Edit:
I encountered this issue recently, it was caused by hamachi disabling the auto tuning when i installed it and as a result windows no longer did any scaling on the packets and i experienced heavily degraded speeds with increased latency. By default it should be set to normal.
Click to expand...


Edit Spotted.. guess what i chose to use when lock down hit , as a quick fix for people to work remotely....

1591209919366.png
 
websquadza said:
Good News: We've picked up which device may be dropping packets randomly - Bad News: unfortunately it's not a hitless repair. We'll be sending out comms for a scheduled maintenance procedure in CPT during this week. The process will take about 5 minutes and will be done way out of hours to minimise impact.
Click to expand...

@websquadza I see there was a scheduled maintenance for CPT this morning, although it only mentions Vumatel. Was this it or is it still upcoming?
 
Last edited:
Any idea what happened to Mitsol? Don't see packages and I'm sure they were there once upon a time.
 
Seeyou said:
I see there was a scheduled maintenance for CPT this morning, although it only mentions Vumatel. Was this it or is it still upcoming?
Click to expand...

No, that was Vumatel. We’re trying to see if we can in fact do this maintenance without taking services down. We have an idea- just working through the plan at the moment. Otherwise we’ll send out a notice later today.
 
websquadza said:
We made a decision in May to no longer sell Mitsol’s services.
Click to expand...
Please check DM's

Long story short. We have 3 providers in the area all of which are "live or almost" but none of them are willing to share ANY details. Vumatel have been doing this build for 3 years and last I heard was a pop completion in mid May 2020. Mitsol have coverage but pulled that away, trying to find out why. DFA and Link Africa are right outside but that's FTTB and backbones.

It has been a nightmare trying to get fibre here as we were 100% confirmed to have fibre via Mitsol and Vumatel but now they backtracking after confirming. No idea where to go and its been months and I'm slowly going insane with rain tower dying left and right, also got servers to host and all sorts.
 
  • Like
Reactions: Yuu
Having to play using a VPN. Massive loss tonight to EU without it.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X