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.6k 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.
    • 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
                        • V
                          vbentley
                          last edited by

                          @RMB:

                          I can confirm that this workaround is working for me!

                          Are you using Pre Shared Keys or RSA Certificates for authentication?

                          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

                            I am using Preshared Keys.

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

                              Thanks. Using PSK works for me too, but I would rather use certs instead.

                              I don't think that the AES patch rollback will make any difference to the issue I am experiencing which is a failure to establish a P1 with RSA Certs and 3DES.

                              I suspect that I could be the only one using RSA Certs with site-to-site IPsec VPN on pfSense as more people would have spotted this.
                              I really wish 2.2.3 was just a GUI XSS fix.

                              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
                              • D
                                doktornotor Banned
                                last edited by

                                @vbentley:

                                I suspect that I could be the only one using RSA Certs with site-to-site IPsec VPN on pfSense as more people would have spotted this.
                                I really wish 2.2.3 was just a GUI XSS fix.

                                Mutual RSA works here with 2.2.3 on pfS -> pfS (2.2.3)

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

                                  Obviously we haven't tested with whatever hardware crypto cards you are using but the base FreeBSD hasn't changed so I wouldn't have expected them to fail.
                                  Does it work if you choose not to use the hardware encryption?

                                  Steve

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

                                    @doktornotor:

                                    Mutual RSA works here with 2.2.3 on pfS -> pfS (2.2.3)

                                    Excellent!
                                    Can you tell me if you are using IP:value references in your certs or DNS:value references?

                                    I am using DNS:value references because one end of the VPN is on a dynamic IP with dynamic DNS. It works on 2.2.2 perhaps StrongSwan 5.3.2 is looking for something in my certs that 5.3.0 doesn't need. I'm thinking this has something to do with reqid.

                                    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

                                      @stephenw10:

                                      Does it work if you choose not to use the hardware encryption?

                                      I will try building two test boxes without crypto cards next week.
                                      OpenSSL version hasn't changed so I'm fairly confident this isn't the problem.

                                      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
                                      • P
                                        phil.davis
                                        last edited by

                                        OpenSSL version hasn't changed so I'm fairly confident this isn't the problem.

                                        That cannot be automatically assumed because of:

                                        FreeBSD patches OpenSSL without changing the version number.

                                        https://forum.pfsense.org/index.php?topic=91461.msg532876#msg532876

                                        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          doktornotor Banned
                                          last edited by

                                          Main problem here is that debugging any IPsec is impossible since logging is totally no-op (yet another regression). I really don't have any decent words for this "strongs"wan thing. Has been nothing but one giant pain in the butt ever since it's been introduced.

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mauirixxx
                                            last edited by

                                            I know this thread is over 2+ weeks old but ….

                                            @Work tonight I upgraded pfSense to 2.2.3 with the AES-N1 option enabled.
                                            @Home when 2.2.3 was released, I upgraded right away, and had the AES-N1 option enabled.

                                            After the upgrade at work tonight, I had the same symptoms - endpoints would connect like they should, but 0 traffic passed between them. After I disabled the AES-N1 acceleration @work and rebooted, all is well and acting like it should again.

                                            So I have 1 endpoint with it enabled, and 1 without, and traffic flows. I haven't tried re-enabling it because stuff works now.

                                            Next test would be to disable it @home, and enable it @work, and see if it still works as it should. Or should I just leave well enough alone?

                                            –mauirixxx

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