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

    [SOLVED]:4 minute wait at 'Configuring firewall' after upgrade from 2.1.5 to 2.2

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 1.2k 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.
    • P
      pkutzner
      last edited by

      I recently upgraded a Soekris Net5501-70 system that was running 2.1.5 to 2.2.  After the upgrade, I'm experiencing much longer boot times due to boot-up hanging at the first "Configuring firewall".  Boot eventually does complete, but that particular spot takes 4 minutes when booting 2.2 compared to only 20 seconds when booting to 2.1.5.

      My setup is relatively simple.  One WAN, one LAN, and one OPT interface (which is one end of a Metro-E line).  I have OpenVPN configured, and that's about the extent of it.  Nothing too complex.  I'm just curious as to how I can go about determining why it takes 11 times longer on 2.2 than 2.1.5.

      UPDATE:  I had PFblockerNG installed and its timeouts were causing the issue.  Following the 'fix' in this thread (as suggested by BBcan177) did the trick:
      https://forum.pfsense.org/index.php?topic=88776.0

      1 Reply Last reply Reply Quote 0
      • BBcan177B
        BBcan177 Moderator
        last edited by

        Do you have pfBlockerNG installed, if so, please follow the fix. In this thread.

        https://forum.pfsense.org/index.php?topic=88776.0

        "Experience is something you don't get until just after you need it."

        Website: http://pfBlockerNG.com
        Twitter: @BBcan177  #pfBlockerNG
        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

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

          Thanks BBcan177, looks like that was the issue.  Following the fix in the thread you linked fixed it.

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