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

    IPSEC Mobile VPN setup broken after upgrade to 2.3.2 (from 2.2.2)

    Scheduled Pinned Locked Moved IPsec
    3 Posts 1 Posters 971 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.
    • B Offline
      bb1976
      last edited by

      I am new to pFSense and am having some trouble getting my VPN setup to work.  I can establish a tunnel connection successfully using my client from a remote internet connection but cannot ping or connect to any device IP's on the network anymore and there is no names resolution either (obviously).  Nothing has changed in my configuration except the upgrade.  I boosted some of the logging levels to the recommended settings for troubleshooting and have also ve attached a few screenshots just in case they may help to point me in the right direction.  Also, if I can pull off any logs that may help in troubleshooting, do let me know.

      Thanks in advance for
      IPSECOverView1.png
      IPSECOverView1.png_thumb
      IPSECOverView2.png
      IPSECOverView2.png_thumb

      1 Reply Last reply Reply Quote 0
      • B Offline
        bb1976
        last edited by

        I just happened to check out the fw rules based on a conversation with a colleague.  Nothing had changed for quite some time and shouldn't have been an issue as there hasn't been a change to the ruleset since way before my update to 2.3.2, however I did see that my IPSEC rule seemed disabled.  I was monitoring my fw logs and amid the spam traffic, there, interspersed with spam traffic was IPSEC traffic as well!  I re-enabled the IPSEC allow rule, and voila, the VPN client was passing traffic again!  Hmmph, sometimes you can't see the forest for the trees?

        IPSecRule.png
        IPSecRule.png_thumb

        1 Reply Last reply Reply Quote 0
        • B Offline
          bb1976
          last edited by

          I just thought I'd mention too that I'm not sure if it was the way that I performed the update that caused this, however, I was on the VPN connection when I performed the update.  Probably a bone-headed thing to do which I will definitely not repeat!  I also will not update without first:

          • checking the release notes
          • waiting for it to be around awhile to see if others have issues
          • Not update without a full backup of the device

          ;D

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