Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    v2.9.0 : DNSBL VIP configurations lost on reboot

    Scheduled Pinned Locked Moved pfBlockerNG
    3 Posts 2 Posters 119 Views 2 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.
    • J Offline
      jypsilantis
      last edited by

      I updated my backup HA instance from v2.8.1 to 2.9.0, and noticed that the DNSBL VIP (configured via Firewall/pfBlockerNG/DNSBL) is lost whenever the firewall is rebooted. As a result pg\fBlockerNG fails to start, until the VIP is manually reentered.

      Has anyone else seen this issue? If so, have you managed to resolve it?

      tinfoilmattT 1 Reply Last reply Reply Quote 0
      • tinfoilmattT Offline
        tinfoilmatt LAYER 8 @jypsilantis
        last edited by

        https://forum.netgate.com/topic/200480/upgrade-to-3_2_14_1-causes-pfb_dnsbl-service-to-not-start?_=1788484369042

        block out log on { ix0 } inet from any to any
        block out log on { ix0 } inet6 from any to any

        1 Reply Last reply Reply Quote 0
        • J Offline
          jypsilantis
          last edited by

          Thank you for the information.

          Unfortunately this did not work for me.

          I have since backed up, rebuilt and restored my primary firewall, (which was th second of th two scheduled for an update - I always start with the backup) and the issue disappeared.

          I suspect that there has been a change in the structure of the replicated data expected from the primary, and that this has resulted in the "clobbering" of configs made directly on the backup. Coupled with an issue with the initiation of an update on the primary.

          The rebuild resolved both. I will try updating the primary first on the next update, rather than the other way around.

          1 Reply Last reply Reply Quote 1
          • First post
            Last post
          Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
          Privacy Policy · Cookie Policy