Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Zeev
New Contributor

IPSec AutoKey(IKE) Phase2 Problem - help

Hi forum, I' ve bought Fotigate 30B on which i' ve configured(only option) VPN/IPSEC/AutoKey(IKE). My configuration is for dial-up server, where the server itself is the fortigate(using group i created earlier). I manage to finish phase 1 of the connection, and as i understand also parts of phase2, but it always gets stuck at the same part: Jul 5 9:30:49: Initiator: sent <FortiWANIP> quick mode message #1 (OK) Now i don' t know what to do with the quick mode. I' ve read alot bout it, and all places direct me to keep it on it' s default(0.0.0.0/0) for dial-up server configuration. I try to connect using a forticlient. Please, if anyone could share more info and help me with this, i' ve been trying to get it to work for 5 days with all sorts of configurations.
11 REPLIES 11
Zeev
New Contributor

Anybody???
emnoc
Esteemed Contributor III

A snippet of your cfg would be helpful. But yes the QM selector should be 0.0.0.0/0 since we have no ideal as to what the client will be set. Have you ran any diagnostic to determine where and how far your getting with the client?

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Zeev
New Contributor

Hi, thanks for the reply. how do i get the cfg snippet? Or better yet, how do i run diagnostics on the VPN? Never had to do such things before... I can tell how far by using the Client' s Test option, I can see it passes the phase 1, and phase 2 authentications, afterwards it' s on hold with the quick mode and nothing happens untill it fails.
Zeev
New Contributor

This is what i see: Now install tunnels into kernel: 1 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 0.0.0.0 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 0.0.0.0 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 0.0.0.0 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 0.0.0.0 End installing tunnels GetIpInterfaceEntry() old interface 22 metric is 50 SetIpInterfaceEntry() Interface metric changed to 20 vnic metric changed to 20! vnic metric changed to 20 and restarted! Got a kernel message Detect local gateway for peer: 46.120.93.115 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 0.0.0.0 sys_get_local_gwy() called: [in] remote gw: 46.120.93.115. [in] Next hop: 192.168.11.99 Get sa_connect message...192.168.11.108->46.120.93.115:500, natt_mode=0 Using new connection...natt_mode=0 Set connection name = WORK. Tunnel 192.168.11.108 ---> 46.120.93.115:500,natt_en=1 is starting negotiation Will negotiate a DHCP SA Initiator: sent 46.120.93.115 aggressive mode message #1 (OK) Initiator: sent 46.120.93.115 aggressive mode message #2 (DONE) XAuth requesting user name and password Responder: parsed 46.120.93.115 xauth_client mode message #0 (OK) Responder: parsed 46.120.93.115 xauth_client mode message #2 (OK) Initiator: parsed 46.120.93.115 xauth_client mode message #0 (OK) Responder: parsed 46.120.93.115 xauth_client mode message #0 (OK) *** initiator selectors ids: peer:0.0.0.0(0.0.0.0), me:192.168.11.108(0.0.0.0) Initiator: sent 46.120.93.115 quick mode message #1 (OK) AND: Jul 8 15:24:19: Initiator: sent 46.120.93.115 aggressive mode message #1 (OK) Jul 8 15:24:19: Initiator: sent 46.120.93.115 aggressive mode message #2 (DONE) Jul 8 15:24:19: Responder: parsed 46.120.93.115 xauth mode message #0 (OK) Jul 8 15:24:19: Responder: parsed 46.120.93.115 xauth mode message #2 (OK) Jul 8 15:24:19: Initiator: parsed 46.120.93.115 xauth mode message #0 (OK) Jul 8 15:24:19: Responder: parsed 46.120.93.115 xauth mode message #0 (OK) Jul 8 15:24:20: Initiator: sent 46.120.93.115 quick mode message #1 (OK)
Zeev
New Contributor

Can' t anyone help me with this? It' s practically working! all i need is some help around with the Quick Mode, i have no idea what it means and i' m new to Autokey(IKE) VPN.
samanka80
New Contributor

Hey Zeev! Sorry I haven' t worked with your model, but I have a 200B and I have some problems with dialup users.... after defining them I can' t find my tunnel in policies. maybe it' s some problem with the os or maybe there is something we should do... I don' t know, I am looking for the answer.
Zeev
New Contributor

Hi Samanka, I also can' t see the policy. I did notice tho, that when i do not add a policy for my VPN it remains stuck at the " Send aggresive mode" phase 1 authentication. Try to add policy for : Source: <VPN> Any Destination <Internal> Any Any Leave it on Accept. It worked for me. Let me know if yours worked, mine remains stuck at phase 2 Quick Mode status...
emnoc
Esteemed Contributor III

Providing a santizied review of your cfgs, would be quite helpful into understanding what you configured i.e show vpn ipsec phase2 show vpn ipsec phase1 suggestion: if you will review the fortigate mr4 VPN guide, it gives great clear examples on how to setup RA-ipsec.

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Zeev
New Contributor

I managed to start the debugger through CLI, and watched the session running(Client trying to connect) and it always gets stuck on this: peer has not completed Configuration Method
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors