Cool Ideas Fibre ISP - Feedback

PBCool · Sep 15, 2017

Saano21 said:
@PBCool

What is the next step ? Do I just wait for someone to contact me ?

Yes so once you have applied for the line, the operator should give you a call and schedule an installation date. The process is the address gets confirmed and the operator "unlocks" it from us applying as the ISP. From there they do the install and configuration then switch the status over to "Pending ISP installation" which we do and change status again.

That's in a perfect world though which of late hasn't been as smooth as it should be on the aerial stuff.

requiem · Sep 15, 2017

Have ticket open since 31 August.

Staff take 1 - 2 days to reply then escalate to vuma.

I am not impressed with the lack of a resolution to my issue.

PBCool · Sep 15, 2017

requiem said:
Have ticket open since 31 August.

Staff take 1 - 2 days to reply then escalate to vuma.

I am not impressed with the lack of a resolution to my issue.

Please PM me the ticket number so I can investigate. The delay is usually due to the response time from Vumatel. I can escalate for you.

Enzo Matrix · Sep 16, 2017

P2P seems to be very slow... 100mb line and getting roughly 1/10th of that.

Speedtest.net is full speed

Whatsup Cool Ideas? Am i being shaped here????

PBCool · Sep 16, 2017

rakabos3 said:
P2P seems to be very slow... 100mb line and getting roughly 1/10th of that.

Speedtest.net is full speed

Whatsup Cool Ideas? Am i being shaped here????

We don't shape if you read this thread I have stated this so many many times. If it's via P2P there are lots of factors at play. Is it torrenting? Which client are you using? Is it setup correctly? How many seeds are there? What is the ratio of the tracker you are using etc.

Enzo Matrix · Sep 16, 2017

PBCool said:
We don't shape if you read this thread I have stated this so many many times. If it's via P2P there are lots of factors at play. Is it torrenting? Which client are you using? Is it setup correctly? How many seeds are there? What is the ratio of the tracker you are using etc.

Hi

I have utorrent and qbittorrent running to see, seeds are 1000+

Sometimes its maxed out, sometimes it crawls. I understand torrent seeds etc.

I just ran a steam update, it was fullspeed. There is definately an issues with P2P

Tinuva · Sep 16, 2017

@PBCool

I actually found some strange stuff testing torrents myself.

I loaded up a torrent on my docker server at home, using Transmission client.
I also loaded up the same torrent on a server in Cape Town data center, using the transmission client.

Transmission on my CISP line, fails to connect to trackers, but is able to download slowly from encrypted peers.
Transmission on server in data center, is able to connect o trackers and also download from peers.

So I don't know where it is blocked, it could be either of:
- enetworks (upstream provider in Cape Town for CISP line)
- liquidtelecom (doubt it)
- somewhere else
- or the IP range I am on is blocked by all of these trackers (doubt it)

Now here is the interesting part, mtr to 1 of the trackers that work on DC transmission and not on CISP transmision client:

DC Server:

Code:

[root@thor ~]# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:27:03 2017
HOST: thor.xxxxxxxxxxx            Loss%   Snt   Last   Avg  Best  Wrst StDev
  4.|-- 168.209.231.100            0.0%    10    3.4   4.1   3.3  10.1   2.0
  5.|-- 168.209.161.59             0.0%    10    3.3   3.4   3.2   3.8   0.0
  6.|-- 168.209.168.7              0.0%    10    3.6   3.7   3.1   5.9   0.6
  7.|-- 168.209.255.222            0.0%    10    4.5   3.9   3.1   8.6   1.6
  8.|-- 168.209.255.222            0.0%    10    3.5  82.7   3.1 169.8  84.0
  9.|-- 149.6.148.129              0.0%    10  144.5 148.8 142.9 168.8  10.4
 10.|-- 154.54.57.105              0.0%    10  142.9 143.0 142.6 143.6   0.0
 11.|-- 154.54.56.77               0.0%    10  143.4 145.0 142.9 150.6   2.8
 12.|-- 130.117.49.117             0.0%    10  156.7 155.6 150.3 157.4   2.7
 13.|-- 130.117.50.33              0.0%    10  157.3 157.2 156.3 159.1   0.7
 14.|-- 154.25.5.242               0.0%    10  157.1 157.6 156.5 160.3   1.2
 15.|-- 87.230.114.22              0.0%    10  156.8 156.9 156.3 157.5   0.0
 16.|-- 87.230.114.22              0.0%    10  157.5 157.3 156.3 159.0   0.6
 17.|-- 62.138.129.14              0.0%    10  158.9 163.1 156.3 194.8  11.7
 18.|-- 62.138.0.158               0.0%    10  156.8 156.6 156.3 157.0   0.0

CISP line:

Code:

root@web:~# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:26:32 2017
HOST: web                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.241.1              0.0%    10    0.5   0.4   0.3   0.6   0.0
  2.|-- 155.93.252.1               0.0%    10    1.4   1.3   1.1   1.4   0.0
  3.|-- 154.0.1.125                0.0%    10    1.3   1.2   1.1   1.4   0.0
  4.|-- 154.0.1.13                 0.0%    10    1.5   1.4   1.3   1.5   0.0
  5.|-- 45.220.191.17              0.0%    10    1.4   1.5   1.2   2.3   0.0
  6.|-- 154.72.97.164              0.0%    10    1.9   1.6   1.4   1.9   0.0
  7.|-- 41.60.242.1                0.0%    10    2.2   2.3   2.1   3.4   0.3
  8.|-- 5.11.10.170                0.0%    10  142.2 142.2 141.9 143.9   0.5
  9.|-- 5.11.10.115                0.0%    10  141.9 141.9 141.7 142.2   0.0
 10.|-- 5.11.10.99                 0.0%    10  142.1 142.5 142.0 144.3   0.6
 11.|-- 80.81.192.239              0.0%    10  157.9 158.2 157.8 160.1   0.5
 12.|-- 87.230.114.9               0.0%    10  161.1 161.4 161.0 163.7   0.7
 13.|-- 87.230.114.22              0.0%    10  161.2 161.5 160.8 166.1   1.6
 14.|-- 62.138.129.14              0.0%    10  158.6 161.3 158.6 169.3   3.7
 15.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
root@web:~#

Its has if packets are hard dropped inbound when they have a source IP of know trackers.

Not a big deal, but interesting none the less. Not sure if it is the same case when on a CISP IP range on JHB ect.

PBCool · Sep 16, 2017

Tinuva said:

@PBCool

I actually found some strange stuff testing torrents myself.

I loaded up a torrent on my docker server at home, using Transmission client.
I also loaded up the same torrent on a server in Cape Town data center, using the transmission client.

Transmission on my CISP line, fails to connect to trackers, but is able to download slowly from encrypted peers.
Transmission on server in data center, is able to connect o trackers and also download from peers.

So I don't know where it is blocked, it could be either of:
- enetworks (upstream provider in Cape Town for CISP line)
- liquidtelecom (doubt it)
- somewhere else
- or the IP range I am on is blocked by all of these trackers (doubt it)

Now here is the interesting part, mtr to 1 of the trackers that work on DC transmission and not on CISP transmision client:

DC Server:

Code:

[root@thor ~]# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:27:03 2017
HOST: thor.xxxxxxxxxxx            Loss%   Snt   Last   Avg  Best  Wrst StDev
  4.|-- 168.209.231.100            0.0%    10    3.4   4.1   3.3  10.1   2.0
  5.|-- 168.209.161.59             0.0%    10    3.3   3.4   3.2   3.8   0.0
  6.|-- 168.209.168.7              0.0%    10    3.6   3.7   3.1   5.9   0.6
  7.|-- 168.209.255.222            0.0%    10    4.5   3.9   3.1   8.6   1.6
  8.|-- 168.209.255.222            0.0%    10    3.5  82.7   3.1 169.8  84.0
  9.|-- 149.6.148.129              0.0%    10  144.5 148.8 142.9 168.8  10.4
 10.|-- 154.54.57.105              0.0%    10  142.9 143.0 142.6 143.6   0.0
 11.|-- 154.54.56.77               0.0%    10  143.4 145.0 142.9 150.6   2.8
 12.|-- 130.117.49.117             0.0%    10  156.7 155.6 150.3 157.4   2.7
 13.|-- 130.117.50.33              0.0%    10  157.3 157.2 156.3 159.1   0.7
 14.|-- 154.25.5.242               0.0%    10  157.1 157.6 156.5 160.3   1.2
 15.|-- 87.230.114.22              0.0%    10  156.8 156.9 156.3 157.5   0.0
 16.|-- 87.230.114.22              0.0%    10  157.5 157.3 156.3 159.0   0.6
 17.|-- 62.138.129.14              0.0%    10  158.9 163.1 156.3 194.8  11.7
 18.|-- 62.138.0.158               0.0%    10  156.8 156.6 156.3 157.0   0.0

CISP line:

Code:

root@web:~# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:26:32 2017
HOST: web                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.241.1              0.0%    10    0.5   0.4   0.3   0.6   0.0
  2.|-- 155.93.252.1               0.0%    10    1.4   1.3   1.1   1.4   0.0
  3.|-- 154.0.1.125                0.0%    10    1.3   1.2   1.1   1.4   0.0
  4.|-- 154.0.1.13                 0.0%    10    1.5   1.4   1.3   1.5   0.0
  5.|-- 45.220.191.17              0.0%    10    1.4   1.5   1.2   2.3   0.0
  6.|-- 154.72.97.164              0.0%    10    1.9   1.6   1.4   1.9   0.0
  7.|-- 41.60.242.1                0.0%    10    2.2   2.3   2.1   3.4   0.3
  8.|-- 5.11.10.170                0.0%    10  142.2 142.2 141.9 143.9   0.5
  9.|-- 5.11.10.115                0.0%    10  141.9 141.9 141.7 142.2   0.0
 10.|-- 5.11.10.99                 0.0%    10  142.1 142.5 142.0 144.3   0.6
 11.|-- 80.81.192.239              0.0%    10  157.9 158.2 157.8 160.1   0.5
 12.|-- 87.230.114.9               0.0%    10  161.1 161.4 161.0 163.7   0.7
 13.|-- 87.230.114.22              0.0%    10  161.2 161.5 160.8 166.1   1.6
 14.|-- 62.138.129.14              0.0%    10  158.6 161.3 158.6 169.3   3.7
 15.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
root@web:~#

Its has if packets are hard dropped inbound when they have a source IP of know trackers.

Not a big deal, but interesting none the less. Not sure if it is the same case when on a CISP IP range on JHB ect.

There is a general issue on Octotel if you are on their line? I will check with upstream anyway.

PBCool · Sep 16, 2017

Tinuva said:

@PBCool

I actually found some strange stuff testing torrents myself.

I loaded up a torrent on my docker server at home, using Transmission client.
I also loaded up the same torrent on a server in Cape Town data center, using the transmission client.

Transmission on my CISP line, fails to connect to trackers, but is able to download slowly from encrypted peers.
Transmission on server in data center, is able to connect o trackers and also download from peers.

So I don't know where it is blocked, it could be either of:
- enetworks (upstream provider in Cape Town for CISP line)
- liquidtelecom (doubt it)
- somewhere else
- or the IP range I am on is blocked by all of these trackers (doubt it)

Now here is the interesting part, mtr to 1 of the trackers that work on DC transmission and not on CISP transmision client:

DC Server:

Code:

[root@thor ~]# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:27:03 2017
HOST: thor.xxxxxxxxxxx            Loss%   Snt   Last   Avg  Best  Wrst StDev
  4.|-- 168.209.231.100            0.0%    10    3.4   4.1   3.3  10.1   2.0
  5.|-- 168.209.161.59             0.0%    10    3.3   3.4   3.2   3.8   0.0
  6.|-- 168.209.168.7              0.0%    10    3.6   3.7   3.1   5.9   0.6
  7.|-- 168.209.255.222            0.0%    10    4.5   3.9   3.1   8.6   1.6
  8.|-- 168.209.255.222            0.0%    10    3.5  82.7   3.1 169.8  84.0
  9.|-- 149.6.148.129              0.0%    10  144.5 148.8 142.9 168.8  10.4
 10.|-- 154.54.57.105              0.0%    10  142.9 143.0 142.6 143.6   0.0
 11.|-- 154.54.56.77               0.0%    10  143.4 145.0 142.9 150.6   2.8
 12.|-- 130.117.49.117             0.0%    10  156.7 155.6 150.3 157.4   2.7
 13.|-- 130.117.50.33              0.0%    10  157.3 157.2 156.3 159.1   0.7
 14.|-- 154.25.5.242               0.0%    10  157.1 157.6 156.5 160.3   1.2
 15.|-- 87.230.114.22              0.0%    10  156.8 156.9 156.3 157.5   0.0
 16.|-- 87.230.114.22              0.0%    10  157.5 157.3 156.3 159.0   0.6
 17.|-- 62.138.129.14              0.0%    10  158.9 163.1 156.3 194.8  11.7
 18.|-- 62.138.0.158               0.0%    10  156.8 156.6 156.3 157.0   0.0

CISP line:

Code:

root@web:~# mtr --udp -P 6969 tracker.coppersurfer.tk --report -n
Start: Sat Sep 16 10:26:32 2017
HOST: web                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.241.1              0.0%    10    0.5   0.4   0.3   0.6   0.0
  2.|-- 155.93.252.1               0.0%    10    1.4   1.3   1.1   1.4   0.0
  3.|-- 154.0.1.125                0.0%    10    1.3   1.2   1.1   1.4   0.0
  4.|-- 154.0.1.13                 0.0%    10    1.5   1.4   1.3   1.5   0.0
  5.|-- 45.220.191.17              0.0%    10    1.4   1.5   1.2   2.3   0.0
  6.|-- 154.72.97.164              0.0%    10    1.9   1.6   1.4   1.9   0.0
  7.|-- 41.60.242.1                0.0%    10    2.2   2.3   2.1   3.4   0.3
  8.|-- 5.11.10.170                0.0%    10  142.2 142.2 141.9 143.9   0.5
  9.|-- 5.11.10.115                0.0%    10  141.9 141.9 141.7 142.2   0.0
 10.|-- 5.11.10.99                 0.0%    10  142.1 142.5 142.0 144.3   0.6
 11.|-- 80.81.192.239              0.0%    10  157.9 158.2 157.8 160.1   0.5
 12.|-- 87.230.114.9               0.0%    10  161.1 161.4 161.0 163.7   0.7
 13.|-- 87.230.114.22              0.0%    10  161.2 161.5 160.8 166.1   1.6
 14.|-- 62.138.129.14              0.0%    10  158.6 161.3 158.6 169.3   3.7
 15.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
root@web:~#

Its has if packets are hard dropped inbound when they have a source IP of know trackers.

Not a big deal, but interesting none the less. Not sure if it is the same case when on a CISP IP range on JHB ect.

Cape Town is an IPT service vs JHB which we have our own network to London. But obviously if there is a portion of the planet our range can't reach it's something we need to address. Will check from JHB side shortly.

PBCool · Sep 16, 2017

rakabos3 said:
Hi

I have utorrent and qbittorrent running to see, seeds are 1000+

Sometimes its maxed out, sometimes it crawls. I understand torrent seeds etc.

I just ran a steam update, it was fullspeed. There is definately an issues with P2P

PM me your account details, as mentioned all protocols are treated with the same priority on the network at all times.

mithrandi · Sep 16, 2017

I don't know about utorrent, but qbittorrent's default connection limits are way too low for a 1000+ seed torrent on a 100 Mbps line; the defaults are something like 100 connections globally and 50 per torrent. It is quite likely that 50 seeds won't be able to collectively upload to you at 100 Mbps unless you got lucky and connected to seeds with high upload bandwidth available (and the chances of this are low in a swarm with 1000+ peers). Try increasing the connection limits and see how it goes.

EDIT: A little explanation as to why this is: A common scenario is someone on a connection with 1 Mbps upload, limiting their upload to 500 kbps, and uploading to 8 different peers; this means that each peer is only getting about 62 kbps each, so on a 100 Mbps connection, you would need to connect to over 1600 of these peers to max out your connection. Of course, there are peers with much higher upload speeds, but in a swarm of 1000+ peers, if you are only connecting to 50 of them, the chances of connecting to any of the peers on higher speed connections is low, so you need the higher connection limit both to increase your speeds by collecting more peers, but also to increase the chances of connecting to one of the peers with more upload bandwidth to offer you.

I have qBittorrent configured for 5000 connections globally and 500 per torrent (but note that on Linux, you may need to increase the file descriptor resource limits to go beyond 1024 connections).

lexor · Sep 16, 2017

Vumatel installed today and after a 30 second call to Cool Ideas I was online.

100/10 - so far VERY happy

Nick_K · Sep 16, 2017

Having a strange issue playing The Division. There is a group of four of us who play, three on Cool Ideas through Vumatel and one on Telkom DSL. For the past three days all of those on Cool Ideas have been having disconnects every thirty minutes or so and when it happens it happens to everybody at the same time. Geographically we are spread out over around 30KM (Johannesburg area).

The guy on DSL has no disconnects whatsoever.

Anybody else having anything like this on Cool Ideas?

Loppas · Sep 17, 2017

This doesn't look right:

PBCool · Sep 17, 2017

Loppas said:
This doesn't look right:

View attachment 463781

So looks like most of the loss happens across your line portion, first hop from router to gateway so please log it with us so we can log it with the operator. Support@cisp.co.za

PBCool · Sep 17, 2017

Nick_K said:
Having a strange issue playing The Division. There is a group of four of us who play, three on Cool Ideas through Vumatel and one on Telkom DSL. For the past three days all of those on Cool Ideas have been having disconnects every thirty minutes or so and when it happens it happens to everybody at the same time. Geographically we are spread out over around 30KM (Johannesburg area).

The guy on DSL has no disconnects whatsoever.

Anybody else having anything like this on Cool Ideas?

Can you PM me your IP?

Loppas · Sep 17, 2017

PBCool said:
Can you PM me your IP?

Will do.

PBCool · Sep 17, 2017

Loppas said:
Will do.

Please log your line fault with us as mentioned

Loppas · Sep 17, 2017

PBCool said:
Please log your line fault with us as mentioned

Didn't receive a message, but im not quite sure its a line fault because the ping is stable to cpt and international. I just ran a test to that specifically and it had some packet loss.

PBCool · Sep 17, 2017

Loppas said:
Didn't receive a message, but im not quite sure its a line fault because the ping is stable to cpt and international. I just ran a test to that specifically and it had some packet loss.

According to your graph nearly 2% of the packet loss is on your first hop of that path which would imply a line issue.

Cool Ideas Fibre ISP - Feedback

Cool Ideas Rep

Expert Member

Cool Ideas Rep

Honorary Master

Cool Ideas Rep

Honorary Master

The Magician

Cool Ideas Rep

Cool Ideas Rep

Cool Ideas Rep

Well-Known Member

Expert Member

Well-Known Member

Senior Member

Cool Ideas Rep

Cool Ideas Rep

Senior Member

Cool Ideas Rep

Senior Member

Cool Ideas Rep