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

    Snort refused to start after this mornings update

    IDS/IPS
    1
    1
    1.1k
    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.
    • B
      battles
      last edited by

      My system updates the snort rules (pay also) every 6 hours and this morning after a 615 boot, it updated the 'Snort GPLv2 Community Rules' only.  Snort was running in Services, but I couldn't get it to start on WAN in Services Snort Interfaces.  After I unchecked all rules, it started in on WAN in Services Snort Interfaces.  However, the entire pfSense server is continuously locking up.  I can't get in via 192.168.1.1 or sshd terminal.  The last time I restarted it, I stopped snort all together and it has been running continuously.  I was wondering if a bad snort rule could cause this?

      pfSense 2.3.4-RELEASE-p1 (i386)
      FreeBSD 10.3-RELEASE-p19
      pfBlockerNG 2.1.2_1
      Snort Security 3.2.9.5_3
      Intel(R) Atom(TM) CPU N270 @ 1.60GHz

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