MikroTik

Community discussions
https://forum.mikrotik.com/

IPSec/IKE2 VPN vs Windows 10

https://forum.mikrotik.com/viewtopic.php?t=165673

Page 1 of 1

IPSec/IKE2 VPN vs Windows 10

Posted: Tue Sep 01, 2020 6:51 pm
by rozvald
Hi,

struggling with proper configuration of an IPSec/IKE2 VPN tunnel on Win10

routerOS: 6.47.2

network configuration:
Internet ----- <public ip> media gateway <192.168.0.0/24> ----- <192.168.0.7> RB4011 <internal 192.xxxxxx subnets, 10.1.2.0/24 as VPN subnet>

Access with iOS and Android is working, have a stable connection. Can access the router with the Mikrotik app over the VPN.

Windows 10 client is not working, but the shown behavior is strange.
The RB4011 says, that the connection is established (SA established, peer authorized). After the DPD timeout it kills the SA.
Windows 10 says, that IKE2 credentials are unacceptable. The Event viewer shows an 13801 error code.

Log on the RB4011:
Code: Select all
17:31:04 ipsec ipsec::: -> ike2 request, exchange: SA_INIT:0 <client public IP>[54774] 56cc6ef715838de1:0000000000000000 
17:31:04 ipsec ipsec::: ike2 respond 
17:31:04 ipsec ipsec::: payload seen: SA 
17:31:04 ipsec ipsec::: payload seen: KE 
17:31:04 ipsec ipsec::: payload seen: NONCE 
17:31:04 ipsec ipsec::: payload seen: NOTIFY 
17:31:04 ipsec ipsec::: payload seen: NOTIFY 
17:31:04 ipsec ipsec::: payload seen: NOTIFY 
17:31:04 ipsec ipsec::: payload seen: VID 
17:31:04 ipsec ipsec::: payload seen: VID 
17:31:04 ipsec ipsec::: payload seen: VID 
17:31:04 ipsec ipsec::: payload seen: VID 
17:31:04 ipsec ipsec::: processing payload: NONCE 
17:31:04 ipsec ipsec::: processing payload: SA 
17:31:04 ipsec ipsec::: IKE Protocol: IKE 
17:31:04 ipsec ipsec:::  proposal #1 
17:31:04 ipsec ipsec:::   enc: 3des-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   auth: sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #2 
17:31:04 ipsec ipsec:::   enc: 3des-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   auth: sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #3 
17:31:04 ipsec ipsec:::   enc: 3des-cbc 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   auth: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #4 
17:31:04 ipsec ipsec:::   enc: aes128-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   auth: sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #5 
17:31:04 ipsec ipsec:::   enc: aes128-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   auth: sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #6 
17:31:04 ipsec ipsec:::   enc: aes128-cbc 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   auth: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #7 
17:31:04 ipsec ipsec:::   enc: aes192-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   auth: sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #8 
17:31:04 ipsec ipsec:::   enc: aes192-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   auth: sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #9 
17:31:04 ipsec ipsec:::   enc: aes192-cbc 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   auth: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #10 
17:31:04 ipsec ipsec:::   enc: aes256-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   auth: sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #11 
17:31:04 ipsec ipsec:::   enc: aes256-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   auth: sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #12 
17:31:04 ipsec ipsec:::   enc: aes256-cbc 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   auth: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #13 
17:31:04 ipsec ipsec:::   enc: aes128-gcm 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #14 
17:31:04 ipsec ipsec:::   enc: aes128-gcm 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #15 
17:31:04 ipsec ipsec:::   enc: aes128-gcm 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #16 
17:31:04 ipsec ipsec:::   enc: aes256-gcm 
17:31:04 ipsec ipsec:::   prf: hmac-sha1 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #17 
17:31:04 ipsec ipsec:::   enc: aes256-gcm 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec:::  proposal #18 
17:31:04 ipsec ipsec:::   enc: aes256-gcm 
17:31:04 ipsec ipsec:::   prf: unknown 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec::: matched proposal: 
17:31:04 ipsec ipsec:::  proposal #11 
17:31:04 ipsec ipsec:::   enc: aes256-cbc 
17:31:04 ipsec ipsec:::   prf: hmac-sha256 
17:31:04 ipsec ipsec:::   auth: sha256 
17:31:04 ipsec ipsec:::   dh: modp1024 
17:31:04 ipsec ipsec::: processing payload: KE 
17:31:04 ipsec ipsec::: adding payload: SA 
17:31:04 ipsec ipsec::: adding payload: KE 
17:31:04 ipsec ipsec::: adding payload: NONCE 
17:31:04 ipsec ipsec::: adding notify: NAT_DETECTION_SOURCE_IP 
17:31:04 ipsec ipsec::: adding notify: NAT_DETECTION_DESTINATION_IP 
17:31:04 ipsec ipsec::: adding payload: CERTREQ 
17:31:04 ipsec ipsec::: <- ike2 reply, exchange: SA_INIT:0 <client public IP>[54774] 56cc6ef715838de1:04115b535d674c3e 
17:31:04 ipsec,info new ike2 SA (R): 192.168.0.7[500]-<client public IP>[54774] spi:04115b535d674c3e:56cc6ef715838de1 
17:31:04 ipsec,info ipsec::: new ike2 SA (R): 192.168.0.7[500]-<client public IP>[54774] spi:04115b535d674c3e:56cc6ef715838de1 
17:31:04 ipsec ipsec::: processing payloads: VID 
17:31:04 ipsec ipsec::: peer is MS Windows (ISAKMPOAKLEY 9) 
17:31:04 ipsec ipsec::: processing payloads: NOTIFY 
17:31:04 ipsec ipsec:::   notify: IKEV2_FRAGMENTATION_SUPPORTED 
17:31:04 ipsec ipsec:::   notify: NAT_DETECTION_SOURCE_IP 
17:31:04 ipsec ipsec:::   notify: NAT_DETECTION_DESTINATION_IP 
17:31:04 ipsec ipsec::: (NAT-T) REMOTE LOCAL 
17:31:04 ipsec ipsec::: KA list add: 192.168.0.7[4500]-><client public IP>[54774] 
17:31:06 ipsec ipsec::: -> ike2 request, exchange: AUTH:1 <client public IP>[54783] 56cc6ef715838de1:04115b535d674c3e 
17:31:06 ipsec ipsec::: peer ports changed: 54774 -> 54783 
17:31:06 ipsec ipsec::: KA remove: 192.168.0.7[4500]-><client public IP>[54774] 
17:31:06 ipsec ipsec::: KA list add: 192.168.0.7[4500]-><client public IP>[54783] 
17:31:06 ipsec ipsec::: payload seen: ENC 
17:31:06 ipsec ipsec::: processing payload: ENC 
17:31:06 ipsec ipsec::: payload seen: ID_I 
17:31:06 ipsec ipsec::: payload seen: CERT 
17:31:06 ipsec ipsec::: payload seen: CERTREQ 
17:31:06 ipsec ipsec::: payload seen: AUTH 
17:31:06 ipsec ipsec::: payload seen: CONFIG 
17:31:06 ipsec ipsec::: payload seen: SA 
17:31:06 ipsec ipsec::: payload seen: TS_I 
17:31:06 ipsec ipsec::: payload seen: TS_R 
17:31:06 ipsec ipsec::: processing payloads: NOTIFY (none found) 
17:31:06 ipsec ipsec::: ike auth: respond 
17:31:06 ipsec ipsec::: processing payload: ID_I 
17:31:06 ipsec ipsec::: ID_I (DER DN): CN=client-Dell7250-2.city,C=HU,ST=County,L=City,O=Home,OU=home,SN= 
17:31:06 ipsec ipsec::: processing payload: ID_R (not found) 
17:31:06 ipsec ipsec::: processing payload: AUTH 
17:31:06 ipsec ipsec::: processing payload: CERT 
17:31:06 ipsec ipsec::: got CERT: CN=client-Dell7250-2.city,C=HU,ST=County,L=City,O=Home,OU=home,SN= 
17:31:06 ipsec ipsec::: processing payloads: NOTIFY (none found) 
17:31:06 ipsec ipsec::: processing payload: AUTH 
17:31:06 ipsec ipsec::: requested auth method: RSA 
17:31:06 ipsec,info,account peer authorized: 192.168.0.7[4500]-<client public IP>[54783] spi:04115b535d674c3e:56cc6ef715838de1 
17:31:06 ipsec,info,account ipsec::: peer authorized: 192.168.0.7[4500]-<client public IP>[54783] spi:04115b535d674c3e:56cc6ef715838de1 
17:31:06 ipsec ipsec::: processing payloads: NOTIFY (none found) 
17:31:06 ipsec ipsec::: peer wants tunnel mode 
17:31:06 ipsec ipsec::: processing payload: CONFIG 
17:31:06 ipsec ipsec:::   attribute: internal IPv4 address 
17:31:06 ipsec ipsec:::   attribute: internal IPv4 DNS 
17:31:06 ipsec ipsec:::   attribute: internal IPv4 NBNS 
17:31:06 ipsec ipsec:::   attribute: MS internal IPv4 server 
17:31:06 ipsec,info acquired 10.1.2.105 address for <client public IP>, CN=client-Dell7250-2.city,C=HU,ST=County,L=City,O=Home,OU=home,SN= 
17:31:06 ipsec,info ipsec::: acquired 10.1.2.105 address for <client public IP>, CN=client-Dell7250-2.city,C=HU,ST=County,L=City,O=Home,OU=home,SN= 
17:31:06 ipsec ipsec::: processing payload: TS_I 
17:31:06 ipsec ipsec::: 0.0.0.0/0 
17:31:06 ipsec ipsec::: [::/0] 
17:31:06 ipsec ipsec::: processing payload: TS_R 
17:31:06 ipsec ipsec::: 0.0.0.0/0 
17:31:06 ipsec ipsec::: [::/0] 
17:31:06 ipsec ipsec::: TSi in tunnel mode replaced with config address: 10.1.2.105 
17:31:06 ipsec ipsec::: canditate selectors: 0.0.0.0/0 <=> 10.1.2.105 
17:31:06 ipsec ipsec::: canditate selectors: [::/0] <=> [::/0] 
17:31:06 ipsec ipsec::: processing payload: SA 
17:31:06 ipsec ipsec::: IKE Protocol: ESP 
17:31:06 ipsec ipsec:::  proposal #1 
17:31:06 ipsec ipsec:::   enc: aes256-cbc 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec:::  proposal #2 
17:31:06 ipsec ipsec:::   enc: aes128-cbc 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec:::  proposal #3 
17:31:06 ipsec ipsec:::   enc: 3des-cbc 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec:::  proposal #4 
17:31:06 ipsec ipsec:::   enc: des-cbc 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec:::  proposal #5 
17:31:06 ipsec ipsec:::   enc: null 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec::: searching for policy for selector: 0.0.0.0/0 <=> 10.1.2.105 
17:31:06 ipsec ipsec::: generating policy 
17:31:06 ipsec ipsec::: matched proposal: 
17:31:06 ipsec ipsec:::  proposal #1 
17:31:06 ipsec ipsec:::   enc: aes256-cbc 
17:31:06 ipsec ipsec:::   auth: sha1 
17:31:06 ipsec ipsec::: ike auth: finish 
17:31:06 ipsec ipsec::: ID_R (FQDN): RB4011-2020.city 
17:31:06 ipsec ipsec::: processing payload: NONCE 
17:31:06 ipsec ipsec::: cert: CN=RB4011-2020.city,C=HU,ST=County,L=City,O=Home,OU=home,SN= 
17:31:06 ipsec ipsec::: adding payload: CERT 
17:31:06 ipsec ipsec::: adding payload: ID_R 
17:31:06 ipsec ipsec::: adding payload: AUTH 
17:31:06 ipsec ipsec::: adding notify: INITIAL_CONTACT 
17:31:06 ipsec ipsec::: preparing internal IPv4 address 
17:31:06 ipsec ipsec::: preparing internal IPv4 netmask 
17:31:06 ipsec ipsec::: preparing internal IPv6 subnet 
17:31:06 ipsec ipsec::: preparing internal IPv4 DNS 
17:31:06 ipsec ipsec::: preparing internal IPv4 DNS 
17:31:06 ipsec ipsec::: preparing internal IPv4 DNS 
17:31:06 ipsec ipsec::: preparing internal IPv4 DNS 
17:31:06 ipsec ipsec::: adding payload: CONFIG 
17:31:06 ipsec ipsec::: initiator selector: 10.1.2.105 
17:31:06 ipsec ipsec::: adding payload: TS_I 
17:31:06 ipsec ipsec::: responder selector: 0.0.0.0/0 
17:31:06 ipsec ipsec::: adding payload: TS_R 
17:31:06 ipsec ipsec::: adding payload: SA 
17:31:06 ipsec ipsec::: <- ike2 reply, exchange: AUTH:1 <client public IP>[54783] 56cc6ef715838de1:04115b535d674c3e 
17:31:06 ipsec ipsec::: IPsec-SA established: <client public IP>[54783]->192.168.0.7[4500] spi=0x47a46b1 
17:31:06 ipsec ipsec::: IPsec-SA established: 192.168.0.7[4500]-><client public IP>[54783] spi=0x58562590 
<<------->>
17:33:06 ipsec ipsec::: sending dpd packet 
17:33:06 ipsec ipsec::: <- ike2 request, exchange: INFORMATIONAL:0 <client public IP>[54783] 56cc6ef715838de1:04115b535d674c3e 
17:33:11 ipsec ipsec::: dpd: retransmit 
17:33:16 ipsec ipsec::: dpd: retransmit 
17:33:21 ipsec ipsec::: dpd: retransmit 
17:33:26 ipsec ipsec::: dpd: retransmit 
17:33:31 ipsec ipsec::: dpd: max retransmit failures reached 
17:33:31 ipsec,info killing ike2 SA: 192.168.0.7[4500]-<client public IP>[54783] spi:04115b535d674c3e:56cc6ef715838de1 
17:33:31 ipsec,info ipsec::: killing ike2 SA: 192.168.0.7[4500]-<client public IP>[54783] spi:04115b535d674c3e:56cc6ef715838de1 
17:33:31 ipsec ipsec::: IPsec-SA killing: <client public IP>[54783]->192.168.0.7[4500] spi=0x47a46b1 
17:33:31 ipsec ipsec::: IPsec-SA killing: 192.168.0.7[4500]-><client public IP>[54783] spi=0x58562590 
17:33:31 ipsec ipsec::: removing generated policy 
17:33:31 ipsec ipsec::: adding payload: DELETE 
17:33:31 ipsec ipsec::: <- ike2 request, exchange: INFORMATIONAL:1 <client public IP>[54783] 56cc6ef715838de1:04115b535d674c3e 
17:33:31 ipsec ipsec::: KA remove: 192.168.0.7[4500]-><client public IP>[54783] 
17:33:31 ipsec,info releasing address 10.1.2.105 
17:33:31 ipsec,info ipsec::: releasing address 10.1.2.105

I guess that the firewall is OK, otherwise the mobile clients could not connect (thus I'm not posting those rules).
The certs for mobile clients and the router are self-signed certs and were generated the same way.

I've checked the topic /viewtopic.php?t=151259 but my settings for the VPN adapter shall be OK:
- the certs are correctly installed (otherwise probably it wouldn't connect on the router side).
- though have 2 VPN adapters, I've set it properly, as the right cert is sent to the router to establish the connection.

Any idea would be welcome, as I'm out of them. Thanks.

Re: IPSec/IKE2 VPN vs Windows 10

Posted: Wed Sep 09, 2020 1:00 am
by rozvald
Tried with NCP secure entry client, and the connection is established with proper settings.

Re: IPSec/IKE2 VPN vs Windows 10

Posted: Wed Sep 09, 2020 11:25 pm
by ksteink
I had a similar issue and the limitation on windows 10 is that you cannot define remote ID nor local ID like you do on MacOS, Linux & Android (using StrongSwan) and iOS.

I fix it by making the remote ID to match my IP Cloud DDNS as also my VPN server hostname to connect on my RouterOS when I did create the server certificates.


Sent from my iPhone using Tapatalk

Re: IPSec/IKE2 VPN vs Windows 10

Posted: Mon Sep 14, 2020 6:00 pm
by rozvald
If I'm not mistaken, that'll work until your server certificate expires and you need to create a new one with a different name. Or you create it for 10 years and replace the Tik within that timeframe..

On the other hand I've updated the hosts file on windows, so that the host name resolves to the CN in the cert and is sent as the remote_id. So it is used as server name in the vpn config as well. I think this should be OK, as the log shows correct entries:
Code: Select all
17:31:06 ipsec ipsec::: ID_R (FQDN): RB4011-2020.city 
17:31:06 ipsec ipsec::: processing payload: NONCE 
17:31:06 ipsec ipsec::: cert: CN=RB4011-2020.city,C=HU,ST=County,L=City,O=Home,OU=home,SN=

Re: IPSec/IKE2 VPN vs Windows 10  [SOLVED]

Posted: Wed Sep 16, 2020 1:18 am
by rozvald
Finally I've found this thread: /viewtopic.php?t=139273

That lead me to the working setup of the certificates - created new ones for CA, server and client. My original server and client certs were issued for "digital signature" which works on the iOS but probably not Windows. At least not on the server side - Microsoft itself says, that client cert can have the usage of 'digital signature'
Now the are issued for 'tls server' and 'tls client', respectively.
Certs were issued for some years, not only 1.

One difference though to the linked solution - instead of IP:xx.xx.xx.xx I used the DNS:xxx.sn.mynetname.net as ksteink mentioned above.
All times are UTC+02:00
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/