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

    pfBlockerNG-devel 3.0.0_7 need enable/disable after HA failover

    Scheduled Pinned Locked Moved pfBlockerNG
    4 Posts 2 Posters 586 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
      agarkauskas
      last edited by

      After a lot of bumps my pfsense HA cluster is online with dual WAN. Yeah!!!

      But...

      When I shutdown the master node the back up node take over in a few seconds and my DNS Resolver stops working.

      Routing is ok, I can ping IPs, but DNS resolution fails. After I hit Disable/Enable in pfBlocker everything works again.

      Anyone had a similar problem?

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

        @agarkauskas
        Are you using pfBlockerNG-devel v3.0.0_7? Check the system.log for more clues.

        "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/

        A 2 Replies Last reply Reply Quote 0
        • A
          agarkauskas @BBcan177
          last edited by

          @bbcan177 Marcelo! Tu é o cara!

          I think I found the problem. Double checking the logs I realized my TIMEZONE settings were different in both pfsense boxes. Box one is configured with America/Sao Paulo timezone. Box two was configured with GMT-3 - which SHOULD be the same - but it was not, it was behaving like GMT+3, so server one was 6 hours behind server two.

          I made the correction and it looks like it is working now. I will run more tests, lets see if it confirms to be the actual problem.

          1 Reply Last reply Reply Quote 0
          • A
            agarkauskas @BBcan177
            last edited by

            @bbcan177 Confirmed. It was the 6 hours time difference.

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