South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I think it's a CalixAnybody know the type of ONT that Frogfoot uses? It's a black box, no logo's or branding. Pic below...
View attachment 603804
Yup, got the same one. Model 801Gv2I think it's a Calix
@PBCool I can understand there's issues, but please give us a bone here. I have internet but I am becoming concerned with international throughput. My Skype daily Standup was horrible this morning and if it doesn't improve I might have to abort working from home which will mean I can no longer afford to keep CISP as an ISP and will have to go back to using LTE or 3GOn the international side I believe a lot of the recent issues are a combination of things, so for one the Angola cables transit has been a bit of a nightmare to manage. They arent really geared for selective announces etc. Then there are a few networks which seem to be experiencing congestion or even if it isn't congestion related it's still loss at peak times.
There have been a few small issues with the longhaul, we are in the process of changing carriers on it.Just to be clear to everyone here, my frustration with my internet is directed towards Octotel. Its pretty clear to me at least that its congestion on their side.
My frustration with CISP is their lack of support. The only way Octotel will rectify the congestion issue is if I log it with CISP and they put pressure on Octotel to fix it since Octotel don't deal with customers directly. I opened a ticket about it at the end of November, was asked to run an iperf test (I doubt I would have got this response if I didn't ask PBcool to look into it) and was told the results were submitted to the CISP network engineers. That's all I've heard about that. I have no idea if CISP has informed or got in contact with Octotel, I've had 0 feedback since then.
Also the packet loss to JHB from CPT in the evenings. That looks to be on CISPs side too, its also pretty annoying.
As a provider using Angola Cables IP Transit i can confirm trying to do traffic engineering with them is near impossible, on paper they have it mapped out but in reality it doesn't work. On the positive side we haven't seen any major routing problems or throughput problems over their network. Several of the in-country transit providers are deploying content nodes of various types of content, akamai, netflix, more specifically netflix. Netflix generally guides eyeballs to these nodes unless the ixp peering has been engineered, the Angola Cables netflix node sits in Angola, not that that is a problem but it may explain some users bad experiences. Obviously this is an assumption, it would need to be backed up based on the src IP of the netflix traffic.On the international side I believe a lot of the recent issues are a combination of things, so for one the Angola cables transit has been a bit of a nightmare to manage. They arent really geared for selective announces etc. Then there are a few networks which seem to be experiencing congestion or even if it isn't congestion related it's still loss at peak times.
Local stream or via VPN?
We have Netflix clusters in JHB and in CPT so that is quite strange.Local ZA boquet - funny thing though was that I still had connectivity on other devices, just netflix spazzing out.
We have Netflix Akamai and GGC on-net already, which are being preferredAs a provider using Angola Cables IP Transit i can confirm trying to do traffic engineering with them is near impossible, on paper they have it mapped out but in reality it doesn't work. On the positive side we haven't seen any major routing problems or throughput problems over their network. Several of the in-country transit providers are deploying content nodes of various types of content, akamai, netflix, more specifically netflix. Netflix generally guides eyeballs to these nodes unless the ixp peering has been engineered, the Angola Cables netflix node sits in Angola, not that that is a problem but it may explain some users bad experiences. Obviously this is an assumption, it would need to be backed up based on the src IP of the netflix traffic.
Another Angola gripe@PBCool , something is wrong with the route to nl.newsdemon.com. I only noticed this today.
1.|-- OPNsense.local 0.0% 10 0.5 0.5 0.4 0.5 0.0
2.|-- 102.132.137.1 0.0% 10 2.5 3.2 2.2 6.5 1.2
3.|-- 154.0.3.97 0.0% 10 6.3 7.3 2.7 29.7 8.1
4.|-- 154.0.5.2 0.0% 10 1.5 1.5 1.3 1.6 0.0
5.|-- 154.0.5.130 0.0% 10 1.6 1.5 1.4 1.7 0.0
6.|-- 154.0.5.151 0.0% 10 1.6 1.8 1.6 2.0 0.0
7.|-- 154.0.1.246 0.0% 10 19.1 19.1 18.9 19.3 0.0
8.|-- 154.0.4.162 0.0% 10 23.4 19.6 18.8 23.4 1.3
9.|-- 102.130.64.13 0.0% 10 20.4 20.4 20.3 20.6 0.0
10.|-- pe2-nc029.ang.sgn.as37468.angolacables.ao 0.0% 10 55.0 55.5 55.0 58.5 1.0
11.|-- 170.238.232.149 50.0% 10 116.0 115.9 115.7 116.0 0.0
12.|-- pe1-nc014.br.ftz.as37468.angolacables.ao 0.0% 10 114.4 114.2 114.0 114.4 0.0
13.|-- pe2-nce022.br.spa.as37468.angolacables.ao 0.0% 10 159.8 160.0 159.7 160.5 0.0
14.|-- pe1-nce014.br.spa.as37468.angolacables.ao 10.0% 10 157.8 157.7 157.6 158.0 0.0
15.|-- as12989.saopaulo.sp.ix.br 0.0% 10 247.5 250.9 247.4 281.2 10.6
16.|-- xe-1-0-0.r3.ny.hwng.net 0.0% 10 261.7 262.4 261.5 263.5 0.3
17.|-- 6-2.r2.ny.hwng.net 0.0% 10 263.4 261.9 261.5 263.4 0.5
18.|-- unknown.hwng.net 0.0% 10 261.6 262.0 261.6 262.5 0.0
19.|-- e3-4.r2.dc.hwng.net 0.0% 10 268.7 268.6 268.3 268.9 0.0
20.|-- unknown.hwng.net 0.0% 10 268.9 268.7 268.3 269.0 0.0
21.|-- 1-1.r2.am.hwng.net 0.0% 10 268.5 271.9 268.5 279.7 4.1
22.|-- 81.171.92.234 10.0% 10 268.6 269.4 268.6 272.7 1.1
![]()
Another Angola gripe, try now?
Blanket statements like this saying everyone has an issue is just wrong, there are so many people without issues including myself, but only negativity is shown on forums. If you feel you are getting a bad service vote with your wallet. My 0.002 cents
Its a calix 801 or 803, used in open access networks, just a layer two device, no layer 3.Anybody know the type of ONT that Frogfoot uses? It's a black box, no logo's or branding. Pic below...
View attachment 603804