[Snort-users] compiling with --enable-inline impacts non-inline sniffing
weberdan at ...11827...
Tue Mar 30 17:22:59 EDT 2010
I configure snort like this: ./configure --enable-ipv6 \
--enable-dynamicplugin --enable-inline --enable-ipfw \
I compile, then run snort like this:
snort -i lo -c snort.conf
where "snort.conf" is an empty file. And it reads from a different
interface, not lo.
Looking in the source, things are okay in the SnortConfigso bad in
MergeSnortConfs(), which I
think is there to merge the configuration on my command line with
whatever is read from the configuration file. Around line 4620
#if defined(GIDS) && defined(IPFW)
config_file->divert_port = cmd_line->divert_port;
if (config_file->interface != NULL)
config_file->interface = NULL;
If I'm understanding it correctly, this erases the interface in the
config_file if it exists, even if I'm not in inline mode. I'm not
sure what test should be there, but this doesn't seem right.
snort still sniffs, but it sniffs the "default interface" as determined
by libpcap, instead of what was on the command line.
Tested on both 220.127.116.11 and 18.104.22.168, as well as the 2.8.6.rc.
More information about the Snort-users