<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sysctl on Inliniac</title>
    <link>https://inliniac.net/blog/tag/sysctl/</link>
    <description>Recent content in Sysctl on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 23 Jan 2008 15:27:29 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/sysctl/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Improving Snort_inline&#39;s NFQ performance</title>
      <link>https://inliniac.net/blog/2008/01/23/improving-snort_inlines-nfq-performance/</link>
      <pubDate>Wed, 23 Jan 2008 15:27:29 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/01/23/improving-snort_inlines-nfq-performance/</guid>
      <description>&lt;p&gt;When using Snort_inline with NFQ support, it&amp;rsquo;s likely that at some point you&amp;rsquo;ve seen messages like these on the console: &lt;em&gt;packet recv contents failure: No buffer space available&lt;/em&gt;. When the messages are appearing Snort_inline slows down significantly. I&amp;rsquo;ve been trying to find out why.&lt;/p&gt;&#xA;&lt;p&gt;There are a number of setting that influence NFQ performance. One of them is the NFQ queue maximum length. This is a value in packets. Snort_inline takes an argument to modify the buffer length: &amp;ndash;queue-maxlen 5000 (note: there are two dashes before queue-maxlen).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
