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

Problem VPN / IPSEC

I used the manual setup L2TP and IPsec (Microsoft VPN) to enable an L2TP connection on my FortiGate 200B. Infelistemente failed. Check them in the event that he is negotiating the second phase, but the connection is terminated soon after. Level information Sub Type ppp ID 31009 Action disconnect status success Message Client 177.31.130.30 control connection (id 615) finished Any Suggestion?
6 REPLIES 6
ede_pfau
SuperUser
SuperUser

As far as I remember Win L2TP needs rekeying after a fixed period AND a fixed amount of data (in KB). Search the forums for the exact settings, this has been solved before.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
gustavocearasc
New Contributor

friend Have other topics searched the forum and did not think that will help answer. Below is your settings, follow the entire procedure in the manual: config user group edit " VPN-L2TP" set member " vpn" next end config firewall address edit " L2TP-CLIENT" set subnet 192.168.50.0 255.255.255.0 next end config vpn l2tp set eip 192.168.50.20 set sip 192.168.50.10 set status enable set usrgrp " VPN-L2TP" end config vpn ipsec phase1 edit " L2TP-P1" set type dynamic set interface " port1" set dhgrp 2 set proposal aes256-md5 3des-sha1 aes192-sha1 set psksecret ENC passorwd next end config vpn ipsec phase2 edit " L2TP-P2" set encapsulation transport-mode set keylife-type both set pfs disable set phase1name " L2TP-P1" set proposal aes256-md5 3des-sha1 aes192-sha1 set keylifekbs 250000 set keylifeseconds 3600 next end
ede_pfau
SuperUser
SuperUser

I cannot search for you now, but for me it looks highly suspicious that Windows will support AES256. And yes, the values for keylifebs and keylifeseconds need to be exactly the ones that Windows uses.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
gustavocearasc
New Contributor

hello I changed the port to another link, apparently has been resolved, now I have difficulties when trying to register the VPN client, the following debug error: find_tunnel_call () -183: can not find tunnel 1049 handle_network_packet () -197: L2TP: Tunnel 1049 is invalid incoming packet (call = 1050).
gustavocearasc
New Contributor

LOG ERROR: create_new_tunnel()-91: Allocated new Tunnel id=1, total count = 1 handle_control_packet()-550: check_control_hdr()-173: check_control_hdr: control, peer_call_id = 0, Ns = 0, Nr = 0 check_control_hdr()-185: Updated control rec seqno. Value is now 1 __avp_protocol_version()-233: peer is using version 8, revision 128. __avp_framing_caps()-248: supported peer framing: __avp_bearer_caps()-264: supported peer bearers: __avp_firmware_rev()-279: peer' s firmware version 2048 _avp_hostname()-295: Peer' s hostname is ' nagios.dominio.com.br' __avp_vendor()-310: peer' s vendor ' Microsoft' __avp_assigned_tunnel()-339: peer' s tunnel 39 avp_receive_window_size()-359: peer' s RWS 8. run_ctrl_state_machine()-91: run_ctrl_state_machine: message type is (1). Tunnel is 39, call is 0. run_ctrl_state_machine()-97: ** run_ctrl_state_machine - SCCRQ ** run_ctrl_state_machine()-108: Rule 177.109.159.62 to 177.109.159.62avp_put_hostname()-84: Sent the host name = 177.1 run_ctrl_state_machine()-165: Sending SCCRP schedule_event()-94: schedule_event()-100: Message due 1104927168, now = 1104927068 handle_control_packet()-550: check_control_hdr()-173: check_control_hdr: control, peer_call_id = 0, Ns = 1, Nr = 1 check_control_hdr()-185: Updated control rec seqno. Value is now 2 run_ctrl_state_machine()-91: run_ctrl_state_machine: message type is (3). Tunnel is 39, call is 0. run_ctrl_state_machine()-174: ** run_ctrl_state_machine - SCCCN ** L2TPD 97: 179:Connection established to 177.109.159.62, 1701. Local: 1, Remote: 39. start_hello_timer()-59: L2TP: starting Hello timer for tunnel 39, next in 60 seconds. schedule_event()-94: schedule_event()-100: Message due 1104933138, now = 1104927138 handle_network_packet()-262: Sending a ZLB to acknowledge last message send_zlb()-73: ** send_zlb ** handle_control_packet()-550: check_control_hdr()-173: check_control_hdr: control, peer_call_id = 0, Ns = 2, Nr = 1 check_control_hdr()-185: Updated control rec seqno. Value is now 3 __avp_assigned_call()-392: Parsed new call id of 1 __avp_call_serno()-418: serial number is 0 __avp_bearer_type()-445: peer' s bears anamylog run_ctrl_state_machine()-91: run_ctrl_state_machine: message type is (10). Tunnel is 39, call is 1. run_ctrl_state_machine()-224: ** run_ctrl_state_machine - ICRQ ** run_ctrl_state_machine()-234: New call was created for tunnel 39, call id = 1 run_ctrl_state_machine()-290: This call is the master_call, its peer_call_id = 2 run_ctrl_state_machine()-298: run_ctrl_state_machine: sending ICRP schedule_event()-94: schedule_event()-100: Message due 1104927252, now = 1104927152 handle_control_packet()-550: check_control_hdr()-173: check_control_hdr: control, peer_call_id = 1, Ns = 3, Nr = 2 check_control_hdr()-185: Updated control rec seqno. Value is now 4 __avp_tx_speed()-495: TX is 3600000 __avp_frame_type()-474: peer' s framing sync avp_handler()-723: AVP 29 was ignored run_ctrl_state_machine()-91: run_ctrl_state_machine: message type is (12). Tunnel is 39, call is 1. run_ctrl_state_machine()-307: ** run_ctrl_state_machine - ICCN ** start_pppd()-156: Starting pppd L2TPD 29: 157:Starting call (launching pppd, opening GRE) run_ctrl_state_machine()-327: Call established with 177.109.159.62, Local: 2, Remote: 1, Serial: 0 handle_network_packet()-262: Sending a ZLB to acknowledge last message send_zlb()-73: ** send_zlb ** L2TPD 25: 315:Client 177.109.159.62 control connection started (id 1), assigned ip 192.168.50.10 start_pppd()-328: /bin/pppd start_pppd()-328: 0 start_pppd()-328: l2tp start_pppd()-328: port2 start_pppd()-328: local start_pppd()-328: file start_pppd()-328: /etc/ppp/options start_pppd()-328: 115200 start_pppd()-328: 201.20.93.114:192.168.50.10 start_pppd()-328: +pap start_pppd()-328: +chap start_pppd()-328: peer-remote start_pppd()-328: 177.109.159.62 start_pppd()-328: lcp-echo-interval start_pppd()-328: 5 start_pppd()-328: lcp-echo-failure start_pppd()-328: 3 start_pppd()-330: monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-117: L2TP: Peer ack' ed control packet. monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-117: L2TP: Peer ack' ed control packet. ike 0: IP 201.20.93.114 (28) is down ike 0: IP 201.20.93.114 (28) is down child_handler()-114: Child handler 28844 vf_close_calls_pppd()-75: L2TPD 87: 86:pppd died for call 1 l2tp_vdbind_msg_handler()-87: del_vdbind message:vd=root 0 devindex=28 ppp0 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930004, now = 1104929904 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930019, now = 1104929919 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930096, now = 1104929996 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930103, now = 1104930003 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930171, now = 1104930071 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-430: Request peer to close call 2 schedule_event()-94: schedule_event()-100: Message due 1104930256, now = 1104930156 l2tp_handle_calls()-300: closing The master call close_call()-409: ** close_call ** close_call()-424: Closing call 2 free_call()-211: ** free_call ** monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-124: The resent packet Nr = 4 monitor_ctrl_pkt_xmit()-147: L2TP: Retransmitting packet... timeout in 1 seconds. schedule_event()-94: schedule_event()-100: Message due 1104930272, now = 1104930172 monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-124: The resent packet Nr = 4 monitor_ctrl_pkt_xmit()-147: L2TP: Retransmitting packet... timeout in 1 seconds. schedule_event()-94: schedule_event()-100: Message due 1104930272, now = 1104930172 monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-124: The resent packet Nr = 4 monitor_ctrl_pkt_xmit()-147: L2TP: Retransmitting packet... timeout in 1 seconds. schedule_event()-94: schedule_event()-100: Message due 1104930272, now = 1104930172 monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-124: The resent packet Nr = 4 monitor_ctrl_pkt_xmit()-147: L2TP: Retransmitting packet... timeout in 1 seconds. schedule_event()-94: schedule_event()-100: Message due 1104930272, now = 1104930172 monitor_ctrl_pkt_xmit()-95: monitor_ctrl_pkt_xmit()-124: The resent packet Nr = 4 monitor_ctrl_pkt_xmit()-147: L2TP: Retransmitting packet... timeout in 1 seconds. schedule_event()-94: schedule_event()-100: Message due 1104930272, now = 1104930172 l2tp_handle_calls()-287: closing down tunnel 1 close_tunnel()-445: ** close_tunnel ** close_tunnel()-458: Closing and destroying tunnel 1 L2TPD 26: 460:Client 177.109.159.62 control connection (id 1) finished close_calls_for_tunnel()-100: free_call()-211: ** free_call ** free_tunnel()-117: Done close_calls_for_tunnel find_tunnel_call()-183: can' t find tunnel 1 handle_network_packet()-197: L2TP: invalid tunnel 1 for incoming packet (call=2). find_tunnel_call()-183: can' t find tunnel 1 handle_network_packet()-197: L2TP: invalid tunnel 1 for incoming packet (call=2). find_tunnel_call()-183: can' t find tunnel 1
gustavocearasc
New Contributor

VPN connects, but drops after a few minutes.
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