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

    Hide TCP Blocks in logs

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 3 Posters 914 Views 3 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.
    • L Offline
      Lurick LAYER 8
      last edited by

      I know this is mostly down to timing issues from Google and other CDNs delaying the TCP:FA/FPA/PA/RA etc but I was wondering if there was a way to just hide this return traffic from my firewall logs. I tried adding a default block to the end of my rules however it stops snort logs as well so I'm wondering if I'm missing an option to block default traffic but still have snort logs show up and other blocks but just hide the TCP traffic blocks in the logs.

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator @Lurick
        last edited by

        @lurick how does a block rule at the end that doesn't log on you wan stop snort from doing what exactly?

        What exactly does it stop snort from showing/doing?

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07 | Lab VMs 2.8, 25.07

        L 1 Reply Last reply Reply Quote 0
        • L Offline
          Lurick LAYER 8 @johnpoz
          last edited by

          @johnpoz In the firewall logs under Status > System Logs > Firewall logs is what I'm looking at, sorry for not being clear.

          johnpozJ 1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            You can disable logging anything blocked by the default block rule, which is usually what block that:
            https://docs.netgate.com/pfsense/en/latest/monitoring/logs/settings.html#global-log-settings

            If you still want to log other traffic being blocked by the default rule you would need to add you own block rule that matches only that out-of-state TCP traffic and doesn't have logging enabled so you can leave default rule logging enabled.

            Steve

            1 Reply Last reply Reply Quote 1
            • johnpozJ Offline
              johnpoz LAYER 8 Global Moderator @Lurick
              last edited by

              @lurick how does that have anything to do with snort?

              Yeah if you tell the firewall not to log X, X wouldn't be in the logs - but what does that have to do with snort?

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 25.07 | Lab VMs 2.8, 25.07

              L 1 Reply Last reply Reply Quote 0
              • L Offline
                Lurick LAYER 8 @johnpoz
                last edited by

                @johnpoz The reason I mentioned snort is it wouldn't show blocked due to snort in the logs with a default block any any at the end of the rules with logging disabled. I didn't think about just blocking and not logging TCP states like FPA/PA/etc. and not logging those since I completely blanked that it would still allow legit traffic, just block out of state traffic by putting that deny at the bottom of the list for WAN stuff.

                1 Reply Last reply Reply Quote 0
                • stephenw10S Offline
                  stephenw10 Netgate Administrator
                  last edited by

                  Yup, that would work.

                  Traffic blocked by Snort shouldn't appear under the default block rule though. Snort has it's own rule it blocks with in Legacy mode. Or in in-line mode it blocks before the firewall rules are parsed anyway.

                  Steve

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