[Oisf-users] Tuning Suricata (2.0beta1) -- no rules and lots of packet loss

[Cooper F. Nelson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I already fixed it, this is my current build script.  Running autogen.sh
twice in each source directory fixed the issue for me.


> #!/bin/sh
> 
> cd /usr/src
> 
> git clone git://phalanx.openinfosecfoundation.org/oisf.git
> 
> cd /usr/src/oisf
> 
> git clone -b 0.5.6 git://github.com/ironbee/libhtp.git
> 
> cd /usr/src/oisf/libhtp; ./autogen.sh; ./autogen.sh
> 
> cd /usr/src/oisf; ./autogen.sh; ./autogen.sh
> 
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-geoip CFLAGS="-ggdb -O0"
> 
> make


On 8/24/2013 12:23 AM, Peter Manev wrote:
> On Fri, Aug 23, 2013 at 8:27 PM, Cooper F. Nelson <cnelson at ucsd.edu> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I tried building the latest version from git and it died with this error:
>>
>>> suricata.c: In function 'SCPrintBuildInfo':
>>> suricata.c:677:50: error: 'defined' undeclared (first use in this function)
>>> suricata.c:677:50: note: each undeclared identifier is reported only once for each function it appears in
>>> suricata.c:677:50: error: expected ')' before numeric constant
>>> make[3]: *** [suricata.o] Error 1
>>> make[3]: Leaving directory `/usr/src/oisf/src'
>>> make[2]: *** [all] Error 2
>>> make[2]: Leaving directory `/usr/src/oisf/src'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/usr/src/oisf'
>>> make: *** [all] Error 2
>>
> 
> Could you try building it like this - (just for the purpose of testing
> and pinpointing the issue)?
> 
> git clone git://phalanx.openinfosecfoundation.org/oisf.git && cd oisf/
> && git clone https://github.com/ironbee/libhtp.git -b 0.5.x &&
> ./autogen.sh && ./configure --enable-geoip --enable-profiling
> --with-libnss-libraries=/usr/lib
> --with-libnss-includes=/usr/include/nss/
> --with-libnspr-libraries=/usr/lib
> --with-libnspr-includes=/usr/include/nspr  &&  make clean &&  make &&
> make install &&  ldconfig
> 
> Would you get the same err? I tried it like this and do not have that problem.
> 


- -- 
Cooper Nelson
Network Security Analyst
UCSD ACT Security Team
cnelson at ucsd.edu x41042
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSGGSfAAoJEKIFRYQsa8FWQK8IAImJ98gsqqT7pajnXWqgXCY2
YVwXU8CsIxt/FXu6HlhddRPEqjQWEXl8G2em6824dgiVqV2V1SDJ73wxvhoT8ydr
B+SsG9kTm+RMCEftS6Zj+/swH2tOBypeQoOf4w2y5UeJIg52tKuCgW1kU0EUnBcr
VmdL7jpLYQ1XEmu5XP8kl6ir03nTE5Cw5qktBr5Cux2H0MtHFlYoDPgqJLw36NxG
kDGBnkkQQX9CjUcF+6YGYt1Lq5FcncM8ihxQL6IkUiVCAOj0T3eCDxbfLOnOTb8a
bnOIjKAkb0MDSP9tuTd8lfK9GesGWseaNkOR10X9WXBGV5lQJdZ1Eni8Xy+fHVQ=
=NL9P
-----END PGP SIGNATURE-----