<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Inliniac &#187; libdnet</title>
	<atom:link href="http://www.inliniac.net/blog/tag/libdnet/feed" rel="self" type="application/rss+xml" />
	<link>http://www.inliniac.net/blog</link>
	<description>Everything inline.</description>
	<lastBuildDate>Thu, 29 Jul 2010 19:38:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Snort_inline updated to 2.8.0.1 in SVN</title>
		<link>http://www.inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn.html</link>
		<comments>http://www.inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn.html#comments</comments>
		<pubDate>Wed, 09 Jan 2008 15:41:19 +0000</pubDate>
		<dc:creator>Victor Julien</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Snort]]></category>
		<category><![CDATA[Snort_inline]]></category>
		<category><![CDATA[libnet]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[inline]]></category>
		<category><![CDATA[libdnet]]></category>
		<category><![CDATA[nitro security]]></category>

		<guid isPermaLink="false">http://www.inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn.html</guid>
		<description><![CDATA[I&#8217;ve just committed an update to Snort_inline&#8217;s SVN. It brings it to the Snort 2.8.0.1 level. It supports both IPv4 and IPv6 on IPQ and NFQ. I have not been able to test IPFW on IPv6, so I don&#8217;t think that will work currently. This update removes the libdnet dependency and replaces it with libnet [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve just committed an update to Snort_inline&#8217;s SVN. It brings it to the Snort 2.8.0.1 level. It supports both IPv4 and IPv6 on IPQ and NFQ. I have not been able to test IPFW on IPv6, so I don&#8217;t think that will work currently.</p>
<p>This update removes the libdnet dependency and replaces it with libnet 1.1. To be able to send ICMPv6 unreachable packets you will need the libnet 1.1 patch I wrote a while ago. You can find that <a href="http://www.inliniac.net/blog/2007/10/16/libnet-11-ipv6-fixes-and-additions.html">here</a>. Get the latest Snort_inline by checking out SVN:</p>
<p>svn co https://snort-inline.svn.sourceforge.net/svnroot/snort-inline/trunk</p>
<p>Consider the code to be of beta quality for now, so be careful with it. Please report any problems with it!</p>
<p>Again, a big thank you to NitroSecurity for funding this work!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working on Snort_inline 2.8.0.1</title>
		<link>http://www.inliniac.net/blog/2007/12/22/working-on-snort_inline-2801.html</link>
		<comments>http://www.inliniac.net/blog/2007/12/22/working-on-snort_inline-2801.html#comments</comments>
		<pubDate>Sat, 22 Dec 2007 12:49:20 +0000</pubDate>
		<dc:creator>Victor Julien</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Snort]]></category>
		<category><![CDATA[Snort_inline]]></category>
		<category><![CDATA[inline]]></category>
		<category><![CDATA[ipv4]]></category>
		<category><![CDATA[libdnet]]></category>
		<category><![CDATA[nitro security]]></category>

		<guid isPermaLink="false">http://www.inliniac.net/blog/2007/12/22/working-on-snort_inline-2801.html</guid>
		<description><![CDATA[The last week I&#8217;ve been working on bringing Snort_inline to the Snort 2.8.0.1 level, including it&#8217;s IPv6 support. I&#8217;m almost ready to commit it to SVN, there are just some issues I need to fix in the inline specific code. The code will get rid of libdnet and use libnet 1.1 for sending reset/reject packets [...]]]></description>
			<content:encoded><![CDATA[<p>The last week I&#8217;ve been working on bringing Snort_inline to the Snort 2.8.0.1 level, including it&#8217;s IPv6 support. I&#8217;m almost ready to commit it to SVN, there are just some issues I need to fix in the inline specific code. The code will get rid of libdnet and use libnet 1.1 for sending reset/reject packets for both IPv4 and IPv6. After committing I will start working on getting the IPv6 features I wrote for NitroSecurity into this tree. This includes more matches, tunnel decoding (including for example the freenet6 tunnel, etc). So stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inliniac.net/blog/2007/12/22/working-on-snort_inline-2801.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Differences between Snort and Snort_inline</title>
		<link>http://www.inliniac.net/blog/2007/05/14/differences-between-snort-and-snort_inline.html</link>
		<comments>http://www.inliniac.net/blog/2007/05/14/differences-between-snort-and-snort_inline.html#comments</comments>
		<pubDate>Mon, 14 May 2007 17:05:41 +0000</pubDate>
		<dc:creator>Victor Julien</dc:creator>
				<category><![CDATA[Snort]]></category>
		<category><![CDATA[Snort_inline]]></category>
		<category><![CDATA[clamav]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[inline]]></category>
		<category><![CDATA[libdnet]]></category>
		<category><![CDATA[nitro security]]></category>
		<category><![CDATA[stickydrop]]></category>
		<category><![CDATA[stream4]]></category>

		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=74</guid>
		<description><![CDATA[Every few weeks the same question comes up: what is the difference between Snort in inline mode and Snort_inline. This makes sense, because the Snort_inline documentation and website fail to explain it. In this post I will try to highlight the main differences. In general I can say that we try to develop Snort_inline as [...]]]></description>
			<content:encoded><![CDATA[<p>Every few weeks the same question comes up: what is the difference between Snort in inline mode and Snort_inline. This makes sense, because the Snort_inline documentation and website fail to explain it. In this post I will try to highlight the main differences. In general I can say that we try to develop Snort_inline as a patchset on top of Snort. Snort_inline is focused at improving the <em>inline</em> part of Snort. Originally of course, Snort&#8217;s <em>inline</em> capabilities were developed in the Snort_inline project. With Snort 2.3.0RC1 they were merged into mainline Snort.</p>
<p><strong>Convenience</strong></p>
<p>We did a number of things to make Snort_inline a little more convenient for inline users.</p>
<ul>
<li><em>inline</em> is enabled by default in ./configure</li>
<li>we got rid of libnet 1.0.2a, switched to libdnet 1.1 instead</li>
<li>a snort_inline specific manual page was added, as well as some extra docs</li>
<li>a example configuration file for inline use is supplied</li>
</ul>
<p><strong>Added functionality</strong></p>
<ul>
<li>we support Linux&#8217; new queue&#8217;ing mechanism called nfqueue. This was contributed by <a href="http://www.nitrosecurity.com/">Nitro Security</a>. Nfqueue supports running multiple copies of Snort_inline to take advantage of SMP and reduce risk of denial of service when Snort_inline should crash.</li>
<li>stickydrop preprocessor enables you to add options to the rules to block an ipaddress for a configurable amount of time</li>
<li>bait-and-switch preprocessor (Linux only) allows you to redirect traffic from a host to a honeypot based on the rules</li>
<li>clamav preprocessor is included (you still need to pass &#8211;enable-clamav to ./configure)</li>
<li>reinject action for FreeBSD: reinjects an accepted packet into the ipfw list at a specific rule number</li>
</ul>
<p><strong>Improved for inline use</strong></p>
<ul>
<li>reject action can send RST packets to both source and destination</li>
<li>stream4 can drop attacks detected in the reassembled stream. It also enforces the TCP window. It implements a number of ideas from <a href="http://www.icir.org/vern/papers/TcpReassembly/index.html" target="_blank">Vern Paxson on TCP reassembly</a>, such as a limit on the number of out of order packets and bytes that are accepted in a stream.</li>
<li>some fixes for FreeBSD</li>
</ul>
<p>As the list shows, if you are interested in Snort running <em>inline</em>, using Snort_inline might be a better choice for you!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inliniac.net/blog/2007/05/14/differences-between-snort-and-snort_inline.html/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
