Snort mailing list archives
duplicate preprocessor error
From: Ted Llewellyn <llewell () ieee org>
Date: Sat, 22 Feb 2003 16:01:21 -0500
I am getting an error when I run snort: Initializing Preprocessors! ERROR (null) (0) => Duplicate preprocessor keyword! Fatal Error, Quitting.. Please note that my snort.conf file consists entirely of: var HOME_NET any var EXTERNAL_NET anyIn other words, there are no preprocessor keywords. So, perhaps someone could tell me what this error report really means.
This is snort compiled from source 1.9.0 with mysql and spade support (in other words, I applied the spade patch and told it where to find mysql). This is a Debian woody system, kernel 2.4.16, glibc, gcc 2.95 I think.
I compiled on a different, although also a Debian machine, with spade support and did not get this error. The only difference is the mysql support. When I couldn't find a duplicate preprocessor entry I tried the stripped down snort.conf and still get the error. In fact I get the error when I specify the -c option at all; I got it once when I didn't put in a correct filename. So, this has nothing to do with the snort.conf, it has something to do with the build.
FYI, snort does run in packet sniffing mode with just the -v switch.Is this a known bug? An unknown bug? I see that someone asked this question before, and didn't seem to get any kind of answer that would help them.
So, here's my config.log: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:587: checking for a BSD compatible install configure:640: checking whether build environment is sane configure:697: checking whether make sets ${MAKE} configure:743: checking for working aclocal configure:756: checking for working autoconf configure:769: checking for working automake configure:782: checking for working autoheader configure:795: checking for working makeinfo configure:811: checking for gcc configure:924: checking whether the C compiler (gcc ) works configure:940: gcc -o conftest conftest.c 1>&5 configure:966: checking whether the C compiler (gcc ) is a cross-compiler configure:971: checking whether we are using GNU C configure:999: checking whether gcc accepts -g configure:1034: checking for gcc option to accept ANSI C configure:1113: checking for ranlib configure:1144: checking for gcc configure:1257: checking whether the C compiler (gcc -g -O2 ) works configure:1273: gcc -o conftest -g -O2 conftest.c 1>&5configure:1299: checking whether the C compiler (gcc -g -O2 ) is a cross-compile
r configure:1304: checking whether we are using GNU C configure:1332: checking whether gcc accepts -g configure:1399: checking host system type configure:1423: checking whether byte ordering is bigendian configure:1656: checking for sparc alignment configure:1668: checking how to run the C preprocessor configure:1751: checking for strings.h configure:1791: checking for string.h configure:1831: checking for stdlib.h configure:1871: checking for unistd.h configure:1911: checking for sys/sockio.h configure:1951: checking for paths.h configure:1990: checking for inet_ntoa in -lnsl configure:2040: checking for socket in -lsocket configure:2226: checking whether printf must be declared configure:2226: checking whether fprintf must be declared configure:2226: checking whether syslog must be declared configure:2226: checking whether puts must be declared configure:2226: checking whether fputs must be declared configure:2226: checking whether fputc must be declared configure:2226: checking whether fopen must be declared configure:2226: checking whether fclose must be declared configure:2226: checking whether fwrite must be declared configure:2226: checking whether fflush must be declared configure:2226: checking whether getopt must be declared configure:2226: checking whether bzero must be declared configure:2226: checking whether bcopy must be declared configure:2226: checking whether memset must be declared configure:2226: checking whether strtol must be declared configure:2226: checking whether strcasecmp must be declared configure:2226: checking whether strncasecmp must be declared configure:2226: checking whether strerror must be declared configure:2226: checking whether perror must be declared configure:2226: checking whether socket must be declared configure:2226: checking whether sendto must be declared configure:2226: checking whether vsnprintf must be declared configure:2226: checking whether snprintf must be declared configure:2226: checking whether strtoul must be declared configure:2286: checking for snprintf configure:2341: checking for strlcpy configure:2396: checking for strlcat configure:2451: checking for strerror configure:2514: gcc -c -g -O2 -Wall conftest.c 1>&5 configure: In function `main':configure:2510: warning: assignment discards qualifiers from pointer target type
configure:2554: checking for floor in -lm configure:2603: checking for pcap_datalink in -lpcap configure:2686: checking for mysql configure:2755: checking for compress in -lz configure:4088: checking for u_int8_t configure:4121: checking for u_int16_t configure:4154: checking for u_int32_t configure:4210: checking for a BSD compatible install ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ 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
Current thread:
- duplicate preprocessor error Ted Llewellyn (Feb 22)
- Re: duplicate preprocessor error Erek Adams (Feb 22)
- Re: duplicate preprocessor error Andrew R. Baker (Feb 22)
- Re: duplicate preprocessor error Ted Llewellyn (Feb 22)
- Re: duplicate preprocessor error Andrew R. Baker (Feb 22)
- Re: duplicate preprocessor error Jim Hoagland (Feb 23)
- Re: duplicate preprocessor error Ted Llewellyn (Feb 22)
- duplicate preprocessor error fixed Ted Llewellyn (Feb 22)