Snort mailing list archives

Re: Problems compiling SnortSam on OpenBSD


From: Joel Esler <jesler () sourcefire com>
Date: Wed, 5 Sep 2012 12:03:26 -0400

I recommend using the latest git version of barnyard2 which has snortsam capability built in.  Support for SnortSam 
compiled directly into Snort hasn't been done in a long time I believe.

--
Joel Esler
Senior Research Engineer, VRT
OpenSource Community Manager
Sourcefire

On Sep 5, 2012, at 11:24 AM, ML mail <mlnospam () yahoo com> wrote:

Hi,

I would like to integrate SnortSam in my Snort installation and therefore I am currently trying to compile the latest 
version 2.70 of it on OpenBSD 4.9 (i386). It looks like I can't get it to compile as I get some errors and no 
snortsam binary at the end :(

Here is the output of makeshortsam.sh:

-------------------------------------------------------------------------------

Building SnortSam (release)
-------------------------------------------------------------------------------
ssp_pf.c: In function 'PFParse':
ssp_pf.c:134: error: storage size of 'paddr' isn't known
ssp_pf.c:221: error: 'DIOCBEGINADDRS' undeclared (first use in this function)
ssp_pf.c:221: error: (Each undeclared identifier is reported only once
ssp_pf.c:221: error: for each function it appears in.)
ssp_pf.c:230: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:293: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:356: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:420: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:463: error: 'struct pfioc_rule' has no member named 'pool_ticket'
-------------------------------------------------------------------------------
Building SnortSam (debug)
-------------------------------------------------------------------------------
ssp_pf.c: In function 'PFParse':
ssp_pf.c:134: error: storage size of 'paddr' isn't known
ssp_pf.c:221: error: 'DIOCBEGINADDRS' undeclared (first use in this function)
ssp_pf.c:221: error: (Each undeclared identifier is reported only once
ssp_pf.c:221: error: for each function it appears in.)
ssp_pf.c:230: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:293: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:356: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:420: error: 'struct pfioc_rule' has no member named 'pool_ticket'
ssp_pf.c:463: error: 'struct pfioc_rule' has no member named 'pool_ticket'
Done.

Anyone know what is going wrong here?

Best,
ML

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users

Please visit http://blog.snort.org to stay current on all the latest Snort news!


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users

Please visit http://blog.snort.org to stay current on all the latest Snort news!


Current thread: