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

    package update | no internet until reroot or reboot

    Scheduled Pinned Locked Moved pfBlockerNG
    5 Posts 3 Posters 668 Views 3 Watching
    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.
    • N Offline
      NinthWave
      last edited by

      Each time I update pfBlocker NG, I lose WAN access until I reroot pfSense.

      Is this a normal behavior? Should I do something else ?

      RonpfSR 1 Reply Last reply Reply Quote 0
      • RonpfSR Offline
        RonpfS @NinthWave
        last edited by RonpfS

        @ninthwave Disable pfblockerNG before doing update.
        Restart Resolver from Services > Tab may bring back internet.
        Monitor Systems logs and pfblockerng logs to find out what is done.

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        N 2 Replies Last reply Reply Quote 1
        • N Offline
          NinthWave @RonpfS
          last edited by

          @ronpfs said in package update | no internet until reroot or reboot:

          @ninthwave Disable pfblockerNG before doing update.
          Restart Resolver from Services > Tab may bring back internet.
          Monitor Systems logs and pfblockerng logs to find out what is done.

          Will try that on next update.

          I just expected that the "update button" did stop it prior to updating.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            SteveITS Rebel Alliance @NinthWave
            last edited by

            @ninthwave
            re: unbound not starting:
            https://forum.netgate.com/topic/159094/pfblockerng-v3-0-0_6-update/4
            and
            https://redmine.pfsense.org/issues/11398
            Short answer: check and start unbound (DNS Resolver) after updating pfBlocker. I've had it start unbound sometimes but other times it is left stopped.

            Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
            Upvote 👍 helpful posts!

            1 Reply Last reply Reply Quote 0
            • N Offline
              NinthWave @RonpfS
              last edited by

              @ronpfs
              Disabling the package prior updating did the job.

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