[Oisf-users] FreeBSD Suricata in-line
Chris Hunt
chrish.cct at gmail.com
Wed May 4 03:38:38 UTC 2011
Pablo,
First of all thank you for replying, I'm sorry for the length of this reply
but I wanted to be thorough...
I have tried starting Suricata a couple ways both ways will start the
engine...
1) I have used the built in rc.d script that is generated by configuring
/etc/rc.conf and adding suricata_enable="YES" and suricata_divertport="8000"
2) I have also tried running suricata from the command line as
"/usr/local/bin/suricata -c /usr/local/etc/suricata/suricata.yaml -d 8000"
I have the following log regarding ipfw:
cat /var/log/ipfw.today
00200 0 0 deny ip from any to 127.0.0.0/8
00300 0 0 deny ip from 127.0.0.0/8 to any
00400 0 0 deny ip from any to ::1
00500 0 0 deny ip from ::1 to any
65535 0 0 deny ip from any to any
I manually add the divert rule
ipfw 2000 add divert 8000 ip from any to any
Here is a print out of the rules:
00100 allow ip from any to any via lo0
00200 deny ip from any to 127.0.0.0/8
00300 deny ip from 127.0.0.0/8 to any
00400 deny ip from any to ::1
00500 deny ip from ::1 to any
00600 allow ipv6-icmp from :: to ff02::/16
00700 allow ipv6-icmp from fe80::/10 to fe80::/10
00800 allow ipv6-icmp from fe80::/10 to ff02::/16
00900 allow ipv6-icmp from any to any ip6 icmp6types 1
01000 allow ipv6-icmp from any to any ip6 icmp6types 2,135,136
02000 divert 8000 ip from any to any
65000 allow ip from any to any
65535 deny ip from any to any
I know that suricata is listening by running sockstat:
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
cct sshd 3944 3 tcp4 192.168.4.80:22 192.168.4.254:2872
cct sshd 3944 4 stream -> ??
root sshd 3940 3 tcp4 192.168.4.80:22 192.168.4.254:2872
root sshd 3940 5 stream -> ??
*root suricata 3937 7 div4 *:8000 *:**
root login 1182 3 dgram -> /var/run/logpriv
smmsp sendmail 1103 3 dgram -> /var/run/log
root sendmail 1099 3 dgram -> /var/run/logpriv
root sendmail 1099 4 tcp4 127.0.0.1:25 *:*
root sshd 1091 3 tcp6 *:22 *:*
root sshd 1091 4 tcp4 *:22 *:*
root ntpd 1046 3 dgram -> /var/run/logpriv
root ntpd 1046 20 udp4 *:123 *:*
root ntpd 1046 21 udp6 *:123 *:*
root ntpd 1046 22 udp6 fe80:4::1:123 *:*
root ntpd 1046 23 udp6 ::1:123 *:*
root ntpd 1046 24 udp4 127.0.0.1:123 *:*
root ntpd 1046 26 udp4 192.168.4.80:123 *:*
root ntpd 1046 27 udp4 192.168.4.81:123 *:*
root syslogd 795 4 dgram /var/run/log
root syslogd 795 5 dgram /var/run/logpriv
root syslogd 795 6 udp6 *:514 *:*
root syslogd 795 7 udp4 *:514 *:*
root devd 619 4 stream /var/run/devd.pipe
Do you know of any way I could verify each link in the chain? How do to
packet get from one interface to the other? Does suricata need any special
settings in the yaml file that I am missing?
Here is my yaml:
%YAML 1.1
---
# Number of packets allowed to be processed simultaneously. Default is a
# conservative 50. a higher number will make sure CPU's/CPU cores will be
# more easily kept busy, but will negatively impact caching.
#
# If you are using the CUDA pattern matcher (b2g_cuda below), different
rules
# apply. In that case try something like 4000 or more. This is because the
CUDA
# pattern matcher scans many packets in parallel.
#max-pending-packets: 50
# Set the order of alerts bassed on actions
# The default order is pass, drop, reject, alert
action-order:
- pass
- drop
- reject
- alert
# The default logging directory. Any log or output file will be
# placed here if its not specified with a full path name. This can be
# overridden with the -l command line parameter.
default-log-dir: /var/log/suricata
# Configure the type of alert (and other) logging you would like.
outputs:
# a line based alerts log similar to Snort's fast.log
- fast:
enabled: yes
filename: fast.log
# log output for use with Barnyard
- unified-log:
enabled: no
filename: unified.log
# Limit in MB.
#limit: 32
# alert output for use with Barnyard
- unified-alert:
enabled: no
filename: unified.alert
# Limit in MB.
#limit: 32
# alert output for use with Barnyard2
- unified2-alert:
enabled: yes
filename: unified2.alert
# Limit in MB.
#limit: 32
# a line based log of HTTP requests (no alerts)
- http-log:
enabled: yes
filename: http.log
# a full alerts log containing much information for signature writers
# or for investigating suspected false positives.
- alert-debug:
enabled: no
filename: alert-debug.log
# alert output to prelude (http://www.prelude-technologies.com/) only
# available if Suricata has been compiled with --enable-prelude
- alert-prelude:
enabled: no
profile: suricata
defrag:
max-frags: 65535
prealloc: yes
timeout: 60
# You can specify a threshold config file by setting "threshold-file"
# to the path of the threshold config file:
# threshold-file: /usr/local/etc/suricata/threshold.config
# The detection engine builds internal groups of signatures. The engine
# allow us to specify the profile to use for them, to manage memory on an
# efficient way keeping a good performance. For the profile keyword you
#\xc2\xa0can use the words "low", "medium", "high" or "custom". If you use
custom
# make sure to define the values at "- custom-values" as your convenience.
# Usually you would prefer medium/high/low
detect-engine:
- profile: medium
- custom-values:
toclient_src_groups: 2
toclient_dst_groups: 2
toclient_sp_groups: 2
toclient_dp_groups: 3
toserver_src_groups: 2
toserver_dst_groups: 4
toserver_sp_groups: 2
toserver_dp_groups: 25
# Suricata is multi-threaded. Here the threading can be influenced.
threading:
# On some cpu's/architectures it is beneficial to tie individual threads
# to specific CPU's/CPU cores. In this case all threads are tied to CPU0,
# and each extra CPU/core has one "detect" thread.
#
# On Intel Core2 and Nehalem CPU's enabling this will degrade performance.
#
set_cpu_affinity: no
#
# By default Suricata creates one "detect" thread per available CPU/CPU
core.
# This setting allows controlling this behaviour. A ratio setting of 2
will
# create 2 detect threads for each CPU/CPU core. So for a dual core CPU
this
# will result in 4 detect threads. If values below 1 are used, less
threads
# are created. So on a dual core CPU a setting of 0.5 results in 1 detect
# thread being created. Regardless of the setting at a minimum 1 detect
# thread will always be created.
#
detect_thread_ratio: 1.5
# Select the cuda device to use. The device_id identifies the device to be
used
# if one has multiple devices on the system. To find out device_id
associated
# with the card(s) on the system run "suricata --list-cuda-cards".
cuda:
device_id: 0
# Select the multi pattern algorithm you want to run for scan/search the
# in the engine. The supported algorithms are b2g, b3g and wumanber.
#
# There is also a CUDA pattern matcher (only available if Suricata was
# compiled with --enable-cuda: b2g_cuda. Make sure to update your
# max-pending-packets setting above as well if you use b2g_cuda.
mpm-algo: b2g
# The memory settings for hash size of these algorithms can vary from lowest
# (2048) - low (4096) - medium (8192) - high (16384) - highest (32768) - max
# (65536). The bloomfilter sizes of these algorithms can vary from low (512)
-
# medium (1024) - high (2048).
#
# For B2g/B3g algorithms, there is a support for two different scan/search
# algorithms. For B2g the scan algorithms are B2gScan & B2gScanBNDMq, and
# search algorithms are B2gSearch & B2gSearchBNDMq. For B3g scan algorithms
# are B3gScan & B3gScanBNDMq, and search algorithms are B3gSearch &
# B3gSearchBNDMq.
#
# For B2g the different scan/search algorithms and, hash and bloom
# filter size settings. For B3g the different scan/search algorithms and,
hash
# and bloom filter size settings. For wumanber the hash and bloom filter
size
# settings.
pattern-matcher:
- b2g:
scan_algo: B2gScanBNDMq
search_algo: B2gSearchBNDMq
hash_size: low
bf_size: medium
- b3g:
scan_algo: B3gScanBNDMq
search_algo: B3gSearchBNDMq
hash_size: low
bf_size: medium
- wumanber:
hash_size: low
bf_size: medium
# Flow settings:
# By default, the reserved memory (memcap) for flows is 32MB. This is the
limit
# for flow allocation inside the engine. You can change this value to allow
# more memory usage for flows.
# The hash_size determine the size of the hash used to identify flows inside
# the engine, and by default the value is 65536.
# At the startup, the engine can preallocate a number of flows, to get a
better
# performance. The number of flows preallocated is 10000 by default.
# emergency_recovery is the percentage of flows that the engine need to
# prune before unsetting the emergency state. The emergency state is
activated
# when the memcap limit is reached, allowing to create new flows, but
# prunning them with the emergency timeouts (they are defined below).
# If the memcap is reached, the engine will try to prune prune_flows
# with the default timeouts. If it doens't find a flow to prune, it will set
# the emergency bit and it will try again with more agressive timeouts.
# If that doesn't work, then it will try to kill the last time seen flows
# not in use.
flow:
memcap: 33554432
hash_size: 65536
prealloc: 10000
emergency_recovery: 30
prune_flows: 5
# Specific timeouts for flows. Here you can specify the timeouts that the
# active flows will wait to transit from the current state to another, on
each
# protocol. The value of "new" determine the seconds to wait after a
hanshake or
# stream startup before the engine free the data of that flow it doesn't
# change the state to established (usually if we don't receive more packets
# of that flow). The value of "established" is the amount of
# seconds that the engine will wait to free the flow if it spend that amount
# without receiving new packets or closing the connection. "closed" is the
# amount of time to wait after a flow is closed (usually zero).
#
# There's an emergency mode that will become active under attack
circumstances,
# making the engine to check flow status faster. This configuration
variables
# use the prefix "emergency_" and work similar as the normal ones.
# Some timeouts doesn't apply to all the protocols, like "closed", for udp
and
# icmp.
flow-timeouts:
default:
new: 30
established: 300
closed: 0
emergency_new: 10
emergency_established: 100
emergency_closed: 0
tcp:
new: 60
established: 3600
closed: 120
emergency_new: 10
emergency_established: 300
emergency_closed: 20
udp:
new: 30
established: 300
emergency_new: 10
emergency_established: 100
icmp:
new: 30
established: 300
emergency_new: 10
emergency_established: 100
# Stream engine settings. Here the TCP stream tracking and reaasembly
# engine is configured.
#
# stream:
# memcap: 33554432 # 32mb tcp session memcap
# max_sessions: 262144 # 256k concurrent sessions
# prealloc_sessions: 32768 # 32k sessions prealloc'd
# midstream: false # don't allow midstream session pickups
# async_oneside: false # don't enable async stream handling
# reassembly:
# memcap: 67108864 # 64mb tcp reassembly memcap
# depth: 1048576 # 1 MB reassembly depth
stream:
memcap: 33554432
reassembly:
memcap: 67108864
depth: 1048576
# Logging configuration. This is not about logging IDS alerts, but
# IDS output about what its doing, errors, etc.
logging:
# The default log level, can be overridden in an output section.
# Note that debug level logging will only be emitted if Suricata was
# compiled with the --enable-debug configure option.
#
# This value is overriden by the SC_LOG_LEVEL env var.
default-log-level: info
# The default output format. Optional parameter, should default to
# something reasonable if not provided. Can be overriden in an
# output section. You can leave this out to get the default.
#
# This value is overriden by the SC_LOG_FORMAT env var.
#default-log-format: "[%i] %t - (%f:%l) <%d> (%n) -- "
# A regex to filter output. Can be overridden in an output section.
# Defaults to empty (no filter).
#
# This value is overriden by the SC_LOG_OP_FILTER env var.
default-output-filter:
# Define your logging outputs. If none are defined, or they are all
# disabled you will get the default - console output.
outputs:
- console:
enabled: yes
- file:
enabled: no
filename: /var/log/suricata.log
- syslog:
enabled: no
facility: local5
format: "[%i] <%d> -- "
# PF_RING configuration. for use with native PF_RING support
# for more info see http://www.ntop.org/PF_RING.html
pfring:
# Default interface we will listen on.
interface: em0
# Default clusterid. PF_RING will load balance packets based on flow.
# All threads/processes that will participate need to have the same
# clusterid.
cluster-id: 99
# Default PF_RING cluster type. PF_RING can load balance per flow or per
hash.
# This is only supported in versions of PF_RING > 4.1.1.
cluster-type: cluster_round_robin
# For FreeBSD ipfw(8) divert(4) support.
# Please make sure you have ipfw_load="YES" and ipdivert_load="YES"
# in /etc/loader.conf or kldload'ing the appropriate kernel modules.
# Additionally, you need to have an ipfw rule for the engine to see
# the packets from ipfw. For Example:
#
# ipfw add 100 divert 8000 ip from any to any
#
# The 8000 above should be the same number you passed on the command
# line, i.e. -d 8000
#
ipfw:
# Reinject packets at the specified ipfw rule number. This config
# option is the ipfw rule number AT WHICH rule processing continues
# in the ipfw processing system after the engine has finished
# inspecting the packet for acceptance. If no rule number is specified,
# accepted packets are reinjected at the divert rule which they entered
# and IPFW rule processing continues. No check is done to verify
# this will rule makes sense so care must be taken to avoid loops in ipfw.
#
## The following example tells the engine to reinject packets
# back into the ipfw firewall AT rule number 5500:
#
# ipfw-reinjection-rule-number: 5500
# Set the default rule path here to search for the files.
# if not set, it will look at the current working dir
default-rule-path: /usr/local/etc/suricata/rules/
rule-files:
- attack-responses.rules
- backdoor.rules
- bad-traffic.rules
- chat.rules
- ddos.rules
- deleted.rules
- dns.rules
- dos.rules
- experimental.rules
- exploit.rules
- finger.rules
- ftp.rules
- icmp-info.rules
- icmp.rules
- imap.rules
- info.rules
- local.rules
- misc.rules
- multimedia.rules
- mysql.rules
- netbios.rules
- nntp.rules
- oracle.rules
- other-ids.rules
- p2p.rules
- policy.rules
- pop2.rules
- pop3.rules
- porn.rules
- rpc.rules
- rservices.rules
- scada.rules
- scan.rules
- shellcode.rules
- smtp.rules
- snmp.rules
- specific-threats.rules
- spyware-put.rules
- sql.rules
- telnet.rules
- tftp.rules
- virus.rules
- voip.rules
- web-activex.rules
- web-attacks.rules
- web-cgi.rules
- web-client.rules
- web-coldfusion.rules
- web-frontpage.rules
- web-iis.rules
- web-misc.rules
- web-php.rules
- x11.rules
- emerging-activex.rules
- emerging-attack_response.rules
- emerging-chat.rules
- emerging-current_events.rules
- emerging-deleted.rules
- emerging-dns.rules
- emerging-dos.rules
- emerging-exploit.rules
- emerging-ftp.rules
- emerging-games.rules
- emerging-icmp.rules
- emerging-icmp_info.rules
- emerging-imap.rules
- emerging-inappropriate.rules
- emerging-malware.rules
- emerging-misc.rules
- emerging-mobile_malware.rules
- emerging-netbios.rules
- emerging-p2p.rules
- emerging-policy.rules
- emerging-pop3.rules
classification-file: /usr/local/etc/suricata/rules/classification.config
reference-config-file: /usr/local/etc/suricata/rules/reference.config
# Holds variables that would be used by the engine.
vars:
# Holds the address group vars that would be passed in a Signature.
# These would be retrieved during the Signature address parsing stage.
address-groups:
HOME_NET: "[192.168.4.0/24]"
EXTERNAL_NET: any
HTTP_SERVERS: "$HOME_NET"
SMTP_SERVERS: "$HOME_NET"
SQL_SERVERS: "$HOME_NET"
DNS_SERVERS: "$HOME_NET"
TELNET_SERVERS: "$HOME_NET"
AIM_SERVERS: any
# Holds the port group vars that would be passed in a Signature.
# These would be retrieved during the Signature port parsing stage.
port-groups:
HTTP_PORTS: "80"
SHELLCODE_PORTS: "!80"
ORACLE_PORTS: 1521
SSH_PORTS: 22
# Host specific policies for defragmentation and TCP stream
# reassembly. The host OS lookup is done using a radix tree, just
# like a routing table so the most specific entry matches.
host-os-policy:
# Make the default policy windows.
windows: [0.0.0.0/0]
bsd: []
bsd_right: []
old_linux: []
linux: [192.168.4.0/24, "8762:2352:6241:7245:E000:0000:0000:0000"]
old_solaris: [192.168.4.0/24]
solaris: ["::1"]
hpux10: []
hpux11: []
irix: []
macos: []
vista: [192.168.4.0/24]
windows2k3: [192.168.4.0/24]
###########################################################################
# Configure libhtp.
#
#
# default-config: Used when no server-config matches
# personality: List of personalities used by default
#
# server-config: List of server configurations to use if address matches
# address: List of ip addresses or networks for this block
# personalitiy: List of personalities used by this block
#
# Currently Available Personalities:
# Minimal
# Generic
# IDS (default)
# IIS_4_0
# IIS_5_0
# IIS_5_1
# IIS_6_0
# IIS_7_0
# IIS_7_5
# Apache
# Apache_2_2
###########################################################################
libhtp:
default-config:
personality: IDS
server-config:
- apache:
address: [192.168.4.5/32, 127.0.0.0/8, "::1"]
personality: Apache_2_2
- iis7:
address:
- 192.168.4.254/32
- 192.168.1.9/32
personality: IIS_7_0
# rule profiling settings. Only effective if Suricata has been built with
the
# the --enable-profiling configure flag.
#
profiling:
rules:
# Profiling can be disabled here, but it will still have a
# performance impact if compiled in.
enabled: yes
# Sort options: ticks, avgticks, checks, matches
sort: avgticks
# Limit the number of items printed at exit.
limit: 100
On Tue, May 3, 2011 at 1:26 AM, Pablo <pablo.rincon.crespo at gmail.com> wrote:
> Hi Chris,
> how do you start suricata? did you find any errors about ipfw in the logs?
> If you set up a ipfw divert socket, then you need an app connected to
> it in order to forward packets. Usually, packets are not forwarded if
> there's no listening application delegated to allow/deny packets.
>
> 2011/5/3 Chris Hunt <chrish.cct at gmail.com>:
> > I have been stuck at the setup of Suricata in IPS mode for several days
> now,
> > any help would be immensely appreciated. My basic procedure is to
> utilize
> > the ports section of BSD to compile Suricata from source with the option
> for
> > IPS. I wanted to put together an easy to follow guide for a fellow noob
> > that included a Suricata engine dumping to unified2 with barnyard2
> dumping
> > this output to MySQL and BASE as a front-end... I'm stuck getting the
> IPS
> > to work...
> >
> > I'm using the loader.conf functionality to load the firewall module and
> the
> > divert module at boot, I've got 2 interfaces (em0 and em1) and I've added
> > the divert rule for port 8000 as rule 2000. When I try to ping or telnet
> > through I get nothing... Do I need to create a NAT rule to NAT traffic
> to
> > port 8000?
> >
> > I've also tried compiling the "options IPFIREWALL" and "options IPDIVERT"
> > just to be on the safe side before making this post.
> >
> >
> > Regard,
> >
> > Chris
> >
> > _______________________________________________
> > Oisf-users mailing list
> > Oisf-users at openinfosecfoundation.org
> > http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users
> >
> >
>
>
>
> --
>
> Best regards,
>
> --
> Pablo Rincón Crespo
> Security researcher and developer
> Open Information Security Foundation -
> http://www.openinfosecfoundation.org
> Emerging Threats Pro, INC - http://www.emergingthreatspro.com
> @PabloForThePPL
> ------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20110503/a4370b9f/attachment-0002.html>
More information about the Oisf-users
mailing list