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

    3.0.0.7 -> WAN stops working periodically

    Scheduled Pinned Locked Moved pfBlockerNG
    9 Posts 5 Posters 980 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.
    • I
      im_not_a_robot
      last edited by im_not_a_robot

      About once a day all outbound connections stop working since I moved to 3.0.0.x. on pfsense 2.4.5p1. After a bit of trial and error I realized that a quick restart of pfsense fixes it immediately.

      • pfblockerNG -> general -> General Settings -> pfblockerNG -> "enable" set to off then on

      I looked at error.log and pfblockerng.log and did not see any problems.

      Has anyone else run into this? Any suggestions what I can test or log next time this happens? Thanks!

      GertjanG G 2 Replies Last reply Reply Quote 0
      • GertjanG
        Gertjan @im_not_a_robot
        last edited by

        @im_not_a_robot said in 3.0.0.7 -> WAN stops working periodically:

        Any suggestions

        Leave pfblockerNG activated and de activate / remove (!) all your feeds. This is situation when you installed it. It does nothing. pfblockerNG without feeds is just one big no-op.

        The pfblockerNG logs are useful when you detect that sites or other destinations are blocked that you need. Check the FirewallpfBlockerNG > Alerts page, see the Alerts and DNSBL lists.

        If the entire WAN goes away, see the general system log, Status> System Logs > System > General and this one Status > System Logs >System > DNS Resolver and check if unbound is starting often.

        Monitoring info here : Status > Monitoring, check Quality on interface WAN : any packer losses ?

        Are you using the default 'unbound' mode or the new python mode ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • T
          Tzvia
          last edited by

          Well, it sounds like you can log into the PFSense GUI, so I would go to Diagnostics and do a DNS lookup and a PING from there to see if PFSense is having a DNS issue or what. Would also go to the main Dashboard and just see if you have a WAN IP (probability do). From there, it would be a good idea as mentioned already above by Gertjan, to check unbound. Is PFBlockerNG in Python mode?

          Tzvia

          Current build:
          Hunsn/CWWK Pentium Gold 8505, 6x i226v 'micro firewall'
          16 gigs ram
          500gig WD Blue nvme
          Using modded BIOS (enabled CSTATES)
          PFSense 2.72-RELEASE
          Enabled Intel SpeedShift
          Snort
          PFBlockerNG
          LAN and 5 VLANS

          I 1 Reply Last reply Reply Quote 0
          • I
            im_not_a_robot @Tzvia
            last edited by

            @tzvia @Gertjan both posts are really helpful. I am just waiting for this to happen again so I can go through both of your sets of steps.

            I am still on standard unbound mode (no python) since I like to have the Resolver DHCP Registration feature enabled. Thanks to both of you for the info, I will reply back if/when it happens again and which steps yielded info.

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

              @im_not_a_robot said in 3.0.0.7 -> WAN stops working periodically:

              since I like to have the Resolver DHCP Registration feature enabled.

              Use Static DHCP only, DHCP Registration restart unbound at every new lease and that will cause DNS service disruptions and problems when new leases are issued at a faster rate than Unbound restart time.

              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

              I 1 Reply Last reply Reply Quote 0
              • I
                im_not_a_robot @RonpfS
                last edited by

                @ronpfs Interesting point. This is on a small home network (<100 devices) and almost every device has a static IP so unless a device is misbehaving that seems less likely. Would there be any evidence in the logs if I run into that situation?

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

                  @im_not_a_robot
                  You will see timestamps in DHCP log that matches Unbound restart in Resolver log.

                  For more : https://forum.netgate.com/search?term=DHCP%20Registration&in=posts&matchWords=all&categories[]=62&sortBy=timestamp&sortDirection=desc&showAs=posts

                  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

                  1 Reply Last reply Reply Quote 0
                  • G
                    Griffo @im_not_a_robot
                    last edited by

                    @im_not_a_robot I believe I am having the same issue. Internet traffic just stops, as we are all WFH at the moment I have had to disable it completely, but will try to collect more information on the weekend.

                    I 1 Reply Last reply Reply Quote 0
                    • I
                      im_not_a_robot @Griffo
                      last edited by

                      @griffo @ronpfs in my case things have gotten more interesting. I can see a restart before each outage. So this suggests

                      1. an unplanned reboot happening about once a week
                      2. pfblockerng or unbound does not start up correctly upon restart

                      #2 is fixed by re-starting pfblockerng but #1 will need more digging. It's easy to see if this is happening by checking NTP logs (search for "Starting") or system logs.

                      The reboot is interesting. In all three cases LAN was fine, WAN was knocked out by the restart, CPU temps are very good, and in at least two of the cases I was making network adjustments through the unifi UI for my access points at the time that things went down. Possibly coincidence.

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