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

Suricata - How to apply different blocking rules per subnet?

pfSense Packages
suricata blocking rules
3
4
211
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.
  • P
    pslinn
    last edited by pslinn Aug 9, 2024, 6:25 PM Aug 9, 2024, 6:25 PM

    I am running pfsense 2.7.2 with all the latest patches on a pc with Intel i5-4570 CPU, 32 Gb of RAM, Supermicro AOC SGP-i4 4 port 1 GBe card and 2 1Gbe 1 port cards.

    I have configured pfSense to have multiple VLANs on LAN and separate subnets on OPT1 to OPT5.

    I am trying to better understand how Suricata has been implemented.

    I have setup separate Suricata interface rules for each VLAN and subnet.

    I believe that I am seeing Suricata implement the same blocking rules across all VLANs and subnets. What I want it to do is implement independent blocking rules for each VLAN and subnet.

    Is this possible with the current implementation?

    Regards.

    S 1 Reply Last reply Aug 9, 2024, 7:17 PM Reply Quote 0
    • S
      SteveITS Galactic Empire @pslinn
      last edited by Aug 9, 2024, 7:17 PM

      @pslinn Suricata works at a low level so cannot distinguish VLANs from their parent interface. Just run one instance on each parent. I'm afraid there isn't a way to run separate instances.

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      P 1 Reply Last reply Aug 10, 2024, 1:02 AM Reply Quote 0
      • P
        pslinn @SteveITS
        last edited by Aug 10, 2024, 1:02 AM

        @SteveITS Thanks

        1 Reply Last reply Reply Quote 0
        • B
          bmeeks
          last edited by Aug 10, 2024, 4:24 PM

          Suricata by default places the physical interface in promiscuous mode, so all traffic traversing the physical interface is seen by all Suricata instances running on the physical interface. That means there is no benefit to creating separate Suricata instances for each VLAN, because a single instance will see the traffic from all VLANs.

          You can, to a limited extent, tailor how a given Suricata instance responds to traffic by using customized HOME_NET and/or EXTERNAL_NET variables and making sure all the rules you are enabling use the $HOME_NET and $EXTERNAL_NET conditionals in the rule text.

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