I have a new ASA 5515 that I want to use for IPSec IKEv2 VPN from an Android AnyConnect 3.0 client.
Has anyone go this to work?
I get this log "TCP access denied by ACL from 220.127.116.11/47170 to Outside:18.104.22.168/443" when I try to connect.
I've gone throught the ASA configuration many times and I tried everything.
Is this even possible?
It looks like client services are not enabled on.
Plus port /443 is the initial SSL connection - IKEv2 (as IKEv1) would start on udp/500.
Open up a TAC case this should work without too many challanges - provided you already have a proper profile imported to your anyconnect.
Why do I need to have client services enabled? I don't want or need any of them.
I am using a client profile created using ASDM and the ASA and exported. I'm not sure how to tell if its proper. But, I have reviewed the profile setting and they look correct. Does a client profile specify IPSec IKEv2 in it? I don't see it.
If I enable client services on the 'outside' interface, I get certificate errors. First the certificate from the ASA is not trusted. If I say "install and continue" then I get a certificate validation error. From that point on, I get only the certificate validation error. "This connection requires a client certifiate, but no matching certifcate could be found."
Perhaps I need to revisit certifcates.
Strictly speaking you do not need client services.
Client services are not part of IKEv2 framework. In ASA + Anyconnect combo we use client services to update AC client from headend and push profile updates.
Looks like you're requesting user certificates too, but that's besides the point.
I would first of all check if you're initiating IKEv2 at all, I assume you're using whatever you configured in "
From profile's perspective there should be mention
- "HostAddress" to specify where the headend is - IP or hostname
- "Protocol" - IPsec. IKEv2 is used - no support for IKEv1 on AC.
You can find an example profile here:
I would also take care that profile on ASA and client are exactly the same (copy/paste/import).
I've tried following that example. The end result is a client profile that cannot be saved or editted from ASDM. There are some XML errors. I don't have the exact error text, unfortunately. However, If I manually create a client profile, its does not have a
I'm going to try to edit the client profile and import it into the ASA and import it into the Android AnyConnect.
I'm also going to upgrade to 9.01 on the ASA and ASDM 7.02. But, I'll do that later.
I left the client profile in the ASA (it can't be editted, but I was able to apply). Not sure if its being used or not. I took the updated client profile to the Android and imported it into AnyConnect. I get this error on the Android: "VPN Server could not parse request." The ASA says: "Local:22.214.171.124:500 Remote:126.96.36.199:43648 Username:Unknown Negotiation aborted due to ERROR: The peer's KE payload contained the wrong DH group."
First, its port 500, so YAY its IPsec.
But what is failing?
Well KE and DH stands for diffie hellman group.
I would still enabled debugging on ASA and export logs from Android to see what is being used.
I think I'm going to update to 9.01 on the ASA and ASDM 7.02 at this time.
I also noticed that I must have at least one AnyConnect Client software image installed. None of them are appropriate (I'm using Andorid client) but I must have at least one or I can't create client profiles properly.
Maybe the new levels will be more functional for me.
That could be agood idea (upgrade) although I'm not sure if 9.0 is yet ready for prime time.
ALthough the IKEv2 Remote access wizard in ASDM should sort out the ASA config for you.
Indeed you need Anyconnect image AND Anyconnect mobile license to succeed.
9.01 VPN wizard still creates a faulty client profile with the same XML error regarding "PrimaryProtocol".
Do I need updated anyconnect client images? I'll try that.