Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Disconnected phase 2 IPSEC pfsense2.4.4-FORTIGATE

    Scheduled Pinned Locked Moved IPsec
    11 Posts 3 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • kiokomanK
      kiokoman LAYER 8
      last edited by kiokoman

      Immagine.jpg

      i say something is wrong on your config.. IKE Phase 2 ?
      where are on your config this ip 192.168.10.2/32 10.0.0.113/32 ?
      i can see you have 192.168.10.0/24 and 10.0.0.0/16

      ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
      Please do not use chat/PM to ask for help
      we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
      Don't forget to Upvote with the 👍 button for any post you find to be helpful.

      1 Reply Last reply Reply Quote 1
      • B
        badiane
        last edited by

        I have configured 192.168.10.0/24 as local LAN subnet(IPSEC)
        and 10.0.0.0/16 as remote subnet (IPSEC)
        I didn't configure the sub net 192.168.10.2/32 and 10.0.0.113/32 any where

        1 Reply Last reply Reply Quote 0
        • B
          badiane
          last edited by

          Thank you very much kiokoman for your replying. Do you think the Lan subnet (IPSEC) should be more specific?

          1 Reply Last reply Reply Quote 0
          • kiokomanK
            kiokoman LAYER 8
            last edited by kiokoman

            like what? if you have 10.0/24 and 0.0/16 on both side is ok.
            maybe try to "Disable rekey" for a test
            also you might try stopping and then starting IPsec service (don't use the restart action)

            ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
            Please do not use chat/PM to ask for help
            we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
            Don't forget to Upvote with the 👍 button for any post you find to be helpful.

            1 Reply Last reply Reply Quote 1
            • B
              badiane
              last edited by

              Please take a look at the log file and here is my new configuration phase1.advanced_option_phase1.png log_no_rekey1.png log_no_rekey2.png log_no_rekey2.png

              1 Reply Last reply Reply Quote 0
              • B
                badiane
                last edited by

                Even thought, the Disable rekey is cheked. The IPsec still keep turn on to inactive about after 30 mn of connexion.

                log_no_rekey1.png log_no_rekey2.png log_no_rekey3.png

                1 Reply Last reply Reply Quote 0
                • kiokomanK
                  kiokoman LAYER 8
                  last edited by

                  you have another error here,

                  no acceptable DIFFIE_HELLMAN_GROUP found

                  check
                  Encryption Algorithm for PHASE 1 -> both side must use the same settings
                  and
                  PFS key group for PHASE 2 -> both side must use the same settings

                  ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
                  Please do not use chat/PM to ask for help
                  we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
                  Don't forget to Upvote with the 👍 button for any post you find to be helpful.

                  1 Reply Last reply Reply Quote 1
                  • B
                    badiane
                    last edited by

                    Here is my configuration of remote side.
                    Excatly, I 've cheked on Diffie-Hellman Group 14 and 5 by error.
                    After the rectification of this error, the status of IPSEC turned to SESSION OUT OF TIME after about 1 hour.

                    remote_config1-1.png

                    remote_config1.png

                    remote_config2.png

                    session_timeout.png

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      Konstanti @badiane
                      last edited by

                      @badiane
                      Hello
                      What is the lifetime value in PFSense's phase 2 settings ? Also of 3600 seconds ?
                      Try only on the Fortigate side to reduce this value to 3000 second

                      B 1 Reply Last reply Reply Quote 1
                      • B
                        badiane @Konstanti
                        last edited by

                        @Konstanti Thank you Konstani. The problem is resolved with
                        -Enable Replay Detection checked
                        -Enable Perfect Forward Secrecy checked
                        -Auto-Negociated checked

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.