L2TP or PSEC for Android to pfSense guide?
-
Hi everyone,
I am looking for a step by step guide to setup either L2TP or IPSEC tunnel for an Android phone to pfSense. The Android phone is in a country where users are not able to download certain applications due to geographical limitations of the Playstore. I can do this easily with OpenVPN but phone is not rooted so no OpenVPN and I would like to learn L2TP or IPSEC tunneling as well.
So, once the phone connects via VPN I want it to proxy all it's outbound and inbound traffic through pfSense server which is in USA in order to give Playstore the impression that phone is in USA.
I have been trying to setup L2TP but I am failing and raw logs show this:
Jul 27 14:00:21 l2tps: Incoming L2TP packet from 54.214.89.189 13733 Jul 27 14:00:21 l2tps: L2TP: Control connection 0x2851fd04 terminated: 0 ()
Is there a good video guide for either L2TP or IPSEC with Android phone involved?
Thanks
-
http://doc.pfsense.org/index.php/Mobile_IPsec_on_2.0
Try IPsec
be sure to add a DNS server when you set up your android device. 8.8.8.8 is a good one generally.
also, to get all the traffic to tunnel, add forwarding route 0.0.0.0/0 in the android device VPN setup.L2TP might work, but L2TP is a fast tunnel with NO encryption.
It would probably be a terrible idea for a phone or any mobile device on untrusted / censored networks. -
I can do this easily with OpenVPN but phone is not rooted so no OpenVPN and I would like to learn L2TP or IPSEC tunneling as well.
If the phone is Android 4.x, then root is no longer required for Openvpn.
-
Following up on what thermo said, "Openvpn Connect" requires no root on 4.0 and above.
For below 4.0, IPsec is the way you might need to go. -
This OpenVPN client is far superior on Android 4.0+:
https://play.google.com/store/apps/details?id=de.blinkt.openvpnFor Android 2.x and 3.x, you can use the FEAT OpenVPN client:
http://www.featvpn.com/ -
Hi everyone,
I have set up ipsec mobile client on my android and added dns server and forwarding route into vpn settings.
But my request is still going to destinations on 3G ip
What else I can do ? -
OK - what does your configuration look like?