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

    Log to pfBlocker Alerts only instead of the firewall logs

    Scheduled Pinned Locked Moved pfBlockerNG
    5 Posts 2 Posters 1.1k 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
      mind12
      last edited by

      Hi,

      Could you please help me with this? I would like to log the pfBlocker events only to the alerts tab and leave the firewall logs completely.
      Is this possible? I know I can disable logging for the IP aliases individually but that's not my goal.
      (I dont plan updating to 2.5 soon.)

      My system:
      2.4.5-RELEASE-p1
      pfBlockerNG-devel 3.0.0_10

      Thank you.

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

        Logging of firewall rules is a 'kernel' thing.
        Rules created by pfBlockerNG set the log check box.
        pfBlockerNG reads the firewall syslog to create it's own event list.

        What is not the case : the firewall communicates to pfBlockerNG.
        As such, you can't (shouldn't) stop the firewall logging by editing the rules that have in their description " ..... auto rule" : it would impact pfBlockerNG .

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

        M 1 Reply Last reply Reply Quote 0
        • M
          mind12 @Gertjan
          last edited by

          @gertjan
          I see, then my only option is to disable logging for an alias completely.
          I dont care what IPs are blocked Inbound to my WAN port except if I need to create an exception.
          Should I disable inbound blocking completely on WAN and leave it to the default block rule?
          My only open ports are for OpenVPN and IPSEC. Do you have any suggestions?

          Thank you.

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

            @mind12

            True : logging WAN that hit the wall is useless.

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

            M 1 Reply Last reply Reply Quote 0
            • M
              mind12 @Gertjan
              last edited by

              I turned off inbound filtering completely instead and left the logging on for the outbound traffic.
              It would be great if we could configure inbound and outbound logging separately in pfBlocker.

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