Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
PBCool said:
It seems to be filters with Mweb on some of the new ranges, so just confirming.
Click to expand...
That would make sense if it was the return traffic, but its outbound that is wrong. Its on the CISP network that it goes to JHB instead of straight to the CPT peering point. Almost as if its in the wrong VRF.
 
Tinuva said:
That would make sense if it was the return traffic, but its outbound that is wrong. Its on the CISP network that it goes to JHB instead of straight to the CPT peering point. Almost as if its in the wrong VRF.
Click to expand...
Yeah that part is fixed :), we are migrating kit from one cabinet to another, need to move our NAP interface next.
 
Diabolix said:
Still no feedback from support, he moved from Web Africa and so far Cool Ideas support has been horrid. I hope I never have any issues if this is the support one receives. Starting to regret recommending you guys. @CoolChick @TheRoDent
Click to expand...

Hi there,

I see that connect has replied to the tickets listed above
 
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   17 |   17 |    0 |    0 |    1 |    0 |
|                             154.0.0.121 -    0 |   17 |   17 |    3 |    3 |    6 |    3 |
|                             154.0.4.209 -    0 |   17 |   17 |    2 |    3 |    6 |    2 |
|                             154.0.4.250 -    0 |   17 |   17 |  158 |  159 |  164 |  159 |
|                          195.66.238.234 -    0 |   17 |   17 |  159 |  162 |  175 |  161 |
|              ae1-br01-eqld5.as57976.net -    0 |   17 |   17 |  165 |  173 |  230 |  167 |
|         et-0-0-2-br02-eqam1.as57976.net -    0 |   17 |   17 |  166 |  171 |  201 |  167 |
|        et-0-0-67-pe01-eqam1.as57976.net -    0 |   17 |   17 |  166 |  167 |  171 |  166 |
|                          185.60.112.157 -    0 |   17 |   17 |  165 |  166 |  172 |  168 |
|________________________________________________|______|______|______|______|______|______|

Nice, pings back to normal
 
@PBCool @CoolChick

Good Day

I have had my Fibre with Cool Ideas since March 2016, when I signed up, I got the free router at the time. Back then, I was told that if I cancel in the first year, i just need to return the free router. The router blew due to a power surge about 7 months ago, so it is long gone.

I have sold my house, and so need to cancel my subscription.

I got told now that i would need to pay R400 fee because I cannot return the router.

To be honest, I find this really ridiculous and would never have taken the free router if this was told to me from the start. I remember specifically asking about this over the phone, and as such this fee comes as quite a surprise to me.
 
DERoestorf said:
@PBCool @CoolChick

Good Day

I have had my Fibre with Cool Ideas since March 2016, when I signed up, I got the free router at the time. Back then, I was told that if I cancel in the first year, i just need to return the free router. The router blew due to a power surge about 7 months ago, so it is long gone.

I have sold my house, and so need to cancel my subscription.

I got told now that i would need to pay R400 fee because I cannot return the router.

To be honest, I find this really ridiculous and would never have taken the free router if this was told to me from the start. I remember specifically asking about this over the phone, and as such this fee comes as quite a surprise to me.
Click to expand...

R400 is cheap for a router - the penalty could have been much worse. If they were clear about the potential need to return the router, and you can't return the router, why is a fee surprising?
 
DERoestorf said:
@PBCool @CoolChick

Good Day

I have had my Fibre with Cool Ideas since March 2016, when I signed up, I got the free router at the time. Back then, I was told that if I cancel in the first year, i just need to return the free router. The router blew due to a power surge about 7 months ago, so it is long gone.

I have sold my house, and so need to cancel my subscription.

I got told now that i would need to pay R400 fee because I cannot return the router.

To be honest, I find this really ridiculous and would never have taken the free router if this was told to me from the start. I remember specifically asking about this over the phone, and as such this fee comes as quite a surprise to me.
Click to expand...
The router always belongs to us, free to use so to speak. If it was hit by lightning it should be replaced and covered by your insurance?

Drop me a PM with your account details.
 
DERoestorf said:
@PBCool @CoolChick

Good Day

I have had my Fibre with Cool Ideas since March 2016, when I signed up, I got the free router at the time. Back then, I was told that if I cancel in the first year, i just need to return the free router. The router blew due to a power surge about 7 months ago, so it is long gone.

I have sold my house, and so need to cancel my subscription.

I got told now that i would need to pay R400 fee because I cannot return the router.

To be honest, I find this really ridiculous and would never have taken the free router if this was told to me from the start. I remember specifically asking about this over the phone, and as such this fee comes as quite a surprise to me.
Click to expand...

You can get one from Wootware for R338 https://www.wootware.co.za/tp-link-tl-wr840n-300mbps-wireless-n-router.html (if that is stil lthe same one they use)
 
@TheRoDent @PBCool
@CoolChick

Please assist

Boksburg. 100/100 trenched
Blitzfibre


Ping statistics for 8.8.8.8:
Packets: Sent = 1108, Received = 1070, Lost = 38 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3529ms, Average = 9ms
Control-C

C:\Users\Home>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 32 ms 13 ms 2 ms 192.168.0.1
2 5 ms 4 ms 3 ms 154.0.0.112
3 2 ms 2 ms 2 ms 154.0.4.193
4 4 ms 2 ms 2 ms 154.0.1.17
5 2 ms * 2 ms 154.0.5.133
6 3 ms 3 ms 3 ms google.jinx.net.za [196.223.14.41]
7 4 ms 3 ms 3 ms 72.14.239.33
8 3 ms 3 ms 2 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Ping statistics for 1.1.1.1:
Packets: Sent = 1160, Received = 1122, Lost = 38 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3516ms, Average = 16ms
Control-C


C:\Users\Home>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 1 ms 1 ms 2 3 ms 2 ms 2 ms 154.0.0.112
3 2 ms 2 ms 3 ms 154.0.4.193
4 4 ms 2 ms 2 ms 154.0.2.33
5 4 ms * 2 ms 154.0.5.133
6 5 ms 4 ms 5 ms cloudflare.jinx.net.za [196.223.14.109]
7 5 ms * 3 ms one.one.one.one [1.1.1.1]

Trace complete.

8166146318.png


8166138562.png
 
crawler said:
@TheRoDent @PBCool
@CoolChick

Please assist

Boksburg. 100/100 trenched
Blitzfibre


Ping statistics for 8.8.8.8:
Packets: Sent = 1108, Received = 1070, Lost = 38 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3529ms, Average = 9ms
Control-C

C:\Users\Home>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 32 ms 13 ms 2 ms 192.168.0.1
2 5 ms 4 ms 3 ms 154.0.0.112
3 2 ms 2 ms 2 ms 154.0.4.193
4 4 ms 2 ms 2 ms 154.0.1.17
5 2 ms * 2 ms 154.0.5.133
6 3 ms 3 ms 3 ms google.jinx.net.za [196.223.14.41]
7 4 ms 3 ms 3 ms 72.14.239.33
8 3 ms 3 ms 2 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Ping statistics for 1.1.1.1:
Packets: Sent = 1160, Received = 1122, Lost = 38 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3516ms, Average = 16ms
Control-C


C:\Users\Home>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 1 ms 1 ms 2 3 ms 2 ms 2 ms 154.0.0.112
3 2 ms 2 ms 3 ms 154.0.4.193
4 4 ms 2 ms 2 ms 154.0.2.33
5 4 ms * 2 ms 154.0.5.133
6 5 ms 4 ms 5 ms cloudflare.jinx.net.za [196.223.14.109]
7 5 ms * 3 ms one.one.one.one [1.1.1.1]

Trace complete.

8166146318.png


8166138562.png
Click to expand...
Hi There.
Have you perhaps logged a ticket with us? If so, please kindly give me the reference number so I can troubleshoot accordingly
 
CoolChick said:
Hi There.
Have you perhaps logged a ticket with us? If so, please kindly give me the reference number so I can troubleshoot accordingly
Click to expand...

I have a ticket number and I've replied with iperf tests, but so far I've just been ignored.
 
My iperf to lnms is a glorious shitshow (CPT Octotel 100/100) (and this happens everytime I use a buffer size less than MTU)

Code: 
iperf3 -R -u -b 10M -p 17001 -c lnms.cisp.co.za --omit 1 -l 1450 -t 5
Connecting to host lnms.cisp.co.za, port 17001
Reverse mode, remote host lnms.cisp.co.za is sending
[  4] local 192.168.0.2 port 53594 connected to 154.0.1.254 port 17001
iperf3: OUT OF ORDER - incoming packet = 24 and received packet = 25 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 47 and received packet = 48 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 99 and received packet = 102 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 101 and received packet = 102 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 143 and received packet = 144 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 183 and received packet = 190 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 185 and received packet = 190 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 187 and received packet = 190 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 189 and received packet = 190 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 215 and received packet = 216 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 229 and received packet = 230 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 605 and received packet = 606 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 665 and received packet = 666 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 693 and received packet = 694 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 701 and received packet = 702 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 755 and received packet = 756 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 783 and received packet = 784 AND SP = 4
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  1.24 MBytes  10.4 Mbits/sec  0.510 ms  17/895 (1.9%)  (omitted)
iperf3: OUT OF ORDER - incoming packet = 906 and received packet = 907 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 948 and received packet = 951 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 950 and received packet = 951 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1024 and received packet = 1025 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1303 and received packet = 1304 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1408 and received packet = 1409 AND SP = 4
[  4]   0.00-1.00   sec  1.19 MBytes  10.0 Mbits/sec  0.162 ms  6/863 (0.7%)
iperf3: OUT OF ORDER - incoming packet = 1910 and received packet = 1911 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1980 and received packet = 1985 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1982 and received packet = 1987 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1984 and received packet = 1987 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 1986 and received packet = 1987 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2398 and received packet = 2401 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2400 and received packet = 2401 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2572 and received packet = 2573 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2613 and received packet = 2614 AND SP = 4
[  4]   1.00-2.00   sec  1.19 MBytes  10.0 Mbits/sec  0.791 ms  9/861 (1%)
iperf3: OUT OF ORDER - incoming packet = 2791 and received packet = 2792 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2805 and received packet = 2806 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2819 and received packet = 2820 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3038 and received packet = 3039 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3046 and received packet = 3047 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3057 and received packet = 3058 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3067 and received packet = 3068 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3274 and received packet = 3275 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3403 and received packet = 3404 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3405 and received packet = 3408 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3407 and received packet = 3408 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 3409 and received packet = 3410 AND SP = 4
[  4]   2.00-3.00   sec  1.18 MBytes  9.93 Mbits/sec  0.455 ms  18/862 (2.1%)
iperf3: OUT OF ORDER - incoming packet = 4005 and received packet = 4008 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4007 and received packet = 4008 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4009 and received packet = 4010 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4015 and received packet = 4016 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4046 and received packet = 4047 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4048 and received packet = 4049 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4066 and received packet = 4067 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4077 and received packet = 4082 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4079 and received packet = 4082 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4081 and received packet = 4082 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4221 and received packet = 4226 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4223 and received packet = 4226 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4225 and received packet = 4226 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4265 and received packet = 4268 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4267 and received packet = 4268 AND SP = 4
[  4]   3.00-4.00   sec  1.19 MBytes  10.0 Mbits/sec  0.323 ms  15/862 (1.7%)
iperf3: OUT OF ORDER - incoming packet = 4403 and received packet = 4404 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4466 and received packet = 4467 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4485 and received packet = 4486 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4487 and received packet = 4488 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4515 and received packet = 4516 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4816 and received packet = 4817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4826 and received packet = 4827 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4916 and received packet = 4917 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4973 and received packet = 4974 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4996 and received packet = 5001 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 4998 and received packet = 5001 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 5000 and received packet = 5001 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 5002 and received packet = 5003 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 5144 and received packet = 5145 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 5148 and received packet = 5149 AND SP = 4
[  4]   4.00-5.00   sec  1.19 MBytes  9.99 Mbits/sec  0.233 ms  16/863 (1.9%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-5.00   sec  6.03 MBytes  10.1 Mbits/sec  0.311 ms  64/4331 (1.5%)
[  4] Sent 4331 datagrams
[SUM]  0.0- 5.0 sec  57 datagrams received out-of-order

iperf Done.

Looks fine with default buffer size though...

Code: 
iperf3 -R -b 10M -p 17001 -c lnms.cisp.co.za --omit 2 -u
Connecting to host lnms.cisp.co.za, port 17001
Reverse mode, remote host lnms.cisp.co.za is sending
[  4] local 192.168.0.2 port 50801 connected to 154.0.1.254 port 17001
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-1.00   sec  1.24 MBytes  10.4 Mbits/sec  0.536 ms  0/159 (0%)  (omitted)
[  4]   1.00-2.00   sec  1.19 MBytes  9.97 Mbits/sec  0.803 ms  0/152 (0%)  (omitted)
[  4]   0.00-1.00   sec  1.19 MBytes  9.94 Mbits/sec  0.388 ms  1/153 (0.65%)
[  4]   1.00-2.00   sec  1.19 MBytes  9.98 Mbits/sec  0.494 ms  1/153 (0.65%)
[  4]   2.00-3.00   sec  1.19 MBytes  9.96 Mbits/sec  0.429 ms  0/152 (0%)
[  4]   3.00-4.00   sec  1.20 MBytes  10.0 Mbits/sec  0.322 ms  0/153 (0%)
[  4]   4.00-5.00   sec  1.19 MBytes  9.96 Mbits/sec  0.375 ms  0/152 (0%)
[  4]   5.00-6.00   sec  1.20 MBytes  10.0 Mbits/sec  0.748 ms  0/153 (0%)
[  4]   6.00-7.00   sec  1.19 MBytes  9.95 Mbits/sec  0.333 ms  0/152 (0%)
[  4]   7.00-8.00   sec  1.19 MBytes  9.96 Mbits/sec  0.409 ms  1/153 (0.65%)
[  4]   8.00-9.00   sec  1.20 MBytes  10.0 Mbits/sec  0.699 ms  0/153 (0%)
[  4]   9.00-10.00  sec  1.18 MBytes  9.89 Mbits/sec  0.366 ms  2/153 (1.3%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  12.0 MBytes  10.1 Mbits/sec  0.405 ms  5/1530 (0.33%)
[  4] Sent 1530 datagrams

iperf Done.

When running at 50mbit

-l 1450

Code: 
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-5.00   sec  30.2 MBytes  50.7 Mbits/sec  0.291 ms  8122/21656 (38%)
[  4] Sent 21656 datagrams
[SUM]  0.0- 5.0 sec  8094 datagrams received out-of-order

default

Code: 
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  60.0 MBytes  50.3 Mbits/sec  0.327 ms  36/7648 (0.47%)
[  4] Sent 7648 datagrams
[SUM]  0.0-10.0 sec  8 datagrams received out-of-order

Not sure if that server is just dodgy, I tend to get the opposite when testing again local CPT server.
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X