VPN issues with 3G (AT&T using overlapping IP space for DNS)
My primary reason for buying a WiFi model was because I wanted to have all VPN issues resolved for my enterprise by Monday morning after the iPad was released - and I did.
Now comes the 3G model and I am back at square 1. AT&T in their never-ending stupidity has decided to use RFC-1918 IP space for DNS. Specifically 172.16.x.y. At issue is when connecting to an IPSec-VPN using 3G, users have all sorts of issues, mostly with regards to split tunneling.
As it stands, our very large organization will NOT be approving iPad 3G for deployment as a sanctioned device using our VPN Infrastructure.
We tried working with Cisco, but they have no access to Apple's modifications to their client and will not assist in resolving this issue.
Does Apple have a work-around?
The solution would be simple if AT&T would simply use public IP space for DNS. They could simply not advertise the space to anyone but AT&T 3G users.
Ideas?????
Now comes the 3G model and I am back at square 1. AT&T in their never-ending stupidity has decided to use RFC-1918 IP space for DNS. Specifically 172.16.x.y. At issue is when connecting to an IPSec-VPN using 3G, users have all sorts of issues, mostly with regards to split tunneling.
As it stands, our very large organization will NOT be approving iPad 3G for deployment as a sanctioned device using our VPN Infrastructure.
We tried working with Cisco, but they have no access to Apple's modifications to their client and will not assist in resolving this issue.
Does Apple have a work-around?
The solution would be simple if AT&T would simply use public IP space for DNS. They could simply not advertise the space to anyone but AT&T 3G users.
Ideas?????
iPad 3G, iPhone OS 3.1.2