

Code: Select all
Running in packet dump mode
--== Initializing Snort ==--
Initializing Output Plugins!
ERROR: Can't find pcap DAQ!
Fatal Error, Quitting..

Code: Select all
mainframe snort # ls -l /usr/lib64/daq/
total 60
-rwxr-xr-x 1 root root 959 Nov 4 20:07 daq_afpacket.la
-rwxr-xr-x 1 root root 18504 Nov 4 20:07 daq_afpacket.so
-rwxr-xr-x 1 root root 912 Nov 4 20:07 daq_dump.la
-rwxr-xr-x 1 root root 10272 Nov 4 20:07 daq_dump.so
-rwxr-xr-x 1 root root 912 Nov 4 20:07 daq_pcap.la
-rwxr-xr-x 1 root root 14424 Nov 4 20:07 daq_pcap.so
Code: Select all
mainframe snort # grep daq snort.conf
# daq
config daq: pcap
config daq_mode: passive
config daq_dir: /usr/lib64/daq/
I noticed the same problem. It seems the daq ebuild may have some issues. Emerging daq with afpacket, dump, and pcap was the only way I could get anything to show up for daq in /usr/lib64/DrWilken wrote:Weird,
I checked which USE flags I had set for daq and I had pcap but /usr/lib64/daq didn't exist.
I then added both pcap, dump and afpacket USE flags in /etc/portage/package.use and then recompiled daq and snort.
I've now verified that the modules existed in /usr/lib64/daq:
...

Code: Select all
...
IUSE="ipv6 afpacket dump +pcap"
DEPEND="pcap? ( >=net-libs/libpcap-1.0.0 )
dump? ( >=net-libs/libpcap-1.0.0 )"
RDEPEND="${DEPEND}"
src_configure() {
econf \
$(use_enable ipv6) \
$(use_enable pcap pcap-module) \
$(use_enable afpacket afpacket-module) \
$(use_enable dump dump-module) \
--disable-ipfw-module \
--disable-bundled-modules
}
...
I agree, it looks fine. I apologize for blaming the ebuild without looking at it. It is interesting that in order to build the daq pcap library we needed to build all the daq libraries. Perhaps it needs more testing.DrWilken wrote:Just had a look at the ebuild for net-libs/daq-0.3 (/usr/portage/net-libs/daq/daq-0.3.ebuild) and I'm not sure but doesn't this look wrong?Code: Select all
... IUSE="ipv6 afpacket dump +pcap" DEPEND="pcap? ( >=net-libs/libpcap-1.0.0 ) dump? ( >=net-libs/libpcap-1.0.0 )" RDEPEND="${DEPEND}" src_configure() { econf \ $(use_enable ipv6) \ $(use_enable pcap pcap-module) \ $(use_enable afpacket afpacket-module) \ $(use_enable dump dump-module) \ --disable-ipfw-module \ --disable-bundled-modules } ...

Awesome, thanks for the hard work testing it. I just built all the packages to get pcap to workwallace1819 wrote:I've taken a look at this. The problem does appear to be related to the actual DAQ package and not the ebuild. It appears that if you only build the pcap module nothing actually gets built. Both afpacket and dump appear to be working correctly. For now if you want to use the pcap DAQ module just make sure that either the afpacket or the dump USE flag is set as well. I'll submit a bug upstream for this.
Code: Select all
. / configure {options} - with-DAQ-libraries = / usr/lib64 - with-DAQ-includes = / usr / includeCode: Select all
--daq-dir /usr/lib64/daq/Code: Select all
snort -c /etc/snort/snort.conf --daq pcap --daq-dir /usr/lib64/daq/ --daq-mode passive -i eth0Code: Select all
--daq-dir /usr/lib64/daq/Code: Select all
snort -c /etc/snort/snort.conf --daq pcap --daq-dir /usr/lib64/daq/ --daq-mode passive -i eth0Code: Select all
ERROR: Can't start DAQ (-1) - socket: Operation not permitted!Code: Select all
perl -MCPAN -e 'install Switch'Code: Select all
emerge oinkmasterCode: Select all
emerge -qavtuDN oinkmasterCode: Select all
snort -c /etc/snort/snort.conf -dev -bCode: Select all
date.timezone = Europe/ZagrebCode: Select all
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICTCode: Select all
B8 1D D2 49 57 40 64 B3 BB D2 FE 79 8B 6F D0 DF ...IW@d....y.o..
AE 19 4F 96 40 46 41 F4 F4 48 BB E3 E0 C9 D5 FC ..O.@FA..H......
F2 BE 6B 51 CD 97 82 EC 01 0D 23 53 2E E9 55 2D ..kQ......#S..U-