Project

General

Profile

Actions
Copy link

Bug #1262

closed

AF_PACKET support not getting built even with configure --enable-af-packet

Added by Raghunath Iyer almost 11 years ago. Updated almost 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Affected Versions:
Effort:
Difficulty:
Label:

Description

Even though configure has --enable-af-packet, suricata --build-info shows AF_PACKET not supported.
Building on a Debian 5.0.5 distribution with kernel 2.6.32.27 on a MIPs platform.
Config.log attached. Suricata --build-info below.

This is Suricata version 2.0.2 RELEASE
Features: NFQ PCAP_SET_BUFF LIBPCAP_VERSION_MAJOR=1 PF_RING HAVE_PACKET_FANOUT LIBNET1.1 HAVE_HTP_URI_NORMALIZE_HOOK HAVE_LUA
SIMD support: none
Atomic intrisics: 4 byte(s)
32-bits, Big-endian architecture
GCC version 4.3.2, C version 199901
L1 cache line size (CLS)=64
compiled with LibHTP v0.5.12, linked against LibHTP v0.5.12
Suricata Configuration:
AF_PACKET support: no
PF_RING support: yes
NFQueue support: yes
NFLOG support: yes
IPFW support: no
DAG enabled: no
Napatech enabled: no
Unix socket enabled: no
Detection enabled: yes

libnss support:                          no
  libnspr support:                         no
  libjansson support:                      no
  Prelude support:                         no
  PCRE jit:                                no
  LUA support:                             yes
  libluajit:                               no
  libgeoip:                                yes
  Non-bundled htp:                         no
  Old barnyard2 support:                   yes
  CUDA enabled:                            no
Suricatasc install:                      yes
Unit tests enabled:                      no
  Debug output enabled:                    no
  Debug validation enabled:                no
  Profiling enabled:                       no
  Profiling locks enabled:                 no
  Coccinelle / spatch:                     no

Generic build parameters:
Installation prefix (--prefix): /usr/local
Configuration directory (--sysconfdir): /usr/local/etc/suricata/
Log directory (--localstatedir) : /usr/local/var/log/suricata/

Host:                                    mips64-unknown-linux-gnu
  GCC binary:                              gcc
  GCC Protect enabled:                     no
  GCC march native enabled:                no
  GCC Profile enabled:                     no

Files

config.log (166 KB) config.log Raghunath Iyer, 08/14/2014 07:59 AM
Actions
Copy link
 #1

Updated by Victor Julien almost 11 years ago

Please use a up to date OS version.

Actions
Copy link
 #2

Updated by Raghunath Iyer almost 11 years ago

This is an embedded platform with a custom distribution derived out of Debian and kernel updates by processor vendor and board vendor. Updating to a latest OS is not feasible until support is available from both. If I can get hints as to where to look for failures - what did not get detected or what option should have been present in kernel, or where to look for in Suricata sources for appropriate defines that I must set in compiler flags, I can make some progress at this end.

Actions
Copy link
 #3

Updated by Victor Julien almost 11 years ago

  • Status changed from New to Rejected

Please don't open any new tickets with Debian 5 issues. There is no point is using an unsupported OS for security things.

Actions
Copy link
 #4

Updated by Victor Julien almost 11 years ago

Besides, we don't have to resources to support outdates OS versions. If you insist on using them, you should accept the burden of figuring things out yourself.

Actions
Copy link

Also available in: Atom PDF