VPN Access

Indeed from a hacking point of view yes, but from an idiot doing a denail of service attack on you being blocked by your firewall... not!

That traffic still has to hit your firewall and get blocked.
 
Indeed from a hacking point of view yes, but from an idiot doing a denail of service attack on you being blocked by your firewall... not!

That traffic still has to hit your firewall and get blocked.
I've used the 'unrestricted' APN on a couple of SIMs since about 2007 and never had such a problem. If you are worried about high bills, make sure you only use pre-paid SIMs.
 
This change by Vodacom has left our company with a major problem. We are in construction and use most of our 3G connections with a combination of Huawei B683's and Hauwei B970b 3G routers. They are hooked up to a Cisco firewall unit to create a tunnel thru to our office. Now all of a sudden with this change they will just not connect. We have figured out the 41.x.x.x and 10.x.x.x issue, however this is transparent to the user and they cannot even access the Huawei units as all their traffic is tunneled thru to Head Office via the VPN, no internet breakout for them on their network. Also one of our directors are very unhappy as his VPN is only working intermittently from his 3G USB Stick.

Surely Vodacom should have let their customers know about this changes.

Can someone from Vodacom please paste the easiest way to get this resolved. From what I understand fo the unrestricted APN is it will allow traffic into that IP as well, which could cause high bills. Vodacom actually has you sign documents for this. Aslo I have about 25 sims like this.

Call 155 and get the InternetVPN APN provisioned on the SIMs. Then change the settings on the various terminals to use the InternetVPN APN.
 
Has anyone actually got the InternetVPN APN setup?
I has told by Vodacom that the InternetVPN APN has been discontinued when the Unrestricted APN was introduced.
No apparently we need to get out own private APN.

This is getting beyond funny with the amount of phone calls I get saying VPN doesn't work.

Wonder if we shouldn't start buying MTN 3G cards instead.
 
Has anyone actually got the InternetVPN APN setup?
I has told by Vodacom that the InternetVPN APN has been discontinued when the Unrestricted APN was introduced.
No apparently we need to get out own private APN.

This is getting beyond funny with the amount of phone calls I get saying VPN doesn't work.

Wonder if we shouldn't start buying MTN 3G cards instead.
Years ago we did not have enough public IP's so we had to use NAT and to overcome the VPN problem, created the InternetVPN APN.

Then we got a crapola allocation of IP's (thanks Ambo!) and could retire the InternetVPN APN.

Unfortunately we're now back to square one and have run out of public IP's, so it's back to NAT and thus the InternetVPN APN got reintroduced in the last week or two.

So you might run into someone who remember the InternetVPN APN and do not yet know it's back. Which it is.

Just insist you want it and if you get any grief send them to me.
 
Years ago we did not have enough public IP's so we had to use NAT and to overcome the VPN problem, created the InternetVPN APN.

Then we got a crapola allocation of IP's (thanks Ambo!) and could retire the InternetVPN APN.

Unfortunately we're now back to square one and have run out of public IP's, so it's back to NAT and thus the InternetVPN APN got reintroduced in the last week or two.

So you might run into someone who remember the InternetVPN APN and do not yet know it's back. Which it is.

Just insist you want it and if you get any grief send them to me.

Thanks,

I will.
 
We have a dozen or so Gauteng VPN users and, in addition to the 10.x.x.x range, no one can connect when they receive an address in the 41.13.x.x range. I've tested this extensively and can confirm the problem. Is this a known issue? Will switching to the InternetVPN APN solve the problem?
 
We have a dozen or so Gauteng VPN users and, in addition to the 10.x.x.x range, no one can connect when they receive an address in the 41.13.x.x range. I've tested this extensively and can confirm the problem. Is this a known issue? Will switching to the InternetVPN APN solve the problem?

Can you give more info please:

- Could they connect in the past, but now cannot connect?
- Can they connect with other networks, i.e. is this only on VC?
- You sure the PC setup is correct?
- Do you use non-standard ports, etc?
 
Can you give more info please:

- Could they connect in the past, but now cannot connect?
- Can they connect with other networks, i.e. is this only on VC?
- You sure the PC setup is correct?
- Do you use non-standard ports, etc?

Thanks for the prompt reply, Jannie.

1. Yes, they could connect before - this problem has arisen in the past few weeks.
2. We only have VC 3G. Just to be clear - all can connect to the VC network, it's just when users are allocated an address in the 10.x.x.x or 41.13.x.x range that they cannot establish a VPN connection to our network. Other IP ranges eg 41.23.x.x work fine. This is not to say that there are not other ranges that will not allow a VPN connection - it's just that 41.13.x.x comes up so often.
3. Yes, I have checked this. As I mentioned earlier - the VPN connection does work, just not on the 41.13.x.x range.
4. Yes, completely standard - port 1723 (PPTP)
 
Can you give more info please:

- Can they connect with other networks, i.e. is this only on VC?

Further to my previous reply, I have spoken to several of the users and two of them use their personal MTN 3G modems when they cannot establish a VPN connection with the work issued VC modems - they can always connect via MTN.
 
Then we got a crapola allocation of IP's (thanks Ambo!) and could retire the InternetVPN APN.

Unfortunately we're now back to square one and have run out of public IP's, so it's back to NAT and thus the InternetVPN APN got reintroduced in the last week or two.
No luck yet with getting another allocation?
 
Thanks for the prompt reply, Jannie.

1. Yes, they could connect before - this problem has arisen in the past few weeks.
2. We only have VC 3G. Just to be clear - all can connect to the VC network, it's just when users are allocated an address in the 10.x.x.x or 41.13.x.x range that they cannot establish a VPN connection to our network. Other IP ranges eg 41.23.x.x work fine. This is not to say that there are not other ranges that will not allow a VPN connection - it's just that 41.13.x.x comes up so often.
3. Yes, I have checked this. As I mentioned earlier - the VPN connection does work, just not on the 41.13.x.x range.
4. Yes, completely standard - port 1723 (PPTP)

1. How do you check the IP? with ifconfig or a 'whatsmyip' type of web site.
2. Which area are these guys that battle with the 41.13 range?
 
1. How do you check the IP? with ifconfig or a 'whatsmyip' type of web site.
2. Which area are these guys that battle with the 41.13 range?

1. checkip.dyndns.org
2. Recent complaints from Linbro Park, Sandringham and Johannesburg South. I can compile a more detailed list if it will help.
 
So we managed to get one SIM switched over the the InternetVPN APN for testing, but it has not made a difference according to the user.
They are still not able to connect to our VPN.
 
So we managed to get one SIM switched over the the InternetVPN APN for testing, but it has not made a difference according to the user.
They are still not able to connect to our VPN.

Are you sure they switched over properly? You need the SIM to be provisioned by Vodacom and then you need to change the APN setting on his device.

Did you do both? What IP do you get with ipconfig.
 
1. checkip.dyndns.org
2. Recent complaints from Linbro Park, Sandringham and Johannesburg South. I can compile a more detailed list if it will help.

You cannot use a web-based IP checker as it'll report the public side of the NAT.

Rather do an ipconfig on the actual device.
 
Top
Sign up to the MyBroadband newsletter
X