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

    pfBlockerNG devel filtering OPT interface, but why?

    Scheduled Pinned Locked Moved pfBlockerNG
    3 Posts 2 Posters 556 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.
    • N
      NGUSER6947
      last edited by

      Newbie to pfBlocker here. I installed the devel version this morning and used the wizard to configure it. I set both interfaces (in and out) as LAN since I only want pfBlocker to filter on the LAN interface (I use the OPT interface for my work PC, and it's "on its own" so to speak).

      However, I am seeing this on the Unified tab:
      c38c1a7e-919a-47ee-ba3a-747acfafe59c-image.png

      I'm not sure why it's even looking at the OPT interface. Checking the Firewall rules, I only see the one pfBlocker rule on the LAN interface. No pfBlocker rules on the WAN or OPT interfaces.

      Everything seems to be working fine, I'm just curious why this is happening. Thank you.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @NGUSER6947
        last edited by

        @nguser6947 said in pfBlockerNG devel filtering OPT interface, but why?:

        I only want pfBlocker to filter on the LAN interface (I use the OPT interface for my work PC, and it's "on its own" so to speak).

        Check this page : Firewall > pfBlockerNG > IP : you've noticed that you can activate IP Blocking per interface. Like "Put a firewall rule with all the IPs on LAN"bot not on your OPT1 interface. So IP filtering can be done by interface.

        Now, check this page Firewall > pfBlockerNG > DNSBL : you'll notice that you can't select between "DNS requests coming from LAN / OPT1 / etc"
        All DNS requests from all your local LANs are fed into the resolver, and you can't distinguish among them. It's an all or nothing thing.
        There is one exception : you can select Group Policy :

        b2b955b4-14f3-4b22-b1b5-db9a777cda84-image.png

        and exclude IPs. Not network, just IPs.

        So, I tend to say : for now, you can't exclude interfaces or networks yet.

        Btw : I hope to be wrong, of course ;)

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

        N 1 Reply Last reply Reply Quote 0
        • N
          NGUSER6947 @Gertjan
          last edited by

          @gertjan Ok thanks, I'll take a look. As I mentioned, everything seems to be working ok so not a big deal. Thanks for your reply.

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