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

    Snort: List of blocked IPs not cleaned up

    Scheduled Pinned Locked Moved pfSense Packages
    6 Posts 4 Posters 2.3k 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.
    • F
      Fesoj
      last edited by

      Using pfSense 2.0.1-RELEASE (i386) with Snort 2.9.1 pkg v. 2.1.1 with the setting "Remove blocked hosts every: 1 Hour" and "Block offenders: yes" for the Snort enabled interface, I found that the list of blocked IPs is not cleaned up and blocked machines remain blocked after the time penalty has elapsed.

      Is this a known (minor) problem?

      I have another machine with pfSense 1.2.3 where the list is properly maintained.

      1 Reply Last reply Reply Quote 0
      • J
        java007md
        last edited by

        Also running Snort 2.9.1 pkg v. 2.1.1 with the blocked hosts set to be removed after one hour - this is working for me.

        You have probably already tried toggling the snort service off/back on, but if not I would give that a try.

        1 Reply Last reply Reply Quote 0
        • F
          Fesoj
          last edited by

          … the machine has even been restarted and the blocked entries still remain.

          I'd probably to need to give some more details: snort is installed on the WAN side with no offenders being blocked and on the LAN side where only a Anti-P2P rules are activated and both source and destination offending addresses are blocked.

          1 Reply Last reply Reply Quote 0
          • C
            Cino
            last edited by

            re-appy the Global Settings page and Interface Edit: If Settings page. This should re-create the missing cron job

            1 Reply Last reply Reply Quote 0
            • F
              Fesoj
              last edited by

              @Cino:

              re-appy the Global Settings page and Interface Edit: If Settings page. This should re-create the missing cron job

              Yes, this seemed to have worked. The old entries were automatically deleted. Thanx.

              1 Reply Last reply Reply Quote 0
              • T
                taryezveb
                last edited by

                @Cino:

                re-appy the Global Settings page and Interface Edit: If Settings page. This should re-create the missing cron job

                I was having the same issue, following the above worked for me as well. Thanks

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