VPN Access

[jannievanzyl]

I understand the issue with IPv4 what I don't understand is Vodacoms inability to find a workaround that doesn't affect the customer. An easier method would be to only issue public addresses to 3G modems and issue NAT'd to cellphones. Surely that would resolve some of the issue if not most of it. I don't know of anyone that VPN's from or through their cellphone.

Basically what happened is no one planned properly for the depletion of IPv4 addresses on the Vodacom network even though the planet has been running short and ahs been warned for years already.

We're ready to switch to v6. Are you?

[The_Librarian]

I might have IF you had enlightened me
As I was thinking; the client is connecting on their 3G via a VPN to their office.
The VPN is setup through the VC network ( am I OK so far ? )
The problem seems to be on the VC side and their implementation of NAT which is interfering with the VPN IP address ( public and private )
The software problem then is on the customer side ( client=mobile / server=office )
What is the software that is giving the problem and what protocols are running ? ( Does this problem occur on all software implementations ? )

Does this occur on a Cisco network / setup ?

The question about what equipment VC is using still stands.

oops, you're right, I should've elaborated a bit

PPTP VPN requires the use of the GRE protocol. When you run on a NAT'ed IP (as in Vodacom's case) the GRE protocol does not route properly. Without the GRE protocol, PPTP VPN will not work.

OpenVPN should work as it does not require the GRE protocol, but I might be wrong.

[Juggy]

We're ready to switch to v6. Are you?

Yeah, does the handset/modem support it? The dekstop/laptop OS supports it.

[ambo]

if Vodacom implement IPv6, will my users be able to VPN in from an IPv6 IP to an IPv4 VPN server?

The original plan was that there would be no communication between IPv4 sockets and IPv6 sockets. You would have been able to only tunnel one on top of the other.

End user demand has forced the standards bodies to rethink this and you can now reach most IPv4 sites/servers from an IPv6(-only) connection. You need some blackboxes in the network to make this work and these devices are just NATing the traffic. This is unlikely to solve the current NAT issue.

Why don't you just IPv6 enable your server so that it can accept either IPv6 or IPv4 connections?

[ambo]

We're ready to switch to v6. Are you?

COOL! Which APN can I test this on?

I've been doing IPv6 over wifi on my Android phone for a couple of years now with no issues. My next phone will have to support IPv6 on the UMTS side as well. Probably the Galaxy Nexus which has the correct Radio Interface Layer (RIL) capabilities for IPv6 PDP contexts.

footnote: Do any of you realise that MyBroadband has been IPv6 enabled for about a year already?

[ramar]

Jannine,

I have clients who are still having problems. The have been provisioned on the InternetVPN APN and have made the necessary changes. This has improved things as they no longer get 10.x.x.x addresses, but the are still unable to connect to VPN's when they get addresses in the 41.13.x.x range. This is in Joburg, northern suburbs.

Anything else we can do?

[Khalfan]

Does anyone know when this will be sorted out? I have literally 100's of users that are affected by the "little" problem.

I have users in Gauteng, Bloem and CPT that are affected.

hey how ya doing the only thing is can you help me go get VPN software which support Vodacom network

[Khalfan]

Jannine,

I have clients who are still having problems. The have been provisioned on the InternetVPN APN and have made the necessary changes. This has improved things as they no longer get 10.x.x.x addresses, but the are still unable to connect to VPN's when they get addresses in the 41.13.x.x range. This is in Joburg, northern suburbs.

Anything else we can do?

hey how ya doing the only thing is can you help me go get VPN software which support Vodacom network