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

    IPSec tunnel problems after pfSense 2.2.3 upgrade

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    64 Posts 17 Posters 28.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.
    • D
      dharrigan
      last edited by

      Hi,

      Bug created for further investigation.

      https://redmine.pfsense.org/issues/4791

      -=david=-

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Any of you confirm that an alternative Phase2 encryption type fixes this?

        Steve

        1 Reply Last reply Reply Quote 0
        • F
          frmpf
          last edited by

          @stephenw10:

          Ok, this looks like a problem with AES-CBC crypto at Phase2.

          Try changing your Phase2 to anything other than AES-CBC (the default value). We are using AES-GCM which is working fine but anything Blowfish also works.

          I will try this shortly and report back (these units aren't production yet so I can test at will)

          1 Reply Last reply Reply Quote 0
          • J
            jdp0418
            last edited by

            Ok, I setup my phase 2 as AES-128 - AES-XCBC (only; no other options selected).  It now appears I have a phase 1 tunnel up, but no phase 2 connection exists between the sites.  If I set it as one of several options under hash, phase 2 comes up.  I noticed that several of the configs posted here appear to have SHA1 selected as the hash algorithm though.

            @vbentley
            I am not 100% clear on how nanoBSD updates, but I am pretty sure its just writes a new image on one of the boot slices of the flash drive.  So yes, that is probably more akin to a fresh install than an upgrade.  That definitely is a big difference!

            1 Reply Last reply Reply Quote 0
            • yuljkY
              yuljk
              last edited by

              Specifying AES-256-GCM only for phase2 results in the same error for me in the Shrewsoft client.

              1 Reply Last reply Reply Quote 0
              • F
                frmpf
                last edited by

                Changed to 3DES and the tunnel works fine, I'll try the other AES modes shortly but tight on time right now…  on the OpenBSD side it didn't like me simply changing "aes" to "aes-128-gcm", so I'll have to dig a bit more.

                1 Reply Last reply Reply Quote 0
                • yuljkY
                  yuljk
                  last edited by

                  frmpf - Which hash algorithm are you using with 3DES?

                  Cheers

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    The Shrewsoft client is extremely picky.

                    Just to sure you use 3DES in the Phase2 config frmpf?

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • F
                      frmpf
                      last edited by

                      I've left the hash as SHA1 in all trials…  I had success with 3DES for quick mode, left main mode as AES:

                      On the pfSense side, I only changed the enc for phase 2 from aes to 3des, everything else the same.

                      Similarly on OpenBSD, just a single quick mode change from aes to 3des

                      Doesn't work with 2.2.3

                      ike dynamic esp from 192.168.87.0/24 to { 172.29.200.0/24, 192.168.77.0/24 } peer 2.2.2.80
                        main auth hmac-sha1 enc aes group modp1024 lifetime 28800
                        quick auth hmac-sha1 enc aes group modp1024 lifetime 3600
                        srcid 1.1.1.251 dstid 2.2.2.80 psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

                      Works with 2.2.3

                      ike dynamic esp from 192.168.87.0/24 to { 172.29.200.0/24, 192.168.77.0/24 } peer 2.2.2.80
                        main auth hmac-sha1 enc aes group modp1024 lifetime 28800
                        quick auth hmac-sha1 enc 3des group modp1024 lifetime 3600
                        srcid 1.1.1.251 dstid 2.2.2.80 psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        The issue here is the encryption type set on the Phase2 only. If anyone is seeing something different please say so.
                        The cause seems to be the AES-NI module that is trying to decrypt traffic that it can't so an alternative solution is to disable the AES-NI module if you must use AES-CBC for example.

                        Is anybody here NOT using the AES-NI module/AES-NI capable hardware?

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • V
                          vbentley
                          last edited by

                          I tried a fresh CD install of 2.2.3 on the remote host but still no luck. My phase 1 fails using RSA certs. So my problem may be useful aid to diagnosis as it shows:-

                          1. I cannot establish Phase 1
                          2. I am using 3DES SHA1 for P1 and P2
                          3. My logs for 2.2.3 show the key exchange AUTHENTICATION_FAILED

                          What makes my case different? I am using hardware crypto at each end.

                          Jun 26 18:47:53 	charon: 06[IKE] <con1|2> received AUTHENTICATION_FAILED notify error
Jun 26 18:47:53 	charon: 06[IKE] <con1|2> received AUTHENTICATION_FAILED notify error
Jun 26 18:47:53 	charon: 06[ENC] <con1|2> parsed IKE_AUTH response 1 [ N(AUTH_FAILED) ]
Jun 26 18:47:53 	charon: 06[NET] <con1|2> received packet: from xxx.xxx.xxx.xxx[500] to yyy.yyy.yyy.yyy[500] (68 bytes)
Jun 26 18:47:52 	charon: 06[NET] <con1|2> sending packet: from yyy.yyy.yyy.yyy[500] to xxx.xxx.xxx.xxx[500] (512 bytes)
Jun 26 18:47:52 	charon: 06[NET] <con1|2> sending packet: from yyy.yyy.yyy.yyy[500] to xxx.xxx.xxx.xxx[500] (544 bytes)
Jun 26 18:47:52 	charon: 06[NET] <con1|2> sending packet: from yyy.yyy.yyy.yyy[500] to xxx.xxx.xxx.xxx[500] (544 bytes)
Jun 26 18:47:52 	charon: 06[NET] <con1|2> sending packet: from yyy.yyy.yyy.yyy[500] to xxx.xxx.xxx.xxx[500] (544 bytes)
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> generating IKE_AUTH request 1 [ EF(4/4) ]
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> generating IKE_AUTH request 1 [ EF(3/4) ]
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> generating IKE_AUTH request 1 [ EF(2/4) ]
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> generating IKE_AUTH request 1 [ EF(1/4) ]
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> splitting IKE message with length of 1972 bytes into 4 fragments
Jun 26 18:47:52 	charon: 06[ENC] <con1|2> generating IKE_AUTH request 1 [ IDi CERT N(INIT_CONTACT) CERTREQ IDr AUTH N(IPCOMP_SUP) N(ESP_TFC_PAD_N) SA TSi TSr N(MULT_AUTH) N(EAP_ONLY) ]
Jun 26 18:47:52 	charon: 06[IKE] <con1|2> establishing CHILD_SA con1
Jun 26 18:47:52 	charon: 06[IKE] <con1|2> establishing CHILD_SA con1
Jun 26 18:47:52 	charon: 06[IKE] <con1|2> sending end entity cert "C=GB, ...</con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2></con1|2>

                          Trademark Attribution and Credit
                          pfSense® and pfSense Certified® are registered trademarks of Electric Sheep Fencing, LLC in the United States and other countries.

                          1 Reply Last reply Reply Quote 0
                          • F
                            frmpf
                            last edited by

                            @stephenw10:

                            The issue here is the encryption type set on the Phase2 only. If anyone is seeing something different please say so.
                            The cause seems to be the AES-NI module that is trying to decrypt traffic that it can't so an alternative solution is to disable the AES-NI module if you must use AES-CBC for example.

                            Is anybody here NOT using the AES-NI module/AES-NI capable hardware?

                            Steve

                            Can confirm, disabled AES-NI on the 2.2.3 device and now the tunnels work in the original configuration. Does that leave room for hope that a fix won't be too tough, since 2.2.2 still works fine with the AES-NI component enabled?  It's just the kernel module loaded for the hardware aes?

                            1 Reply Last reply Reply Quote 0
                            • yuljkY
                              yuljk
                              last edited by

                              I can confirm that everything is working after switching across to 3DES for phase 2 (algorithm SHA1)

                              I did not have the AES-NI module enabled on my box at any point.

                              Thanks guys - Hopefully we'll see a fix for AES fairly soon :)

                              Chris

                              1 Reply Last reply Reply Quote 0
                              • H
                                heper
                                last edited by

                                https://redmine.pfsense.org/issues/4791

                                might be "fixed"in the snapshots dating after renato's comments

                                1 Reply Last reply Reply Quote 0
                                • P
                                  pbnet
                                  last edited by

                                  Still does not work for me, even if not using AES encryption

                                  Here is my setup:

                                  • On PFSense 2.2.3:


                                  • On cisco RV042:

                                  And the results are

                                  on PFSense:

                                  on RV042:

                                  Now the logs show incomplete ISAKMP SA on the RV042

                                  and conn unrouted on PFSense

                                  Of course, no machine on the remote VPN side can be reached.

                                  I don't really think it's a AES issue here, since I'm not using it…. or am I doing something wrong ???
                                  Everything was fine on PFSense 2.2.2

                                  Thanks for any suggestion

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    That looks like an identifier mismatch, nothing to do with this bug.
                                    The Linksys is complainiung about the identifier sent by pfSense being an FQDN not an IP.

                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      pbnet
                                      last edited by

                                      Thanks a lot Stephen.

                                      You're a life savior.

                                      One quick question, regarding something I don't understand

                                      My identifier: My IP Address (does it take the WAN IP Address here) ?
                                      Peer identifier: Peer IP Address (does it take the IP/host name of remote gateway ?)

                                      Thanks a lot.

                                      1 Reply Last reply Reply Quote 0
                                      • V
                                        vbentley
                                        last edited by

                                        You can use IP addresses for your identifiers but they are not much use unless the WAN IP addresses at each end are both static. The IP address identifier is just for IP addresses not hostnames.

                                        If you have one or more WAN interfaces with dynamic IP addresses you should use an identifier that doesn't change.

                                        If you have a resolvable hostname for your pfSense host and another for your Linksys host you could use the Distinguished Name type like in this example:-

                                        On pfSense
                                        My Identifier: Distinguished Name: pfsense.mydynamic.dns
                                        Peer Identifier: Distinguished Name: linksys.mydynamic.dns

                                        On Linksys
                                        My Identifier: Distinguished Name: linksys.mydynamic.dns
                                        Peer Identifier: Distinguished Name: pfsense.mydynamic.dns

                                        Trademark Attribution and Credit
                                        pfSense® and pfSense Certified® are registered trademarks of Electric Sheep Fencing, LLC in the United States and other countries.

                                        1 Reply Last reply Reply Quote 0
                                        • V
                                          vbentley
                                          last edited by

                                          Am I the only one on this thread that was using RSA Certificate authentication on 2.2.2?

                                          Trademark Attribution and Credit
                                          pfSense® and pfSense Certified® are registered trademarks of Electric Sheep Fencing, LLC in the United States and other countries.

                                          1 Reply Last reply Reply Quote 0
                                          • RMBR
                                            RMB
                                            last edited by

                                            Hi,

                                            I have had some contact with pfSense Support and they have narrowed down the problem.

                                            -quote-
                                            Expect 2.2.4 out soon!
                                            For now, simply disable AES-NI from System > Advanced, Misc, set Crypto Acceleration to None, and then reboot.
                                            -end-of-quote-

                                            I can confirm that this workaround is working for me!

                                            Kind regards,
                                            Rene.

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