Cool Ideas Fibre ISP – Feedback Thread 6

bHOLDher said:
I doubt that PiHole would be giving you trouble, I run it too. If PiHole works for you with IPv4 then you don't need to fiddle with it, it will still resolve both A and AAAA records. To try narrow down the issue, run
Code: 
nslookup www.google.co.za
Confirm that you get both IPv4 and IPv6 addresses. Now you know PiHole works fine.
Then take both answers and run
Code: 
tracert 192.178.54.3
and
tracert [2c0f:fb50:4002:81c::2003]
And confirm whether or not your router is blocking the traffic.

The following should also route without trouble for you, whether or not IPv6 is enabled:
Code: 
tracert github.com
Click to expand...
Enabled IPv6 - didnt change anything on Piholes

Google
Code: 
nslookup www.google.co.za
Server:  pi.hole
Address:  192.168.5.212

Non-authoritative answer:
Name:    www.google.co.za
Addresses:  2c0f:fb50:4002:802::2003
          142.251.47.67

Code: 
tracert google.com

Tracing route to google.com [2c0f:fb50:4002:807::200e]
over a maximum of 30 hops:

  1     1 ms     2 ms     2 ms  2c0f::1
  2     *        *        *     Request timed out.
  3     5 ms     4 ms     4 ms  2c0f:f9a8::1:27:11:3
  4     *        *        *     Request timed out.
  5     5 ms     5 ms     5 ms  2c0f:fb50:8322::1
  6     5 ms     5 ms     5 ms  2c0f:fb50:4002:807::200e

Trace complete.

Github
Code: 
nslookup github.com
Server:  pi.hole
Address:  192.168.5.212

Non-authoritative answer:
Name:    github.com
Address:  20.87.245.0

Code: 
 tracert github.com

Tracing route to github.com [20.87.245.0]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  unifi.705 [192.168.5.1]
  2     *        *        *     Request timed out.
  3     4 ms     4 ms     4 ms  100.99.2.194
  4     4 ms     5 ms     4 ms  100.99.8.4
  5     5 ms     4 ms     5 ms  microsoft.ixp.joburg [196.60.8.133]
  6     *        5 ms     5 ms  ae26-0.icr01.jnb21.ntwk.msn.net [104.44.50.86]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     5 ms     5 ms     5 ms  20.87.245.0

Trace complete.

And github.com wont load in any browser (Edge, FF, Brave) - its bizarre. Also having issues with Teams which isnt ideal
 
Mzezman said:
Enabled IPv6 - didnt change anything on Piholes

Google
Code: 
nslookup www.google.co.za
Server:  pi.hole
Address:  192.168.5.212

Non-authoritative answer:
Name:    www.google.co.za
Addresses:  2c0f:fb50:4002:802::2003
          142.251.47.67

Code: 
tracert google.com

Tracing route to google.com [2c0f:fb50:4002:807::200e]
over a maximum of 30 hops:

  1     1 ms     2 ms     2 ms  2c0f::1
  2     *        *        *     Request timed out.
  3     5 ms     4 ms     4 ms  2c0f:f9a8::1:27:11:3
  4     *        *        *     Request timed out.
  5     5 ms     5 ms     5 ms  2c0f:fb50:8322::1
  6     5 ms     5 ms     5 ms  2c0f:fb50:4002:807::200e

Trace complete.

Github
Code: 
nslookup github.com
Server:  pi.hole
Address:  192.168.5.212

Non-authoritative answer:
Name:    github.com
Address:  20.87.245.0

Code: 
 tracert github.com

Tracing route to github.com [20.87.245.0]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  unifi.705 [192.168.5.1]
  2     *        *        *     Request timed out.
  3     4 ms     4 ms     4 ms  100.99.2.194
  4     4 ms     5 ms     4 ms  100.99.8.4
  5     5 ms     4 ms     5 ms  microsoft.ixp.joburg [196.60.8.133]
  6     *        5 ms     5 ms  ae26-0.icr01.jnb21.ntwk.msn.net [104.44.50.86]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     5 ms     5 ms     5 ms  20.87.245.0

Trace complete.

And github.com wont load in any browser (Edge, FF, Brave) - its bizarre. Also having issues with Teams which isnt ideal
Click to expand...
That's crazy, it all looks good. I have zero issues with teams and IPv4 only sites... Very confusing.
 
bHOLDher said:
That's crazy, it all looks good. I have zero issues with teams and IPv4 only sites... Very confusing.
Click to expand...
Yeah - i will spend a bit more time on it tonight to try narrow down the issue but its been a head scratcher - luckily its not mission critical
 
Mzezman said:
Yeah - i will spend a bit more time on it tonight to try narrow down the issue but its been a head scratcher - luckily its not mission critical
Click to expand...
I wonder if you browser will show something helpful in the F12/Dev Tools on the network tab?

Hmmmmmmm just thinking about this now: I wonder if it is an MTU issue?? But I would have guessed you would possibly have MTU issues on the IPv6 side and not on the IPv4 side.
 
bHOLDher said:
Hmmmmmmm just thinking about this now: I wonder if it is an MTU issue?? But I would have guessed you would possibly have MTU issues on the IPv6 side and not on the IPv4 side.
Click to expand...
You might be onto something, as there are known MTU/MSS Clamping related issues with Ubiquity routers.
 
Last edited:
@PBCool I've send you a PM. Getting the same high latency on 2 site-site vpn connections. Please assist.
 
HI All.

Please note, there is a Latency issue with AWS related services in Cape Town.

We are not receiving AWS prefix via CINX (Cape Town internet Exchange) since the 16th, and have Reported this to Amazon.
Service providers who doesn't have an Interconnect with AWS, seems to be affected.

This can also affect games using AWS, such as Valorant and Fortnite EU, etc. with traffic being routed via JHB.

Your patience is much appreciated.
 
CoolEscalator said:
HI All.

Please note, there is a Latency issue with AWS related services in Cape Town.

We are not receiving AWS prefix via CINX (Cape Town internet Exchange) since the 16th, and have Reported this to Amazon.
Service providers who doesn't have an Interconnect with AWS, seems to be affected.

This can also affect games using AWS, such as Valorant and Fortnite EU, etc. with traffic being routed via JHB.

Your patience is much appreciated.
Click to expand...
HI All, This should now be resolved.

@Bleach999
 
CoolEscalator said:
HI, I believe all is sorted with UPnP enabled now?
Please let us know should the issue persist in any way.
Click to expand...
Good day, I had some Nat type issues yesterday even with upnp enabled but couldn't respond due to a power cut shortly after. I haven't had any issues since power has been restored and I think the new IP and upnp fixed my issues
 
UNKWNMS said:
Good day, I had some Nat type issues yesterday even with upnp enabled but couldn't respond due to a power cut shortly after. I haven't had any issues since power has been restored and I think the new IP and upnp fixed my issues
Click to expand...
Thank you for reverting back and confirming.
Perhaps when you encounter the issue again, it's best to also reboot as a troubleshooting step first.

But glad everything is now sorted:)
 
Good day @semaphore @fogbound @Enzo Matrix . Please note, all known area outages are posted on our announcements page - https://coolideas.co.za/announcements. The Fibre line provider has not confirmed any outage in your area. Please log a ticket with our support team on 0105932665 or [email protected].


EDIT: Hi All, please note there was an Issue, that has since been resolved.
Please log a ticket should your line still be down
 
Last edited:
Seems like AWS transit at cinx has some packet loss to Germany.
At least thats what i'm seeing in PUBG (18.157.2.245).
I've setup my smokeping to watch it but thats going to take some time.
Anybody else notice this?
For now i may need to VPN into EU to bypass xD
 
Zassie said:
Seems like AWS transit at cinx has some packet loss to Germany.
At least thats what i'm seeing in PUBG (18.157.2.245).
I've setup my smokeping to watch it but thats going to take some time.
Anybody else notice this?
For now i may need to VPN into EU to bypass xD
Click to expand...
Hi, so we have noticed some peak time loss the to AWS the last few nights, and haver reported it to Amazon Today. (Pending Feedback)
We did make a routing change today from NAPA to CINX (For AWS traffic) to see if it makes any difference.

So far, only seeing minor losses (0.4%) max, but too early to tell as its not peak just yet. (Issue happens between 19:00-22:30)

Zassie said:
(18.157.2.245).
Click to expand...
But will monitor that destination as well to see if I can pick up anything, thanks.

Currently I'm monitoring 52.223.28.81 and 35.71.152.58
 
CoolEscalator said:
Hi, so we have noticed some peak time loss the to AWS the last few nights, and haver reported it to Amazon Today. (Pending Feedback)
We did make a routing change today from NAPA to CINX (For AWS traffic) to see if it makes any difference.

So far, only seeing minor losses (0.4%) max, but too early to tell as its not peak just yet. (Issue happens between 19:00-22:30)


But will monitor that destination as well to see if I can pick up anything, thanks.

Currently I'm monitoring 52.223.28.81 and 35.71.152.58
Click to expand...
Perfect! Thank you so much for the hard work!

Impressive how you guys already picked up an issue and are addressing it!

Both those IP's resolve locally for me, but also going to pop them onto my smokeping instance and see what happens! ^.^
 
Zassie said:
Perfect! Thank you so much for the hard work!

Impressive how you guys already picked up an issue and are addressing it!

Both those IP's resolve locally for me, but also going to pop them onto my smokeping instance and see what happens! ^.^
Click to expand...
Only a pleasure :) feel free to share the results once you pick up something, but if the issue is with AWS as we suspect, CINX change will likely not make a difference. But will share an update should we receive it.

Thus far, it only seems to be CPT.
JHB doesn't seem to show the same symptoms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter