<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>IPS on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/ips/</link>
    <description>Recent content in IPS on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Tue, 04 Sep 2012 20:53:53 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/ips/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>New AF_PACKET IPS mode in Suricata</title>
      <link>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</link>
      <pubDate>Tue, 04 Sep 2012 20:53:53 +0000</pubDate>
      <guid>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</guid>
      <description>&lt;h4 id=&#34;a-new-suricata-ips-mode&#34;&gt;A new Suricata IPS mode&lt;/h4&gt;
&lt;p&gt;Suricata IPS capabilities are not new. It is possible to use Suricata with Netfilter or ipfw to build a state-of-the-art IPS. On Linux, this system has not the best throughput performance. Patrick McHardy’s work on &lt;a href=&#34;https://lwn.net/Articles/512442/&#34;&gt;netlink: memory mapped I/O&lt;/a&gt; should bring some real improvement but this is not yet available.&lt;/p&gt;
&lt;p&gt;I’ve thus decided to do an implementation of IPS based on AF_PACKET (read raw socket). The idea is based on one of the snort’s running mode. It peers two network interfaces and all packets received from one interface are sent to the other interface (if a signature with drop keyword does not fired on the packet). This requires to dedicate two network interfaces for Suricata but this provide a simple bridge system. As suricata is using latest AF_PACKET features (read load balancing), it was possible to build something really promising.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
