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

    PFSense V.2.4.5-RELEASE (amd64) and Snort 3.2.9.10_3 not starting

    Scheduled Pinned Locked Moved IDS/IPS
    1 Posts 1 Posters 152 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.
    • peteP
      pete
      last edited by pete

      Haven't paid attention.

      ***Apr 5 09:06:46 php /tmp/snort_em136912_startcmd.php: The command '/usr/local/bin/snort -R 36912 -D -q --suppress-config-log -l /var/log/snort/snort_em136912 --pid-path /var/run --nolock-pidfile -G 36912 -c /usr/local/etc/snort/snort_36912_em1/snort.conf -i em1' returned exit code '1', the output was ''

      Apr 5 09:06:46 snort 71684 FATAL ERROR: /usr/local/etc/snort/snort_36912_em1/snort.conf(6) !any is not allowed in EXTERNAL_NET.***

      First thought it was my cloud flare DNS entry of 1.1.1.1. Removed it and it still errored out. Then disabled IPv6 on my WAN link and Snorts starts with no errors.

      Not sure what my issue is. I want to keep using IPv6 if I can and I did not understand the IPv6 entries that I see in my External interface list.

      • Pete

      Auto mater
      23.09.1-RELEASE (amd64)
      built on Mon Dec 11 12:24:00 CST 2023
      FreeBSD 14.0-CURRENT
      PFSense + Qotom - Master
      PFSense + Jetway - Backup
      PFSense + Jetway - Backup
      PFSense + Generic - Backup

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