<div dir="ltr">Hi,<div><br></div><div>I'm new to the world of strongswan and vpns in general, so I apologize if this is answered elsewhere. I inherited a strongSwan box running Linux strongSwan U5.7.2/K4.14.177-139.253.amzn2.x86_64. The other end is a Cisco ASA5585X. The connection was up and running a few days ago, but I've been trying to get auto=route working (it was previously auto=start) and that caused the tunnel to go up/down a couple times. Now the tunnel will not establish a connection. To me, it seems like it's the phase 2 establishment that is failing, but I'm curious if someone could help clear up what is going on or which part is failing?</div><div><br></div><div>My understanding (waiting for verification) is that the configured settings for the tunnel from the cisco side are:</div><div><br></div><div>Phase 1<br> Encryption algorithm: AES-256<br> Hash algorithm: SHA-512<br> DH Group: 14<br> Lifetime: 28800 (seconds)<br><br>Phase 2:<br> Mode: IKE V2 Tunnel<br> ESP Encryption algorithm: AES-256<br> ESP Hash algorithm: SHA-512<br> PFS: DH Group 14<br> Lifetime: 3600 (seconds)<br></div><div><br></div><div>I have the following ipsec.conf file for the tunnel:</div><div><br></div><div>config setup<br> # strictcrlpolicy=yes<br> # uniqueids = no<br> charondebug="ike 2, knl 2,esp 2, cfg 2, chd 2, lib 2, net 2"<br><br>conn %default<br> ikelifetime=480m<br> keylife=60m<br> rekeymargin=3m<br> keyingtries=1<br> keyexchange=ikev1<br> authby=secret<br><br>conn FOO<br> leftid=205.251.242.103<br> left=172.30.101.187<br> leftsubnet=<a href="http://205.251.242.103/32">205.251.242.103/32</a><br> leftupdown=/tmp/vpn/firewall-rules.sh<br> right=176.32.98.166<br> rightsubnet=<a href="http://104.40.92.107/32">104.40.92.107/32</a><br> ike=aes256-sha512-modp2048!<br> keyexchange=ikev2<br> esp=aes256-sha2_512-modp2048!<br> rekeymargin=9m<br> type=tunnel<br> compress=no<br> authby=secret<br> auto=route<br> keyingtries=%forever<br> forceencaps=yes<br> mobike=no<br></div><div><br></div><div><br></div><div>ipsec statusall gives the following:<br><br></div><div>Status of IKE charon daemon (strongSwan 5.7.2, Linux 4.14.177-139.253.amzn2.x86_64, x86_64):<br> uptime: 19 hours, since May 08 18:56:20 2020<br> malloc: sbrk 1884160, mmap 0, used 828960, free 1055200<br> worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 0<br> loaded plugins: charon pkcs11 tpm aesni aes des rc2 sha2 sha1 md4 md5 mgf1 random nonce x509 revocation constraints acert pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem openssl gcrypt fips-prf gmp curve25519 chapoly xcbc cmac hmac ctr ccm gcm curl attr kernel-netlink resolve socket-default farp stroke vici updown eap-identity eap-sim eap-aka eap-aka-3gpp eap-aka-3gpp2 eap-md5 eap-gtc eap-mschapv2 eap-dynamic eap-radius eap-tls eap-ttls eap-peap xauth-generic xauth-eap xauth-pam xauth-noauth dhcp led duplicheck unity counters<br>Listening IP addresses:<br> 172.30.101.187<br>Connections:<br> FOO: 172.30.101.187...176.32.98.166 IKEv2<br> FOO: local: [205.251.242.103] uses pre-shared key authentication<br> FOO: remote: [176.32.98.166] uses pre-shared key authentication<br> FOO: child: <a href="http://205.251.242.103/32">205.251.242.103/32</a> === <a href="http://104.40.92.107/32">104.40.92.107/32</a> TUNNEL<br>Routed Connections:<br> FOO{1}: ROUTED, TUNNEL, reqid 1<br> FOO{1}: <a href="http://205.251.242.103/32">205.251.242.103/32</a> === <a href="http://104.40.92.107/32">104.40.92.107/32</a><br>Security Associations (0 up, 0 connecting):<br> none<br></div><div><br></div><div><br></div><div>Sending traffic to 104.40.92.107 does not bring the tunnel up. If I try to bring the tunnel up manually using ipsec up FOO, I get the following:<br><br>initiating IKE_SA FOO[1] to 176.32.98.166<br>generating IKE_SA_INIT request 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) N(FRAG_SUP) N(HASH_ALG) N(REDIR_SUP) ]<br>sending packet: from 172.30.101.187[500] to 176.32.98.166[500] (464 bytes)<br>received packet: from 176.32.98.166[500] to 172.30.101.187[500] (599 bytes)<br>parsed IKE_SA_INIT response 0 [ SA KE No V V N(NATD_S_IP) N(NATD_D_IP) CERTREQ N(FRAG_SUP) V ]<br>received Cisco Delete Reason vendor ID<br>received Cisco Copyright (c) 2009 vendor ID<br>received FRAGMENTATION vendor ID<br>selected proposal: IKE:AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/MODP_2048<br>local host is behind NAT, sending keep alives<br>received 1 cert requests for an unknown ca<br>authentication of '205.251.242.103' (myself) with pre-shared key<br>establishing CHILD_SA FOO{2}<br>generating IKE_AUTH request 1 [ IDi N(INIT_CONTACT) IDr AUTH SA TSi TSr N(EAP_ONLY) N(MSG_ID_SYN_SUP) ]<br>sending packet: from 172.30.101.187[4500] to 176.32.98.166[4500] (304 bytes)<br>received packet: from 176.32.98.166[4500] to 172.30.101.187[4500] (208 bytes)<br>parsed IKE_AUTH response 1 [ V IDr AUTH N(NO_PROP) ]<br>authentication of '176.32.98.166' with pre-shared key successful<br>IKE_SA FOO[1] established between 172.30.101.187[205.251.242.103]...176.32.98.166[176.32.98.166]<br>scheduling reauthentication in 28116s<br>maximum IKE_SA lifetime 28656s<br>received NO_PROPOSAL_CHOSEN notify, no CHILD_SA built<br>failed to establish CHILD_SA, keeping IKE_SA<br>establishing connection 'FOO' failed<br></div><div><br></div><div><br></div><div>Any help or direction would greatly be appreciated as I'm not really sure what I can do next. Also, I'm hoping this is the underlying reason for auto=route not working as expected. Thank you,</div><div><br></div><div>Jim</div></div>
<br>
<p><font size="1"><b><span>Confidentiality and Privacy Notice:</span> </b>Information transmitted by this email is proprietary to [m]pirik and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. All personal messages express views solely of the sender, are not to be attributed to [m]pirik, and may not be copied or distributed without this disclaimer. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records.</font></p>