HT204684: Unable to resolve unicast DNS names that end in .local in iOS

Learn about Unable to resolve unicast DNS names that end in .local in iOS

Lucifer_123

Level 1 (0 points)

Q: Split tunneling not working with IPSEC Client on iPad/iPhone

I am able to connect fine from iPhone using IPSEC VPN Client to Cisco IOS Router. On the Router we have defined several internal networks in the split tunnel access-list. Now after I am connected, I am able to access ONLY the first internal network defined on the split-tunnel ACL. Internal n/w on subsequent ACL's are not reachable.

If I configured 'tunnel-all' on Router, everything works fine. But I do not want iphone/ipad user to access Internet using my Router's ISP.

This works fine from Windows based PC.

Any insight will be helpful.

Regards.

iPhone 4, iOS 5.1.1

Posted on Jun 5, 2012 1:34 AM

I have this question too

Q: Split tunneling not working with IPSEC Client on iPad/iPhone

All replies

Helpful answers

by petercthomas,

petercthomas Aug 20, 2012 4:50 AM in response to Lucifer_123
Level 1 (0 points)

Aug 20, 2012 4:50 AM in response to Lucifer_123

According to one VPN manufacturer, iOS does not support split-tunneling on Apple devices. All traffic must be passed through VPN end-point.

Very frustrating!

Snipet taken from online support: http://www.watchguard.com/help/docs/wsm/11_XTM/en-US/index.html#en-US/mvpn/ipsec /mvpn_ipsec_ios_vpn_c.html

Select Yes, force all Internet traffic to flow through the tunnel..
This configures the tunnel for default-route VPN. The VPN client on the Mac OS X or iOS device does not support split tunneling.
Reply options

Link to this post

HT204684: Unable to resolve unicast DNS names that end in .local in iOS

Q: Split tunneling not working with IPSEC Client on iPad/iPhone

All replies Helpful answers

by petercthomas,

All replies

Helpful answers