<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Load-Balancing on Inliniac</title>
    <link>https://inliniac.net/blog/tag/load-balancing/</link>
    <description>Recent content in Load-Balancing on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 18 Sep 2008 11:32:40 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/load-balancing/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Snort_inline load balancing</title>
      <link>https://inliniac.net/blog/2008/09/18/snort_inline-load-balancing/</link>
      <pubDate>Thu, 18 Sep 2008 11:32:40 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/09/18/snort_inline-load-balancing/</guid>
      <description>&lt;p&gt;Dave Remien of &lt;a href=&#34;http://www.nitrosecurity.com/&#34;&gt;NitroSecurity&lt;/a&gt; created a patch that &amp;ldquo;implements a relatively simple form of (IPV4) load balancing&amp;rdquo; between multiple Snort_inline processes using Nfqueue. Here is what it does:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;1. Load balancing. The bottom half of the source and dest addresses are added together, and mod&amp;rsquo;d with the number of &amp;ldquo;load-balancing&amp;rdquo; snorts you desire to run. This means that traffic stays with a particular snort, so that state is maintained.&lt;/p&gt;&#xA;&lt;p&gt;2. Because you can run many snorts (presumably on many CPUs), you can now take advantage of that super-hooty 16way box and those 10 gig NICs you just got your hands on&amp;hellip;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Multiple Snort_inline processes with Vuurmuur</title>
      <link>https://inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur/</link>
      <pubDate>Mon, 12 Nov 2007 21:29:58 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur/</guid>
      <description>&lt;p&gt;One of the cool things of the &lt;a href=&#34;http://snort-inline.sf.net/&#34;&gt;Snort_inline&lt;/a&gt; project is the support for NFQUEUE. NFQUEUE is the new queuing mechanism to push packets from the kernel to userspace so a userspace program can issue a verdict on it. What makes NFQUEUE cooler than it&amp;rsquo;s predecessor ip_queue is that it supports multiple queue&amp;rsquo;s. This means that there can be more than one Snort_inline process inspecting and judging traffic. The challenge is to make sure that each Snort_inline instance sees all traffic belonging to a certain connection so Snort_inline can do stateful inspection on it. Luckily, &lt;a href=&#34;http://www.vuurmuur.org/&#34;&gt;Vuurmuur&lt;/a&gt; makes it very easy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
