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

    Snort package doesn't shows up on the available package list

    Scheduled Pinned Locked Moved pfSense Packages
    12 Posts 4 Posters 2.3k 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.
    • P
      phil.davis
      last edited by

       <package><name>snort</name>
      	<version>2.9.6.2 pkg v3.1.4</version>
      	<required_version>2.1</required_version>
      	<status>Stable</status></package> 
      
      

      Some selected bits of pkg_config.8.xml
      The current version of Snort requires pfSense 2.1 or later.
      pfSense V2.0.1 is now very old - time to upgrade and get loads of bug and security fixes.

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • Y
        ypmict
        last edited by

        @phil.davis:

         <package><name>snort</name>
        	<version>2.9.6.2 pkg v3.1.4</version>
        	<required_version>2.1</required_version>
        	<status>Stable</status></package> 
        
        

        Some selected bits of pkg_config.8.xml
        The current version of Snort requires pfSense 2.1 or later.
        pfSense V2.0.1 is now very old - time to upgrade and get loads of bug and security fixes.

        I see…
        thanks for your reply...
        One question though.. If I auto invoke the uprade, does all my pfsense setting intact? or is it safe using this auto update from v2.0.1 to v2.1.5?
        thank you very much for your reply

        1 Reply Last reply Reply Quote 0
        • P
          phil.davis
          last edited by

          Backup your config (and system) before upgrading - this is standard advice in the computing world.
          The upgrade preserves (or converts as needed) all settings.
          It also reinstalls all packages with the latest version.
          You might need to access the webGUI of some packages and enable them again after an upgrade (e.g. pfBlocker disables itself after an upgrade/reinstall).

          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

          1 Reply Last reply Reply Quote 0
          • BBcan177B
            BBcan177 Moderator
            last edited by

            @ypmict:

            One question though.. If I auto invoke the uprade, does all my pfsense setting intact? or is it safe using this auto update from v2.0.1 to v2.1.5?

            There should be an option in the Snort:Global Tab to "Keep Snort Settings After Deinstall".

            Not sure if there will be issues or not, so Please ensure you make a backup of the Config.

            "Experience is something you don't get until just after you need it."

            Website: http://pfBlockerNG.com
            Twitter: @BBcan177  #pfBlockerNG
            Reddit: https://www.reddit.com/r/pfBlockerNG/new/

            1 Reply Last reply Reply Quote 0
            • Y
              ypmict
              last edited by

              thanks to both of you for the reply…  :)

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

                @phil.davis:

                 <package><name>snort</name>
                	<version>2.9.6.2 pkg v3.1.4</version>
                	<required_version>2.1</required_version>
                	<status>Stable</status></package> 
                
                

                Some selected bits of pkg_config.8.xml
                The current version of Snort requires pfSense 2.1 or later.
                pfSense V2.0.1 is now very old - time to upgrade and get loads of bug and security fixes.

                Phil is correct.  At the request of the pfSense developers, support for pfSense versions older than 2.1 was removed a while back.  I will also admit that the move made maintaining the code easier because it no longer had to cope with multiple versions of the PHP engine…  ;)

                Bill

                1 Reply Last reply Reply Quote 0
                • Y
                  ypmict
                  last edited by

                  Hi…
                  after i upgrade my pfsense to the latest version and reinstaling snort...
                  I got some errors now after i try to start snort

                  as below:

                  Nov 14 00:08:03 snort[88692]: FATAL ERROR: /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/rules/snort.rules(5030) Unknown rule option: 'stream_size'.
                  Nov 14 00:08:03 php: /snort/snort_interfaces.php: The command '/usr/local/bin/snort -R 46086 -D -q -l /var/log/snort/snort_bge046086 –pid-path /var/run --nolock-pidfile -G 46086 -c /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/snort.conf -i bge0' returned exit code '1', the output was ''

                  ...hope you guys can help me..
                  thank you very much

                  1 Reply Last reply Reply Quote 0
                  • BBcan177B
                    BBcan177 Moderator
                    last edited by

                    @ypmict:

                    Nov 14 00:08:03 snort[88692]: FATAL ERROR: /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/rules/snort.rules(5030) Unknown rule option: 'stream_size'.
                    Nov 14 00:08:03 php: /snort/snort_interfaces.php: The command '/usr/local/bin/snort -R 46086 -D -q -l /var/log/snort/snort_bge046086 –pid-path /var/run --nolock-pidfile -G 46086 -c /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/snort.conf -i bge0' returned exit code '1', the output was ''

                    Enable the "Stream5" Pre-Processor, as the rule is failing because its not enabled.

                    See the following link:

                    https://forum.pfsense.org/index.php?topic=82346.msg450504#msg450504

                    "Experience is something you don't get until just after you need it."

                    Website: http://pfBlockerNG.com
                    Twitter: @BBcan177  #pfBlockerNG
                    Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                    1 Reply Last reply Reply Quote 0
                    • Y
                      ypmict
                      last edited by

                      @BBcan177:

                      @ypmict:

                      Nov 14 00:08:03 snort[88692]: FATAL ERROR: /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/rules/snort.rules(5030) Unknown rule option: 'stream_size'.
                      Nov 14 00:08:03 php: /snort/snort_interfaces.php: The command '/usr/local/bin/snort -R 46086 -D -q -l /var/log/snort/snort_bge046086 –pid-path /var/run --nolock-pidfile -G 46086 -c /usr/pbi/snort-amd64/etc/snort/snort_46086_bge0/snort.conf -i bge0' returned exit code '1', the output was ''

                      Enable the "Stream5" Pre-Processor, as the rule is failing because its not enabled.

                      See the following link:

                      https://forum.pfsense.org/index.php?topic=82346.msg450504#msg450504

                      Hi…
                      thank you for the reply.. very much appreciated..

                      but when I checked my Stream5 pre-proc it already tick and enable…

                      after sometime I try to disable the SIP and … weird it can now start/run the Snort..
                      do you know why it happened?

                      thanks...

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

                        You need to enable the SIP preprocessor or else you will encounter additional start failures.  NEVER DISABLE ANY PREPROCESSORS except perhaps Portscan and Sensitive Data.  If you don't run any SCADA rules, then you can disable those two (Modbus and DNP3).

                        Your problems are likely a result of staying on an older version of pfSense and Snort.  The upgrade may have left some defaults unset.  That's just a guess.  I suggest blowing away your Snort configuration and starting from scratch.  You can do that by deleting all the configured interfaces in Snort and creating them anew.

                        Bill

                        1 Reply Last reply Reply Quote 0
                        • Y
                          ypmict
                          last edited by

                          Hi..
                          I right now already uninstalled and uncheck the save config after deinstalled and then reinstalled snort fresh… but it shows the same error when i try to start it...
                          anyway that I need to search all snort config file and delete manually by using the ssh?

                          thanks..

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