Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: AT&T.Net (coppageatt.net)
Date: Thu May 09 2013 - 10:33:18 CDT
I'm still getting non descriptive alerts. For example "Snort Alert [124:10:1]. I'm wondering if our pulled pork is setup correctly. Our Pulledpork server is running on a cent 5.5 and our sensors were upgraded to cent 6.3.
Everything including the 5.5 box has snort 18.104.22.168 installed on it. In the pulledpork.conf the dist is defined as: "distro=Centos-5-4". Could the distro being defined as 5.4 be the problem and should it be "distro=Centos-6-3"? Or could the Pulledpork server being an old OS be the issue?
I'm new to snort and this contract and the problem seemed to start happening when they started upgrade from cent 5.5 to 6.3 and upgrading from an older version of snort. I think we still have a couple of sensors on Cent 5.5 and an older version of snort.
Sent from mobile device via my thumbs.
On May 6, 2013, at 2:23 PM, Joel Esler <jeslersourcefire.com> wrote:
> Good to hear you got it squared away.
> On May 6, 2013, at 1:19 PM, AT&T.Net <coppageatt.net> wrote:
>> Thank Joe,
>> In looking how this box was set up, pulled pork is being used on a central server but one of the scripts being used to push the rules and that file to all the sensors was pulling from the wrong location and therefore the correct Sid file was not being pushed.
>> Sent from mobile device via my thumbs.
>> On May 6, 2013, at 11:06 AM, Joel Esler <jeslersourcefire.com> wrote:
>>> On May 6, 2013, at 10:59 AM, "AT&T.Net" <coppageatt.net> wrote:
>>>> My snort is giving me an alert for example. Snort Alert [1:24889:0]. When I look at my snort.rules file there is rev 1 but not a rev 0. If the last number is referencing the rev, why would it have fired on a non existing rev? I've searched my old archived rules on the server and other rules and don't have that SID with a rev 0.
>>> That rule is at rev:1. We start all rules at Rev 1.
>>> So, I am thinking two things
>>> #1 -- You aren't using pulledpork to manage your downloads (which as part of it's download and managing process, it creates the sid-msg.map for you)
>>> #2 -- Your barnyard2 instance isn't reading the sid-msg.map file that pulledpork generates.
>>> Joel Esler
>>> Senior Research Engineer, VRT
>>> OpenSource Community Manager
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Snort-users mailing list
Go to this URL to change user options or unsubscribe:
Snort-users list archive:
Please visit http://blog.snort.org to stay current on all the latest Snort news!