Frogfoot - Western Cape

I am still having issues with my frogfoot (via Vox) connection since the outage.

Convinced there is something up with the DNS. Maybe there is a firewall that blocking DNS traffic or a new network device that still has default IP (some have 1.1.1.1 default).
Have had them reset the connection on their side a few times, bounced my ONT and router countless times.
Then I change my DNS to use Quad and it kinda works for a while and then Quad DNS stops working and Google works for a bit, then Cloudflare starts working for a while = rinse repeat....

Apple TV does not work at all. DSTV Stream works sometimes, but keeps disconnecting. Some sites do not work.

Anyone having similar issues?

EDIT:
Got it working at the moment with Cloudflare DNS over TLS
Lets see how long it lasts
I had similar to you re "DSTV Stream works sometimes, but keeps disconnecting."

For me, it worked (once I was logged in), but would disconnect (ie. log me out) every time after I watched an episode of something, then left that screen to exit back to the main menu / home within the app.

I put it down to a screw up from a DStv update, but now you've got me thinking - maybe it was Frogfoot, though I use 1.0.0.1 as my primary DNS, and 1.1.1.1 as secondary.

Did the same at the time I was still using DStv stream, which was up to the end of November '24 ; I cancelled after that due to the frustration of it all.

I don't use anything Apple, but you'd think if Apple TV was the problem, more people would experience what you are.

I'm with Axxess, so again, possible that Frogfoot as FNO is the issue and not Vox as ISP (in your case)?

Hope you get it sorted ; I fortunately only had the one issue, with DStv Stream, (but) both on Android smartphone & Android TV re always logging me out of the app.
 
I am still having issues with my frogfoot (via Vox) connection since the outage.

Convinced there is something up with the DNS. Maybe there is a firewall that blocking DNS traffic or a new network device that still has default IP (some have 1.1.1.1 default).
Have had them reset the connection on their side a few times, bounced my ONT and router countless times.

Can't reach cloudflare DNS (1.1.1.1)
View attachment 1787365


Can't reach Google DNS (8.8.8.8)
View attachment 1787366

CAN reach Quad DNS (9.9.9.9) - for a bit anyway
View attachment 1787367

Then I change my DNS to use Quad and it kinda works for a while and then Quad DNS stops working and Google works for a bit, then Cloudflare starts working for a while = rinse repeat....
Apple TV does not work at all. DSTV Stream works sometimes, but keeps disconnecting. Some sites do not work.

Anyone having similar issues?

EDIT:
Got it working at the moment with Cloudflare DNS over TLS
Lets see how long it lasts

And since yesterday Google DNS is the only responder

Cloudflare
1737011315675.png

Google
1737011364010.png

Quad9
1737011399544.png
 
Still having issues - numerous calls to Vox / FF -no dice. Waiting for the latest port reset

I did, however, notice something - not sure if related.

When one of the DNS's servers are not reachable via ping (only tried CloudFlare so far - only one that has been down since this discovery), I ping with very small packets and it seems to work!?

1737624036880.png

Could it be a firewall issue on some route?

Normal size ping works to google as normal

1737624166859.png
 
You can try an MTU size test and ask your isp what it should be.
Thanks - am very familiar with the MTU chaos and havetried lots of different ones here.

Using both ping and MTUPath for my tests, across multiple devices (all PC's / laptops on 1500)
Generally the tests suggest it should be 1480, but I also interrogate hops along the traceroute path and sometimes it is a bit less.
Tried setting it to the lowest ones along the various routes as well.

Tried 3 different routers, FF Microtik, Netgear Orbi, Cudy Mesh - all have the same issue so it must be the line.

Logged several tickets, calls to Vox support for FROGFOOT to reset / reprovision my port / line - every time this information gets misintepreted at Vox end. Other day the FF engineers arrived to replace the ONT - when asked why they said that is what Vox told them to do, and gave them none of the other information I have been logging.

So bored of this....
 
My life as a picture

1737891744084.png

Even going to MyBB (and most sites) - first attempt : "Cannot reach site", then browser auto refreshes and voila.
Been a bit better since last night but still struggling first load misses and some sites listed below just don't work at all
  • Banking apps (only on mobile devices - differenent devices, different banks)
  • 2FA on almost anything
  • DSTV
  • Apple TV
  • And often with DNS as displayed on the picture above
The little red spike every hourish is concerning and noticeable when streaming -disconnect.
Interestingly, when the DNS above goes RED, you cannot ping it with a normal packet size, but if you ping with say a 5 byte packet, it works., at that point MTUpath also reports a MTU blackhole to the DNS not reachable by traditional PING
 
Last edited:
If you are able I'd advise everyone to move off Vox/FF network. Absolutely trash network with always attitude of its not us its you. Its clear to me that either Vox planning on something or taking way too much out of the equation to maintain and upgrade their existing network.
 
Still having issues - numerous calls to Vox / FF -no dice. Waiting for the latest port reset

I did, however, notice something - not sure if related.

When one of the DNS's servers are not reachable via ping (only tried CloudFlare so far - only one that has been down since this discovery), I ping with very small packets and it seems to work!?

View attachment 1790373

Could it be a firewall issue on some route?

Normal size ping works to google as normal

View attachment 1790374
PATHPING.EXE -p 100 -q 250 1.1.1.1
Let's see where it goes
 
My life as a picture

View attachment 1791077

Even going to MyBB (and most sites) - first attempt : "Cannot reach site", then browser auto refreshes and voila.
Been a bit better since last night but still struggling first load misses and some sites listed below just don't work at all
  • Banking apps (only on mobile devices - differenent devices, different banks)
  • 2FA on almost anything
  • DSTV
  • Apple TV
  • And often with DNS as displayed on the picture above
The little red spike every hourish is concerning and noticeable when streaming -disconnect.
Interestingly, when the DNS above goes RED, you cannot ping it with a normal packet size, but if you ping with say a 5 byte packet, it works., at that point MTUpath also reports a MTU blackhole to the DNS not reachable by traditional PING
Perhaps keep a traceroute on hand when it works, and do another when it doesn't. Should give you an idea where things go belly up. It could be backhaul flapping somewhere.
 
Perhaps keep a traceroute on hand when it works, and do another when it doesn't. Should give you an idea where things go belly up. It could be backhaul flapping somewhere.
Thanks - tried this. when it works, it goes all the way. when it does not it never gets to vox.

Not working - both google and Cloudflare
1738043349768.png

Working today- but only with Quad9

1738043448555.png
 
Thanks for the reminder about PathPing - had not seen that in a V long time.

I think the problem is obvious here.

1738080288798.png

1738080574215.png

Now to get Vox / Frogfoot to action... 😬
 
Last edited:
My experience with Vox x Frogfoot has been dismal in the Western Cape.
I have a client, who migrated from Vox Premium Business to Vox Business Standard.
They are now spinning me a story saying that it takes time to 'create a new path for the fibre on the back-end'

Opinion from those in the know @r00igev@@r / @PBCool ?
 
My experience with Vox x Frogfoot has been dismal in the Western Cape.
I have a client, who migrated from Vox Premium Business to Vox Business Standard.
They are now spinning me a story saying that it takes time to 'create a new path for the fibre on the back-end'

Opinion from those in the know @r00igev@@r / @PBCool ?
Makes no sense. The only thing I could think of may be based on SLAs. Does Premium have multiple path while Standard doesn't kind of thing?
 
Makes no sense. The only thing I could think of may be based on SLAs. Does Premium have multiple path while Standard doesn't kind of thing?
Potentially has a route for failover as it has a better SLA.
Account Manager: 'it is out of Vox hands now and it is the FNO that is causing the delay'
1738567695912.png

At the same time this dude is trying to sell me other services, like I dont know they are both owned by Vivica
 
My experience with Vox x Frogfoot has been dismal in the Western Cape.
I have a client, who migrated from Vox Premium Business to Vox Business Standard.
They are now spinning me a story saying that it takes time to 'create a new path for the fibre on the back-end'

Opinion from those in the know @r00igev@@r / @PBCool ?
Yes. I've seen installations in the WC where they use DFA be difficult to change.
If available install an alternative solution using either Openserve or Octatel and manage it using SD-WAN. When that is in place you can fix the Frogfoot path without it impacting business services and continuity.
Two paths even where one is not that good is always better than one.
 
Top
Sign up to the MyBroadband newsletter
X