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

    Snort 2.9.2.3 pkg v. 2.5.1 Whitelists

    pfSense Packages
    5
    9
    2.3k
    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.
    • I
      it_adminz
      last edited by

      Snort is ignoring whitelists…

      I have checked all settings and everything seems correct. My alias is setup correct but snort still blocks whitelist ips / addresses.

      I don't know where these are added within the file system, so I could check or manually create these entries.

      Snort is currently off for now untill I can resolve this issue.

      Thanks for any help...

      1 Reply Last reply Reply Quote 0
      • S
        SleepIT
        last edited by

        Same problem here.  I've tried both "Host" and "Network" formats for the Aliases configuration but Snort is not respecting them at all.

        1 Reply Last reply Reply Quote 0
        • I
          it_adminz
          last edited by

          Tried the same thing.

          1 Reply Last reply Reply Quote 0
          • S
            SleepIT
            last edited by

            I haven't figured out a place in the filesystem where the whitelist should be entered either.  I can't find any whitelist files for Snort despite quite a bit of hunting.  Unfortunately I've never used Snort outside of PFSense so I'm not familiar with its config files.

            Still looking…

            1 Reply Last reply Reply Quote 0
            • S
              SleepIT
              last edited by

              Add the following to your suppress list (Services: Snort: Suppression: Edit)

              suppress gen_id 0, sig_id 0, track by_src, ip xxx.xxx.xxx.xxx

              Where xxx.xxx.xxx.xxx is the IP you wish to whitelist.  Make sure to restart Snort so it takes effect.

              "gen_id 0, sig_id 0" is a global parameter and causes it to apply to all rules.

              I've tested it every which way and it certainly appears to be working!

              1 Reply Last reply Reply Quote 0
              • I
                it_adminz
                last edited by

                Thanks! Worked like a charm…

                1 Reply Last reply Reply Quote 0
                • M
                  moe2006
                  last edited by

                  Ok, this seems to work for certain IPs, but not for Subnets… I have the same problem adding whitelist, aliases to the config but IPs from Homenet still getting blocked...

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

                    For networks try this in suppress list:
                    suppress gen_id 0, sig_id 0, track by_src, ip [xxx.xxx.xxx.xxx/29,yyy.yyy.yyy.yyy/28,zzz.zzz.zzz.zzz/28]

                    All networks must be in the same suppress line.

                    1 Reply Last reply Reply Quote 0
                    • _
                      _igor_
                      last edited by

                      great, that saved my life :) Had the same problem a while and didnt find a solution.

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