Cool Ideas Fibre ISP – Feedback Thread 4

KoolKop · Dec 8, 2022

Seeyou said:
Connect your PC directly to the ONT via network cable. Reset all the changes you made above. Create a new PPPoE connection in Windows with the login details CISP gave you, using automatically assigned IP / DNS, then dial it.

TheLostPacket said:
No, you cant use the ONT as a router because it doesnt dial the pppoe connection. It purely acts as a fibre to copper conversion. You need a router to dial the pppoe, or you can use you laptop and have it dial the connection when plugged directly into the ONT

Thanks, I'll try when I'm back home.

bHOLDher · Dec 8, 2022

@PBCool, @TheRoDent
Teams routing still seems a bit broken, with a few people on different FNOs having a lot of packet loss in our teams calls. But I am not sure where the route loops are starting:

Code:

Tracing route to s-0005.s-msedge.net [52.113.194.132]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.2
  2     3 ms     2 ms     2 ms  154.0.0.113
  3     3 ms     2 ms     2 ms  154.0.4.193
  4     *        *        *     Request timed out.
  5     *        *        2 ms  154.0.4.193
  6     *        *        *     Request timed out.
  7     4 ms     4 ms     3 ms  196.223.14.173
  8     6 ms     3 ms     4 ms  ae21-0.icr01.jnb20.ntwk.msn.net [104.44.237.225]
  9     *       23 ms    23 ms  be-100-0.ibr01.jnb20.ntwk.msn.net [104.44.20.65]
 10    23 ms     *        *     be-6-0.ibr01.cpt20.ntwk.msn.net [104.44.29.193]
 11     3 ms     3 ms     3 ms  154.0.4.194
 12     *        *        *     Request timed out.
 13    23 ms    23 ms    23 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 14    22 ms    23 ms    23 ms  13.104.186.208
 15     *       23 ms    26 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 16     *        *        *     Request timed out.
 17    22 ms    22 ms    22 ms  52.113.194.132

Trace complete.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.2 -    0 |  386 |  386 |    0 |    0 |    1 |    0 |
|                             154.0.0.113 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                             154.0.4.194 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   55 |  121 |   55 |    2 |    2 |    4 |    3 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   37 |  158 |  100 |    2 |    3 |    6 |    3 |
|         ae21-0.icr01.jnb20.ntwk.msn.net -   45 |  139 |   77 |    0 |    4 |   14 |    4 |
|                             154.0.4.194 -   48 |  133 |   70 |    2 |    3 |   23 |    3 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   85 |   89 |   14 |    0 |    7 |   24 |    4 |
|                             154.0.4.194 -   52 |  126 |   61 |    2 |   12 |   29 |    3 |
|      ae27-0.cpt02-96cbe-1b.ntwk.msn.net -   34 |  166 |  111 |    0 |   22 |   43 |   23 |
|                             154.0.4.194 -   17 |  233 |  194 |    2 |   18 |   41 |    3 |
|                          13.104.186.208 -   49 |  133 |   69 |    0 |   23 |   46 |    3 |
|                             154.0.4.194 -   49 |  132 |   68 |    3 |   13 |   25 |   23 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   92 |   83 |    7 |    0 |   23 |   25 |   23 |
|                             154.0.4.194 -   32 |  170 |  116 |    3 |   16 |   25 |   23 |
|                          13.104.186.208 -   32 |  173 |  119 |    0 |   23 |   66 |   23 |
|                             154.0.4.194 -   14 |  253 |  219 |    3 |   18 |   66 |   23 |
|                          52.113.194.132 -   17 |  232 |  193 |    0 |   22 |   33 |   23 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

TheRoDent · Dec 8, 2022

bHOLDher said:

@PBCool, @TheRoDent
Teams routing still seems a bit broken, with a few people on different FNOs having a lot of packet loss in our teams calls. But I am not sure where the route loops are starting:

Code:

Tracing route to s-0005.s-msedge.net [52.113.194.132]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.2
  2     3 ms     2 ms     2 ms  154.0.0.113
  3     3 ms     2 ms     2 ms  154.0.4.193
  4     *        *        *     Request timed out.
  5     *        *        2 ms  154.0.4.193
  6     *        *        *     Request timed out.
  7     4 ms     4 ms     3 ms  196.223.14.173
  8     6 ms     3 ms     4 ms  ae21-0.icr01.jnb20.ntwk.msn.net [104.44.237.225]
  9     *       23 ms    23 ms  be-100-0.ibr01.jnb20.ntwk.msn.net [104.44.20.65]
 10    23 ms     *        *     be-6-0.ibr01.cpt20.ntwk.msn.net [104.44.29.193]
 11     3 ms     3 ms     3 ms  154.0.4.194
 12     *        *        *     Request timed out.
 13    23 ms    23 ms    23 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 14    22 ms    23 ms    23 ms  13.104.186.208
 15     *       23 ms    26 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 16     *        *        *     Request timed out.
 17    22 ms    22 ms    22 ms  52.113.194.132

Trace complete.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.2 -    0 |  386 |  386 |    0 |    0 |    1 |    0 |
|                             154.0.0.113 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                             154.0.4.194 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   55 |  121 |   55 |    2 |    2 |    4 |    3 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   37 |  158 |  100 |    2 |    3 |    6 |    3 |
|         ae21-0.icr01.jnb20.ntwk.msn.net -   45 |  139 |   77 |    0 |    4 |   14 |    4 |
|                             154.0.4.194 -   48 |  133 |   70 |    2 |    3 |   23 |    3 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   85 |   89 |   14 |    0 |    7 |   24 |    4 |
|                             154.0.4.194 -   52 |  126 |   61 |    2 |   12 |   29 |    3 |
|      ae27-0.cpt02-96cbe-1b.ntwk.msn.net -   34 |  166 |  111 |    0 |   22 |   43 |   23 |
|                             154.0.4.194 -   17 |  233 |  194 |    2 |   18 |   41 |    3 |
|                          13.104.186.208 -   49 |  133 |   69 |    0 |   23 |   46 |    3 |
|                             154.0.4.194 -   49 |  132 |   68 |    3 |   13 |   25 |   23 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   92 |   83 |    7 |    0 |   23 |   25 |   23 |
|                             154.0.4.194 -   32 |  170 |  116 |    3 |   16 |   25 |   23 |
|                          13.104.186.208 -   32 |  173 |  119 |    0 |   23 |   66 |   23 |
|                             154.0.4.194 -   14 |  253 |  219 |    3 |   18 |   66 |   23 |
|                          52.113.194.132 -   17 |  232 |  193 |    0 |   22 |   33 |   23 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

Cool, checking it out.

TheRoDent · Dec 8, 2022

bHOLDher said:

@PBCool, @TheRoDent
Teams routing still seems a bit broken, with a few people on different FNOs having a lot of packet loss in our teams calls. But I am not sure where the route loops are starting:

Code:

Tracing route to s-0005.s-msedge.net [52.113.194.132]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.2
  2     3 ms     2 ms     2 ms  154.0.0.113
  3     3 ms     2 ms     2 ms  154.0.4.193
  4     *        *        *     Request timed out.
  5     *        *        2 ms  154.0.4.193
  6     *        *        *     Request timed out.
  7     4 ms     4 ms     3 ms  196.223.14.173
  8     6 ms     3 ms     4 ms  ae21-0.icr01.jnb20.ntwk.msn.net [104.44.237.225]
  9     *       23 ms    23 ms  be-100-0.ibr01.jnb20.ntwk.msn.net [104.44.20.65]
 10    23 ms     *        *     be-6-0.ibr01.cpt20.ntwk.msn.net [104.44.29.193]
 11     3 ms     3 ms     3 ms  154.0.4.194
 12     *        *        *     Request timed out.
 13    23 ms    23 ms    23 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 14    22 ms    23 ms    23 ms  13.104.186.208
 15     *       23 ms    26 ms  ae27-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.230.107]
 16     *        *        *     Request timed out.
 17    22 ms    22 ms    22 ms  52.113.194.132

Trace complete.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.2 -    0 |  386 |  386 |    0 |    0 |    1 |    0 |
|                             154.0.0.113 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                             154.0.4.194 -    0 |  386 |  386 |    2 |    2 |    4 |    2 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   55 |  121 |   55 |    2 |    2 |    4 |    3 |
|                      Request timed out. -  100 |   77 |    0 |    0 |    0 |    0 |    0 |
|                             154.0.4.194 -   37 |  158 |  100 |    2 |    3 |    6 |    3 |
|         ae21-0.icr01.jnb20.ntwk.msn.net -   45 |  139 |   77 |    0 |    4 |   14 |    4 |
|                             154.0.4.194 -   48 |  133 |   70 |    2 |    3 |   23 |    3 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   85 |   89 |   14 |    0 |    7 |   24 |    4 |
|                             154.0.4.194 -   52 |  126 |   61 |    2 |   12 |   29 |    3 |
|      ae27-0.cpt02-96cbe-1b.ntwk.msn.net -   34 |  166 |  111 |    0 |   22 |   43 |   23 |
|                             154.0.4.194 -   17 |  233 |  194 |    2 |   18 |   41 |    3 |
|                          13.104.186.208 -   49 |  133 |   69 |    0 |   23 |   46 |    3 |
|                             154.0.4.194 -   49 |  132 |   68 |    3 |   13 |   25 |   23 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   92 |   83 |    7 |    0 |   23 |   25 |   23 |
|                             154.0.4.194 -   32 |  170 |  116 |    3 |   16 |   25 |   23 |
|                          13.104.186.208 -   32 |  173 |  119 |    0 |   23 |   66 |   23 |
|                             154.0.4.194 -   14 |  253 |  219 |    3 |   18 |   66 |   23 |
|                          52.113.194.132 -   17 |  232 |  193 |    0 |   22 |   33 |   23 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

Check this again please. We are now preferring msn network via NAP Africa.

bHOLDher · Dec 8, 2022

TheRoDent said:
Check this again please. We are now preferring msn network via NAP Africa.

It definitely looks cleaner, but I was running a continuous ping and had a +-20s period of timeouts, I wonder if there is another problem on MS's network too?

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.2 -    0 |  256 |  256 |    0 |    0 |    1 |    0 |
|                             154.0.0.113 -    0 |  256 |  256 |    2 |    2 |    4 |    2 |
|                             154.0.4.193 -    0 |  256 |  256 |    2 |    2 |    3 |    2 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                    microsoft.ixp.joburg -    3 |  234 |  228 |    3 |    4 |   58 |    3 |
|         ae21-0.icr01.jnb20.ntwk.msn.net -    6 |  210 |  198 |    3 |    4 |   27 |    3 |
|       be-100-0.ibr01.jnb20.ntwk.msn.net -   93 |   54 |    4 |    0 |   23 |   24 |   23 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   90 |   56 |    6 |    0 |   24 |   29 |   24 |
|        ae100-0.icr01.cpt20.ntwk.msn.net -   11 |  182 |  163 |    0 |   23 |   43 |   23 |
|      ae27-0.cpt02-96cbe-1b.ntwk.msn.net -    4 |  228 |  221 |   22 |   23 |   60 |   23 |
|                          13.104.186.208 -    4 |  226 |  219 |   22 |   22 |   47 |   23 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                          52.113.194.132 -    4 |  228 |  221 |   22 |   22 |   27 |   22 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

bHOLDher · Dec 8, 2022

TheRoDent said:
Check this again please. We are now preferring msn network via NAP Africa.

It actually looks good now, not getting ping timeouts anymore. Thanks!!

TheRoDent · Dec 8, 2022

bHOLDher said:

It definitely looks cleaner, but I was running a continuous ping and had a +-20s period of timeouts, I wonder if there is another problem on MS's network too?

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.2 -    0 |  256 |  256 |    0 |    0 |    1 |    0 |
|                             154.0.0.113 -    0 |  256 |  256 |    2 |    2 |    4 |    2 |
|                             154.0.4.193 -    0 |  256 |  256 |    2 |    2 |    3 |    2 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                    microsoft.ixp.joburg -    3 |  234 |  228 |    3 |    4 |   58 |    3 |
|         ae21-0.icr01.jnb20.ntwk.msn.net -    6 |  210 |  198 |    3 |    4 |   27 |    3 |
|       be-100-0.ibr01.jnb20.ntwk.msn.net -   93 |   54 |    4 |    0 |   23 |   24 |   23 |
|         be-6-0.ibr01.cpt20.ntwk.msn.net -   90 |   56 |    6 |    0 |   24 |   29 |   24 |
|        ae100-0.icr01.cpt20.ntwk.msn.net -   11 |  182 |  163 |    0 |   23 |   43 |   23 |
|      ae27-0.cpt02-96cbe-1b.ntwk.msn.net -    4 |  228 |  221 |   22 |   23 |   60 |   23 |
|                          13.104.186.208 -    4 |  226 |  219 |   22 |   22 |   47 |   23 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                          52.113.194.132 -    4 |  228 |  221 |   22 |   22 |   27 |   22 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

OK, would have been a bit iffy whilst the network was converging.

BadBoyGP · Dec 8, 2022

PBCool said:
Are you also on Vuma Villages?

Vuma Ariel, west rand jhb.

At the moment no internet connection for the last 5mins.

NR7 · Dec 8, 2022

Internet unusable. Openserve JHB East.

@TheRoDent

TheRoDent · Dec 8, 2022

chrisGolf said:

Thanks

Code:

$ ping 9.9.9.9 -c 5
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=56 time=4.07 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=56 time=4.20 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=56 time=4.27 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=56 time=4.09 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=56 time=4.06 ms

--- 9.9.9.9 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 4.061/4.138/4.274/0.083 ms

was quad9 an isolated issue? or would other routes be impacted ?

Please note that we are experiencing issues at JINX/Q9 again so have reverted changes.

Latency will be increased again.

semaphore · Dec 8, 2022

Dead here evotel north riding

bullzeye.za · Dec 8, 2022

Same here, internet down. Call Centre immediately hangs up, figure something bad happened.

TheRoDent · Dec 8, 2022

NR7 said:
Internet unusable. Openserve JHB East.

@TheRoDent

What are the symptoms ? Can you do a traceroute to 8.8.8.8 for me ?

BadBoyGP · Dec 8, 2022

TheRoDent said:
Please note that we are experiencing issues at JINX/Q9 again so have reverted changes.

Latency will be increased again.

At the moment there is 0 connection..

Will it come back?

kbgvirus · Dec 8, 2022

Vuma Ariel JHB North

Completely dead. This has become way to frequent

BadBoyGP · Dec 8, 2022

kbgvirus said:
Vuma Ariel JHB North

Completely dead. This has become way to frequent

Same here, vuma Ariel Constantia kloof, west rand

TheRoDent · Dec 8, 2022

bullzeye.za said:
Same here, internet down. Call Centre immediately hangs up, figure something bad happened.

Investigating.

NR7 · Dec 8, 2022

TheRoDent said:
What are the symptoms ? Can you do a traceroute to 8.8.8.8 for me ?

Completely dead, can't do anything.

Im on Openserve and two other people in here reported the same on Evotel and Vuma. So it must be a Cool Ideas issue then ?

bullzeye.za · Dec 8, 2022

TheRoDent said:
What are the symptoms ? Can you do a traceroute to 8.8.8.8 for me ?

tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.220
2 2 ms 2 ms 2 ms 154.0.0.119
3 2 ms 2 ms 2 ms 154.0.4.194
4 2 ms 2 ms 2 ms 100.99.0.145
5 * 2 ms 2 ms 100.99.0.55
6 2 ms 2 ms 2 ms 100.99.0.146
7 2 ms 2 ms 2 ms 100.99.0.55
8 3 ms 2 ms 2 ms 100.99.0.145
9 3 ms 2 ms 2 ms 100.99.0.55
10 2 ms 2 ms 2 ms 100.99.0.146
11 2 ms 2 ms 2 ms 100.99.0.55
12 2 ms 2 ms 2 ms 100.99.0.146
13 2 ms 2 ms 2 ms 100.99.0.55
14 2 ms 2 ms 2 ms 100.99.0.146
15 2 ms 2 ms 2 ms 100.99.0.55
16 3 ms 2 ms 2 ms 100.99.0.146
17 * * * Request timed out.
18 3 ms 3 ms 2 ms 100.99.0.145
19 * * * Request timed out.
20 2 ms 2 ms 2 ms 100.99.0.145
21 2 ms 2 ms 2 ms 100.99.0.55
22 2 ms 2 ms 2 ms 100.99.0.146
23 2 ms 2 ms 2 ms 100.99.0.55
24 3 ms 2 ms 2 ms 100.99.0.145
25 2 ms * 3 ms 100.99.0.55
26 3 ms 2 ms 2 ms 100.99.0.145
27 3 ms 2 ms 2 ms 100.99.0.55
28 3 ms 2 ms 2 ms 100.99.0.145
29 3 ms 2 ms 2 ms 100.99.0.55
30 2 ms 2 ms 2 ms 100.99.0.146

So just loops back and forth between 55 and 145/146. Cool.

semaphore · Dec 8, 2022

TheRoDent said:
What are the symptoms ? Can you do a traceroute to 8.8.8.8 for me ?

Cool Ideas Fibre ISP – Feedback Thread 4

Active Member

Well-Known Member

Cool Ideas Rep

Cool Ideas Rep

Well-Known Member

Well-Known Member

Cool Ideas Rep

Senior Member

Senior Member

Cool Ideas Rep

Honorary Master

Expert Member

Cool Ideas Rep

Senior Member

Active Member

Senior Member

Cool Ideas Rep

Senior Member

Expert Member

Honorary Master

Attachments