[2.2] Mobile clients not connecting anymore

jalonergan

I am having the same issues with IPSEC and 2.2. Most of the Pfsense online guides are for versions less than 2.1.5. Does anyone have a step by step guide that they can post for a verified working configuration utilizing PSEC on 2.2 with Shrew Client and Android 4.4 as the clients. Thanks!

Joe

eri--

Please provide the logs to analyze this.
Also read the RELEASE notes about the new update and changes with things to conisder.

pinoyboy

Moved…

eri--

Please open a new thread for your issue but probably its related that you need on pfSense side to set the phase2 to 0.0.0.0/0 for the client.
It is on the release notes.

HaburGate

@ermal:

Please open a new thread for your issue but probably its related that you need on pfSense side to set the phase2 to 0.0.0.0/0 for the client.
It is on the release notes.

Is this under the Local Network field? Currently I have it set to "LAN Subnet."

maxxer

I managed to install a fresh new 2.2, configure using this howto, and captured this log. I hope this can help debug.
Let me know if you need further debugging.
thanks for the help.

maxxer

I made some searches and tests myself.
First I found a possible issue with missing leftsendcert=always, but doesn't seem to apply to this problem.
Then I found an old thread about android and 2.2, and that seem to matter!

I had to do two changes:

on the server set IPSec mobile to main mode
on the Android client remove the IPSec identifier field (leave blank)

This way the VPN connection is established.
Can anyone else please confirm?

Sadly this way I have a regression: Ubuntu client won't connect anymore, it seems it's starting an aggressive mode connection thus fails…

HaburGate

Hi Maxxer, can you post a screenshot of your Phase 1 and Phase 2 screens? (with applicable info blacked out). Fighting the same issue here, trying to get Android and iPhone clients connected.

maxxer

@vocatus:

Hi Maxxer, can you post a screenshot of your Phase 1 and Phase 2 screens? (with applicable info blacked out). Fighting the same issue here, trying to get Android and iPhone clients connected.

attaching here a working configuration for Android. Tested just with one device running Lollipop. NOT working with Ubuntu (seems it doesn't like main mode, just aggressive).
IKE mode works both in auto, v1 or v2. Just make sure to leave blank group identifier on the phone configuration.

ipsecphase1.png_thumb
ipsecphase2.png_thumb

sserg18

here is my config. works on mac os, ios 7.1.1, ios 8.0. cisco ipsec vpn

ipsec-2s.jpg_thumb
ipsec-3s.jpg_thumb
ipsec-4s.jpg_thumb
ipsec-6s.jpg_thumb
ipsec10s.jpg_thumb

sserg18

@maxxer:

@vocatus:

Hi Maxxer, can you post a screenshot of your Phase 1 and Phase 2 screens? (with applicable info blacked out). Fighting the same issue here, trying to get Android and iPhone clients connected.

attaching here a working configuration for Android. Tested just with one device running Lollipop. NOT working with Ubuntu (seems it doesn't like main mode, just aggressive).
IKE mode works both in auto, v1 or v2. Just make sure to leave blank group identifier on the phone configuration.

if we make Key Exchange version = auto
then Negotiation mode - switches from agressive, mode main.

In this case mac os ios not work.

Phoenix

@maxxer:

I had to do two changes:

on the server set IPSec mobile to main mode

on the Android client remove the IPSec identifier field (leave blank)

Some time ago, I stumbled upon, that leaving the IPSec identifier blank android will initiate with main mode, having something in this field will switch it to aggressive mode. This still applies for android 5.0

dharrigan

Hi,

I can confirm too that by setting mode to main and removing the ipsec identifier, I'm able to connect to my VPN again using Android with Lollipop.

So, is this a bug with Android and nothing we can do on pfSense, or is this something that we can fix on pfSense?

Now then, will this configuration work for iOS….. :-)

-=david=-

eri--

Do you see on the logs anything related to identity?

This seems like android is not sending the proper identity as configured hence it works when left blank because it sends its ip.

dharrigan

Hi,

I don't think it is only that tbh.

First, I enabled "main" on my IPsec phase 1 entry, then removed from my Android the IPSec Identifier. I was able to connect successfully on Android.

I then disconnected my Android, enabled "aggressive" on my IPsec phase 1 entry, kept the IPSec Identifier missing on Android. I was unable to connect successfully.

Switching back to "main" allowed my Android to reconnect again.

Then:

Keeping "main" on my IPsec phase 1 entry, but this time filling in the IPSec identifier in Android to match the user distinguished name for my peer identifier doesn't result in a successful connection.

Changing to "aggressive", keeping the IPsec identifier in Android doesn't result in a successful connection.

Therefore, it appears to me (at least) that the only way I can get Android to connect is to enable "main" on pfSense and remove the IPsec identifier from Android's configuration.

Hope this helps!

-=david=-

eri--

Without logs no since i do not have an andorid device!

dwood

I finally gave on Ipsec after iOS and PC clients could not connect after 2.2. I spent a few hours trying to get it working…got connections, but never figured out how to fix LAN routing.

I gave OpenVPN a try and was pleasantly surprised after 15 minutes of reading/wizards to get both iOS and PC clients connected and routing perfectly. Maybe the easiest VPN configuration ever. Thanks to the pfsense crew for making it so easy :-)

maxxer

@ermal:

Do you see on the logs anything related to identity?

This seems like android is not sending the proper identity as configured hence it works when left blank because it sends its ip.

This is the full log taken during my tests.

Given this, isn't it better to work in main mode? Or does removing the identifier creates a security problem? thanks
[tough this is not yet an acceptable solution to me, I cannot connect using Ubuntu's network manager strongswan]

eri--

This is quite clear here


Feb 10 13:55:51 pfSense charon: 15[IKE] <con1|113>no EAP key found for hosts 'C=US, ST=State, L=Locality, O=pfSense webConfigurator Self-Signed Certificate, E=admin@pfSense.localdomain, CN=pfSense-54d4d54a8beac' - 'admin'
Feb 10 13:55:51 pfSense charon: 15[IKE] no EAP key found for hosts 'C=US, ST=State, L=Locality, O=pfSense webConfigurator Self-Signed Certificate, E=admin@pfSense.localdomain, CN=pfSense-54d4d54a8beac' - 'admin'
Feb 10 13:55:51 pfSense charon: 15[IKE] <con1|113>EAP-MS-CHAPv2 verification failed, retry (1)</con1|113></con1|113>

Your ids are not matching with the ones you entered under EAP on pre-shared secrets.

maxxer

@ermal:

This is quite clear here


Feb 10 13:55:51 pfSense charon: 15[IKE] <con1|113>no EAP key found for hosts 'C=US, ST=State, L=Locality, O=pfSense webConfigurator Self-Signed Certificate, E=admin@pfSense.localdomain, CN=pfSense-54d4d54a8beac' - 'admin'
Feb 10 13:55:51 pfSense charon: 15[IKE] no EAP key found for hosts 'C=US, ST=State, L=Locality, O=pfSense webConfigurator Self-Signed Certificate, E=admin@pfSense.localdomain, CN=pfSense-54d4d54a8beac' - 'admin'
Feb 10 13:55:51 pfSense charon: 15[IKE] <con1|113>EAP-MS-CHAPv2 verification failed, retry (1)</con1|113></con1|113>

Your ids are not matching with the ones you entered under EAP on pre-shared secrets.

sorry for mixing things up, this must be the test I made from Ubuntu (strongswan client doesn't allow to enter a PSK)