Spontaneous spinach
Expert Member
- Joined
- Nov 17, 2013
- Messages
- 1,394
You got a working vpn for Netflix USA?Yep, my VPNs are up down like yo-yos atm![]()
My net seems to be stable, a little sluggish but stable. Everything better on your end ?
You got a working vpn for Netflix USA?Yep, my VPNs are up down like yo-yos atm![]()
My VPNs are for local support, they seem to be back up except for one site in Q'Town which could well be due to other problems.You got a working vpn for Netflix USA?![]()
My net seems to be stable, a little sluggish but stable. Everything better on your end ?
Ah! You know your stuff , hopefully you can comment on what was the issue when you figure it out.My VPNs are for local support, they seem to be back up except for one site in Q'Town which could well be due to other problems.
Nor going to say the problem is fixed yet as I've been trying to figure out what is stuffed for over an hour - it wasn't dns as I could happily ping the various site firewalls but the vpn's would not connect.

I was still seeing intermittent problems with VPNs in the early evening but all seems fine this am - fingers crossed.Apparently some SAIX DNS was under DOS attack.
TI customers should get better responses from our anycast caching DNS IPs than Google:
105.225.0.1
105.225.0.2
My Internet is dead dead dead , I can't even download a picture from whatsapp.I was still seeing intermittent problems with VPNs in the early evening but all seems fine this am - fingers crossed.
We normally use the default IPs (currently 196.43.54.190 / 196.43.38.190) but I've changed our firewall to the ones you recommend while leaving the the remote sites on default. I'll report back if any problems are experienced.
We are still seeing VPN links falling over for a couple minutes at a time at the remote sites so are slowing moving them to the DNS IPs suggested by ranger which seems to be doing the trick - touch wood.My Internet is dead dead dead , I can't even download a picture from whatsapp.
Keeps failing , how's things on your end ?
Ahh it's probably an issue in Durban , my cousin is also having this issue so i ruled out an error on my line , I noticed a a few people complaining on downdetect.We are still seeing VPN links falling over for a couple minutes at a time at the remote sites so are slowing moving them to the DNS IPs suggested by ranger which seems to be doing the trick - touch wood.
Not sure if this will work for you in Durban or even if it's what causing your problems as our sites were only battling to keep the IPSec VPN tunnels up, no reports received of normal internet hassles.
, thanks for replying! When will this rollout take place ? I switched to the Google dnsNew DSL sessions in the Northern and Southern regions will now get 105.225.0.1 and 105.225.0.2 for DNS in order to mitigate the problems on SAIX DNS.
SAIX is also busy with other mitigations.
Sorry bud, ask for assistance on twitter. They might be slow to respond but they're quite helpful!How is it in this day and age that Telkom's account department has no clue as to issues on the technical side. Considering the tel numbers you have to submit, ID no, and what not on every 6 minute wait for assistance with a line fault report?
We did have not have any Telkom service for 2 weeks, zip nadha, and Telkom gave me 2 x references for fault reports.
Come end of the month - they bill you for a full month of services...are they being opportunistic hoping I won't notice?
But I did....so now I have another ref number for a dispute....Why should I even NEED to register a dispute...if our whole streets phone lines were dead for 2 weeks.
Why are these things not integrated yet into 1 single software system - that flags faults at accounts - and credits their customers till such time their fault is restored...could it be that hard?
Why should I have to wait on the line - at my cost while a customer rep - goes to hear from technical somewhere else - and that takes ages - to find out what and when things went south on my line...when they have job cards linked to telephone numbers?
On the technical side the technology is whizbang - when it works - but man its time you linked your technical system to your accounting system. Instead of hoping for a cash windfall when customers get no service.
How is it in this day and age that Telkom's account department has no clue as to issues on the technical side. Considering the tel numbers you have to submit, ID no, and what not on every 6 minute wait for assistance with a line fault report?
We did have not have any Telkom service for 2 weeks, zip nadha, and Telkom gave me 2 x references for fault reports.
Come end of the month - they bill you for a full month of services...are they being opportunistic hoping I won't notice?
But I did....so now I have another ref number for a dispute....Why should I even NEED to register a dispute...if our whole streets phone lines were dead for 2 weeks.
Why are these things not integrated yet into 1 single software system - that flags faults at accounts - and credits their customers till such time their fault is restored...could it be that hard?
Why should I have to wait on the line - at my cost while a customer rep - goes to hear from technical somewhere else - and that takes ages - to find out what and when things went south on my line...when they have job cards linked to telephone numbers?
On the technical side the technology is whizbang - when it works - but man its time you linked your technical system to your accounting system. Instead of hoping for a cash windfall when customers get no service.
When will this rollout take place ?
I switched to the Google dns
BAM maximum speed!
Can i have the Dns you're using ?On a new seasion. That is because you get it via PPP/IPCP on a new connection only.
Sme happened when I switched from SAIX DNS to our own today when I experienced the problems when testing something on a new line.
(At home I have been using our DNS for many months to test).
Still using the old DNS on automatic here in PE when I tested just now:On a new seasion. That is because you get it via PPP/IPCP on a new connection only.
17:57:47 red GUI hangup
17:53:33 pppd[8841] secondary DNS address 196.43.38.190
17:53:33 pppd[8841] primary DNS address 196.43.54.190
17:53:33 pppd[8841] remote IP address 105.227.2.1
17:53:33 pppd[8841] local IP address 105.229.215.113
17:53:33 pppd[8841] PAP authentication succeeded
17:53:33 pppd[8841] Remote message: Login ok
In the event of a routing issue to Google, nothing is going to work for you.Can i have the Dns you're using ?
Using Google Dns doesn't cause any issues , right ?
I'm not clued up on this
Ahh thanks! I'll set it back to automatic , I'll even try the ones you mentioned in a few post back.In the event of a routing issue to Google, nothing is going to work for you.
Google may not be able to direct you to the non-Google CDNs we host in our network (at least one video streaming CDN, at least one social media CDN, at least one general-purpose CDN) so you may not get the best experience we can give you.
Google may be doing analytics on your DNS queries and correlating them with anything else you do that Google has access to.
You could use us first and Google 2nd, or the other way around.