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

    Ipsec mobile clients in 2.0 not working?

    Scheduled Pinned Locked Moved IPsec
    20 Posts 4 Posters 7.7k 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.
    • A
      alexandrnew
      last edited by

      from 1.2.3 or 2.0 ?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        2.0

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • A
          alexandrnew
          last edited by

          in files:
          ipsec log in debug mode & /var/etc/racoon.conf & /var/etc/spd.conf & setkey -D & setkey -DP
          files: 1.2.3 - worked
          pfsense - only updated
          pfsense updated + disable nat-t

          in all variants - client settings not changed

          [1.2.3 -worked.txt](/public/imported_attachments/1/1.2.3 -worked.txt)
          [pfsense - updated.txt](/public/imported_attachments/1/pfsense - updated.txt)
          [disable nat-t on pfsense.txt](/public/imported_attachments/1/disable nat-t on pfsense.txt)

          1 Reply Last reply Reply Quote 0
          • A
            alexandrnew
            last edited by

            jimp, I can send you the username \ password in PM for the client and pfsense

            1 Reply Last reply Reply Quote 0
            • A
              alexandrnew
              last edited by

              up

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                It's already a known issue and the solution will not be fast. Just keep an eye on the ticket for any updates.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • A
                  alexandrnew
                  last edited by

                  @jimp:

                  Just keep an eye on the ticket for any updates.

                  tell me where to watch for updates? or them will be seen in the pfsese?

                  1 Reply Last reply Reply Quote 0
                  • jimpJ
                    jimp Rebel Alliance Developer Netgate
                    last edited by

                    On the ticket. If any progress is made, someone will update that ticket.

                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • L
                      limecat
                      last edited by

                      jimp, can you clarify whether this is likely to be the same issue as this:
                      http://forum.pfsense.org/index.php/topic,41631.0.html

                      and if so, would the same information you asked for here be relevant?  I would really like to help however possible to see this resolved.

                      Thanks.

                      1 Reply Last reply Reply Quote 0
                      • A
                        alexandrnew
                        last edited by

                        in 2.0.1 not working & nat-t not working…

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

                          i was having problems with 2.0 and 2.1 for shrew ipsec clients where the initial connection would work fine, later subsequent connections would seem to connect but would fail to pass data

                          i tried disabling NAT-T and DPD as suggested elsewhere in this forum, but the ultimate fix was to setup the pfsense and shrew client per typical "road warrior" configs

                          e.g. http://dekapitein.vorkbaard.nl/tech-1/how-to-set-up-ipsec-tunneling-in-pfsense-2-0-release-for-road-warriors

                          with the EXCEPTION of setting the P1 Proposal Generation to "Unique" instead of "Default"

                          [that setting change is noted in the redmine link mentioned in this thread, but its in a slightly different context of multiple clients coming from the same nat network]

                          anyway, since making that change, i havent seen the problem where later reconnects fail, and no need to disable NAT-T and DPD

                          maybe that setting will work for you

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