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

    2.3.4-p1 Breaks PFBlockerNG broke one VLAN, rest ok

    Scheduled Pinned Locked Moved pfBlockerNG
    3 Posts 2 Posters 612 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
      peter808
      last edited by

      I also went into problems after upgrading to 2.3.4-p1.

      I have two physical NICs in my pfsense-box and 2 additional VLANs.

      After upgrading pfsense, PFB does not work on just one of my VLAN-interfaces. The others are working without any problems and I did not change anything after upgrading PFS.

      Also the logs do not show any error on this.

      What I tried is deactivating and activating the VLAN-interface in PFB, restarted the PFB-service an the whole machine.  I also can ping 10.10.10.1 from the VLAN and reach the corresponding web-address via browser, seing the point on a black page.

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

        push

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

          To confirm, can you ping 10.10.10.1 from each VLAN, and can you browser to 10.10.10.1 and get the 1x1 pix from each VLAN?

          "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
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.