Status
Not open for further replies.
Cabled device, does not matter if it's wifi or cable. Local is fine, there I get full speed, but I don't need local 20Mb I need international 20Mb. Vumatel, Durbanville, router is a Fortigate 60E

As soon as I changed ISP's yesterday the slowness started. It really feels like I am back on ADSL to be honest.

Are your speedstests over a 1Gb link? if so you have major bandwidth issues lol

Edit: Just have to add, was nice to get connected within 30 minutes last night.
I logged into the Vumatel portal, added the package, and then got a popup to phone or email to get the service going.
The first call was not great, was told that I need to go to the CISP website and place the order there, so I put the phone down lol. Then I thought to myself, how can a ISP tell you to get onto the internet in order to order internet... So I phoned back, told them I have zero access (which was true) to internet that's why I am applying for internet with them. Then some magic happened and it was working, so not a bad support team at all.

Also Cabled Device, Also on Vumatel, Stellenberg (So basically exactly the same routes), Router is a Mikrotik RB2011

http://www.speedtest.net/result/7683752165.png

http://www.speedtest.net/result/7683756975.png

So, quiet possibly something on your side or something you might have changed by mistake :)
 
Also Cabled Device, Also on Vumatel, Stellenberg (So basically exactly the same routes), Router is a Mikrotik RB2011

http://www.speedtest.net/result/7683752165.png

http://www.speedtest.net/result/7683756975.png

So, quiet possibly something on your side or something you might have changed by mistake :)

Then why do I get full speed locally? International is screwed for me, local fine

Seems the only thing I changed by mistake was ISP's lol

Can you do a trace to 41.164.132.41 if you don't mind? Just want to see if the routes are the same, the 41.164.132.41 is in Cape Town...

Tracing route to 41.164.132.41 over a maximum of 30 hops

1 1 ms 1 ms 3 ms 192.168.10.1
2 14 ms 4 ms 2 ms 155.93.227.1
3 2 ms 9 ms 2 ms 154.0.1.125
4 4 ms 2 ms 2 ms 154.0.1.13
5 20 ms 20 ms 19 ms 154.0.1.61
6 20 ms 21 ms 24 ms 154.0.3.113
7 23 ms 24 ms 23 ms 154.0.2.117
8 22 ms 22 ms 22 ms 154.0.5.133
9 26 ms 23 ms 26 ms 196.223.14.24
10 23 ms 23 ms 23 ms 41.160.0.244
11 * * * Request timed out.
12 * * * Request timed out.
13 26 ms 27 ms 27 ms 172.18.32.27
14 24 ms 24 ms 25 ms 41.164.132.33
15 * ^C
 
Last edited:
Then why do I get full speed locally? International is screwed for me, local fine

I am guessing you are using a Windows device.
If so, it will be due to Windows TCP Stack which doesn't scale very well when you add latency.
Hence local is great but international doesn't seem great.

You could try setting your TCP scaling to be a bit more aggressive, but i don't think thats going to help on anything lower than 100mb/s. But if you want to try just google "Change Windows TCP Scaling"

Trace looks the same:

1 <1 ms <1 ms <1 ms 172.18.7.225
2 1 ms 1 ms <1 ms 155.93.227.1
3 1 ms <1 ms <1 ms c3h-backbone.coolideas.co.za [154.0.1.125]
4 1 ms 1 ms 1 ms cd-backbone.coolideas.co.za [154.0.1.13]
5 20 ms 20 ms 20 ms c1p-backbone.coolideas.co.za [154.0.1.61]
6 21 ms 20 ms 20 ms utx-cust.coolideas.co.za [154.0.4.53]
7 19 ms 18 ms 18 ms c35-backbone.coolideas.co.za [154.0.2.113]
8 21 ms 21 ms 20 ms u139-cust.coolideas.co.za [154.0.5.133]
9 19 ms 19 ms 19 ms neotel.jinx.net.za [196.223.14.24]
10 19 ms 19 ms 19 ms 41.160.0.244
11 * * * Request timed out.
12 * * * Request timed out.
13 41 ms 41 ms 41 ms 172.18.32.27
14 42 ms 41 ms 41 ms 41.164.132.33
15 * * * Request timed out.
 
Last edited:
I am guessing you are using a Windows device.
If so, it will be due to Windows TCP Stack which doesn't scale very well when you add latency.
Hence local is great but international doesn't seem great.

You could try setting your TCP scaling to be a bit more aggressive, but i don't think thats going to help on anything lower than 100mb/s. But if you want to try just google "Change Windows TCP Scaling"

I had full speed international till the moment I changed ISP's, that TCP scaling excuse is just a way for ISP's to justify their crap networks
 
I am guessing you are using a Windows device.
If so, it will be due to Windows TCP Stack which doesn't scale very well when you add latency.
Hence local is great but international doesn't seem great.

You could try setting your TCP scaling to be a bit more aggressive, but i don't think thats going to help on anything lower than 100mb/s. But if you want to try just google "Change Windows TCP Scaling"

Trace looks the same:

1 <1 ms <1 ms <1 ms 172.18.7.225
2 1 ms 1 ms <1 ms 155.93.227.1
3 1 ms <1 ms <1 ms c3h-backbone.coolideas.co.za [154.0.1.125]
4 1 ms 1 ms 1 ms cd-backbone.coolideas.co.za [154.0.1.13]
5 20 ms 20 ms 20 ms c1p-backbone.coolideas.co.za [154.0.1.61]
6 21 ms 20 ms 20 ms utx-cust.coolideas.co.za [154.0.4.53]
7 19 ms 18 ms 18 ms c35-backbone.coolideas.co.za [154.0.2.113]
8 21 ms 21 ms 20 ms u139-cust.coolideas.co.za [154.0.5.133]
9 19 ms 19 ms 19 ms neotel.jinx.net.za [196.223.14.24]
10 19 ms 19 ms 19 ms 41.160.0.244
11 * * * Request timed out.
12 * * * Request timed out.
13 41 ms 41 ms 41 ms 172.18.32.27
14 42 ms 41 ms 41 ms 41.164.132.33
15 * * * Request timed out.


Cool thanks for the trace
 
Cabled device, does not matter if it's wifi or cable. Local is fine, there I get full speed, but I don't need local 20Mb I need international 20Mb. Vumatel, Durbanville, router is a Fortigate 60E

As soon as I changed ISP's yesterday the slowness started. It really feels like I am back on ADSL to be honest.

Are your speedstests over a 1Gb link? if so you have major bandwidth issues lol

Edit: Just have to add, was nice to get connected within 30 minutes last night.
I logged into the Vumatel portal, added the package, and then got a popup to phone or email to get the service going.
The first call was not great, was told that I need to go to the CISP website and place the order there, so I put the phone down lol. Then I thought to myself, how can a ISP tell you to get onto the internet in order to order internet... So I phoned back, told them I have zero access (which was true) to internet that's why I am applying for internet with them. Then some magic happened and it was working, so not a bad support team at all.
Have you tried removing the Fortinet? IE plug straight into the CPE? PM me your account details and I can allocate you another IP to test. This sounds like an MTU issue.
 
Have you tried removing the Fortinet? IE plug straight into the CPE? PM me your account details and I can allocate you another IP to test. This sounds like an MTU issue.

Router works fine with other ISP so no need to remove it
 
I had full speed international till the moment I changed ISP's, that TCP scaling is just a way for ISP's to justify their crap networks

Well also your first hop.
1 ms 1 ms 3 ms 192.168.10.1

That tells me you are either on wireless, which can get destroyed as easily as adding 1 new device, to devices being far apart, to somebody next door getting wifi etc etc etc... Or something isn't to great with your router.

Unfortunately we have working proof of TCP scaling and latency... thats why we use the Relay to Stream to Twitch because TCP stack on windows suuuuucks with international connections
 
Well also your first hop.
1 ms 1 ms 3 ms 192.168.10.1

That tells me you are either on wireless, which can get destroyed as easily as adding 1 new device, to devices being far apart, to somebody next door getting wifi etc etc etc... Or something isn't to great with your router.

Unfortunately we have working proof of TCP scaling and latency... thats why we use the Relay to Stream to Twitch because TCP stack on windows suuuuucks with international connections

My TCP scaling is fine thanks, worked 100% till I changed ISP


Don't worry about those ms in the traceroute, it's normal

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.1.5.1
2 2 ms 2 ms 2 ms 10.1.230.1

And those two hops above are R500 000+ 10Gb cisco switches, 20Gb link between them with CPU idling and less than 100Mb traffic through it at the moment, me connected at 1Gb, you don't always get 1ms trace routes on lan, 2ms or 3ms is 100% fine

When you ping it's 1ms.
Pinging 192.168.10.1 with 32 bytes of data:
Reply from 192.168.10.1: bytes=32 time=1ms TTL=255
Reply from 192.168.10.1: bytes=32 time=1ms TTL=255
Reply from 192.168.10.1: bytes=32 time=1ms TTL=255
 
Last edited:
Router works fine with other ISP so no need to remove it
This doesn't matter if the other ISP was fragmenting packets and your Fortinet is using a smaller MTU than normal this can be the result.

It's a simple test so please pm me your account details and entertain the request :). We can then look to tweak your firewall to get to optimum.
 
This doesn't matter if the other ISP was fragmenting packets and your Fortinet is using a smaller MTU than normal this can be the result.

It's a simple test so please pm me your account details and entertain the request :). We can then look to tweak your firewall to get to optimum.

I did PM you details, MTU on Fortigate is 1500 which is the default, let me know if I should change that

HomeFW (global) # fnsysctl ifconfig -a wan1
wan1 Link encap:Ethernet HWaddr *************
inet addr:155.93.227.*** Bcast:155.93.227.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:23762 errors:0 dropped:0 overruns:0 frame:0
TX packets:18867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20070572 (19.1 MB) TX bytes:8373221 (7.10 MB)
 
Last edited:
MTU seems ok no?

ping www.google.co.za -f -l 1500

Pinging www.google.co.za [216.58.223.3] with 1500 bytes of data:
Request timed out.
Request timed out.


If there was an MTU issue I should be getting this: (Friend on Afrihost's test)
H:\>ping www.google.co.za -f -l 1500

Pinging www.google.co.za [216.58.223.3] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
 
MTU seems ok no?

ping www.google.co.za -f -l 1500

Pinging www.google.co.za [216.58.223.3] with 1500 bytes of data:
Request timed out.
Request timed out.


If there was an MTU issue I should be getting this: (Friend on Afrihost's test)
H:\>ping www.google.co.za -f -l 1500

Pinging www.google.co.za [216.58.223.3] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Yes 1500 is the correct setting.

Have you bypassed your firewall as yet?
 
Will plug straight into my ONT and test as well because no matter which overseas server I try my speeds are pretty slow compared to max line speed...
 
Will plug straight into my ONT and test as well because no matter which overseas server I try my speeds are pretty slow compared to max line speed...
Your issue is more than likely packetloss on the FF network. We have seen this with a couple customers.
 
Hey @PBCool

I replied to #COOL-20180921-148990 to get some additional feedback a week ago. Not a single follow up on this ticket in 7 days. I have tried getting your twitter account and email support to escalate it but have had no success.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X