[GH-ISSUE #136] Can not connect to vpn server #123

Closed
opened 2026-03-02 07:27:56 +03:00 by kerem · 1 comment
Owner

Originally created by @tswsxk on GitHub (Apr 10, 2019).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/136

I suddenly could not connect to my vpn server which is Centos 7.6
Here is my log

Apr 10 15:04:34 dm pluto[25112]: packet from 114.214.246.164:500: ignoring unknown Vendor ID payload [01528bbbc00696121849ab9a1c5b2a5100000001]
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: responding to Main Mode from unknown peer 114.214.246.164 on port 500
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Oakley Transform [AES_CBC (256), HMAC_SHA1, DH20] refused
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Oakley Transform [AES_CBC (128), HMAC_SHA1, DH19] refused
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R1: sent MR1, expecting MI2
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R2: sent MR2, expecting MI3
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Peer ID is ID_IPV4_ADDR: '114.214.246.164'
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=PRESHARED_KEY cipher=aes_256 integ=sha group=MODP2048}
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Configured DPD (RFC 3706) support not enabled because remote peer did not advertise DPD support
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: the peer proposed: 202.38.75.5/32:17/1701 -> 114.214.246.164/32:17/0
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: NAT-Traversal: received 2 NAT-OA. Using first, ignoring others
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: responding to Quick Mode proposal {msgid:01000000}
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8:     us: 202.38.75.5:17/1701
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8:   them: 114.214.246.164:17/1701
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2 transport mode {ESP/NAT=>0x83e86832 <0x4c36aeda xfrm=AES_CBC_256-HMAC_SHA1_96 NATOA=114.214.246.164 NATD=114.214.246.164:4500 DPD=active}
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: Configured DPD (RFC 3706) support not enabled because remote peer did not advertise DPD support
Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: STATE_QUICK_R2: IPsec SA established transport mode {ESP/NAT=>0x83e86832 <0x4c36aeda xfrm=AES_CBC_256-HMAC_SHA1_96 NATOA=114.214.246.164 NATD=114.214.246.164:4500 DPD=active}
Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: received Delete SA(0x83e86832) payload: deleting IPSEC State #8
Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: deleting other state #8 (STATE_QUICK_R2) and sending notification
Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: ESP traffic information: in=696B out=0B
Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164: deleting connection "l2tp-psk"[4] 114.214.246.164 instance with peer 114.214.246.164 {isakmp=#0/ipsec=#0}
Apr 10 15:05:09 dm pluto[25112]: packet from 114.214.246.164:4500: received and ignored empty informational notification payload
Originally created by @tswsxk on GitHub (Apr 10, 2019). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/136 I suddenly could not connect to my vpn server which is Centos 7.6 Here is my log ``` Apr 10 15:04:34 dm pluto[25112]: packet from 114.214.246.164:500: ignoring unknown Vendor ID payload [01528bbbc00696121849ab9a1c5b2a5100000001] Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: responding to Main Mode from unknown peer 114.214.246.164 on port 500 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Oakley Transform [AES_CBC (256), HMAC_SHA1, DH20] refused Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Oakley Transform [AES_CBC (128), HMAC_SHA1, DH19] refused Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R1: sent MR1, expecting MI2 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R2: sent MR2, expecting MI3 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Peer ID is ID_IPV4_ADDR: '114.214.246.164' Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=PRESHARED_KEY cipher=aes_256 integ=sha group=MODP2048} Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: Configured DPD (RFC 3706) support not enabled because remote peer did not advertise DPD support Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: the peer proposed: 202.38.75.5/32:17/1701 -> 114.214.246.164/32:17/0 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: NAT-Traversal: received 2 NAT-OA. Using first, ignoring others Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: responding to Quick Mode proposal {msgid:01000000} Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: us: 202.38.75.5:17/1701 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: them: 114.214.246.164:17/1701 Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2 transport mode {ESP/NAT=>0x83e86832 <0x4c36aeda xfrm=AES_CBC_256-HMAC_SHA1_96 NATOA=114.214.246.164 NATD=114.214.246.164:4500 DPD=active} Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: Configured DPD (RFC 3706) support not enabled because remote peer did not advertise DPD support Apr 10 15:04:34 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: STATE_QUICK_R2: IPsec SA established transport mode {ESP/NAT=>0x83e86832 <0x4c36aeda xfrm=AES_CBC_256-HMAC_SHA1_96 NATOA=114.214.246.164 NATD=114.214.246.164:4500 DPD=active} Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #7: received Delete SA(0x83e86832) payload: deleting IPSEC State #8 Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: deleting other state #8 (STATE_QUICK_R2) and sending notification Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164 #8: ESP traffic information: in=696B out=0B Apr 10 15:05:09 dm pluto[25112]: "l2tp-psk"[4] 114.214.246.164: deleting connection "l2tp-psk"[4] 114.214.246.164 instance with peer 114.214.246.164 {isakmp=#0/ipsec=#0} Apr 10 15:05:09 dm pluto[25112]: packet from 114.214.246.164:4500: received and ignored empty informational notification payload ```
kerem closed this issue 2026-03-02 07:27:56 +03:00
Author
Owner

@hwdsl2 commented on GitHub (Apr 11, 2019):

@tswsxk Hello! From the logs you provided... Your VPN client sent the disconnection (Delete SA) request shortly after connecting. One possible solution is to apply the fix for "Windows Error 809" and reboot [1].

[1] https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#windows-error-809

<!-- gh-comment-id:481964792 --> @hwdsl2 commented on GitHub (Apr 11, 2019): @tswsxk Hello! From the logs you provided... Your VPN client sent the disconnection (Delete SA) request shortly after connecting. One possible solution is to apply the fix for "Windows Error 809" and reboot [1]. [1] https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#windows-error-809
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-ipsec-vpn-server#123
No description provided.