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

    Suricata blocks homenet ip address

    Scheduled Pinned Locked Moved IDS/IPS
    4 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.
    • C
      crester
      last edited by

      Hello.

      I have configured manually few IP address with an alias and overrided home_net into interface configuration of suricata.
      However it blocks these ip addresses if they offends Suricata.
      I thought that adding IP addresses to home_net they aren't blocked by suricata/snort, but it looks it isn't. … isn't it?

      Thank you

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

        Hello.
        I have addedd same IP groups to pass list and it doesn't work neither.
        always one of these IPs offends Suricata, it is blocked.

        Suricata only blocks "SRC"

        I have seen this post
        https://forum.pfsense.org/index.php?topic=88840.msg546704#msg546704
        in 2015 with the same issue, but no answer.

        Some help will be appreciated.
        Thank you

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

          I don't know why but rebooting had worked.

          1 Reply Last reply Reply Quote 0
          • bmeeksB
            bmeeks
            last edited by

            @crester:

            I don't know why but rebooting had worked.

            99 times out of 100 this means you had duplicate Snort instances running on the same interface.  To the GUI, one of those process instances is like a zombie and lost.  So any changes made to HOMENET or anything else in the GUI don't get applied to that running zombie process.  Rebooting will kill everything and then you get back to a single Snort instance per configured interface and things are normal.

            Bill

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