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

    Problem PFblockerNG 2.0.17 WAN/LAN

    Scheduled Pinned Locked Moved pfBlockerNG
    2 Posts 2 Posters 1.0k 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.
    • M
      magusi
      last edited by

      Hello,

      a client uses pfsense 2.2 already and sets up a new machine with pfsense 2.3. With new machine we have a problem with WAN/LAN assignment of the floating rules.

      We added pfblockerng 2.0.17 to pfsense 2.3.1_5 and geoblocking did not work as expected (it blocks nothing), when in the pfblockerng config:

      Interface rules/Configuration -> "inbound firewall rules" is set to "WAN" and "outbound firewall rules" is set to "LAN".
      This setting worked on the old machine (pfsense 2.2.6, pfblockerng 2.0.6).

      For a test, we changed the setting on the new machine to inbound = LAN and outbound = WAN, and it worked and blocked the defined adresses.

      Any idea, why this working?

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

        If you restored a config from a different box, maybe the interfaces are different in this hardware. Check the interface assignments in pfSense, as the package reads those pfSense settings.

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