<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Inliniac</title>
	<atom:link href="http://www.inliniac.net/blog/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.inliniac.net/blog</link>
	<description>Everything inline.</description>
	<pubDate>Fri, 04 Jul 2008 13:09:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Multiple Snort_inline processes with Vuurmuur by Aki Heikkinen</title>
		<link>http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html#comment-11369</link>
		<dc:creator>Aki Heikkinen</dc:creator>
		<pubDate>Sun, 15 Jun 2008 18:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/2007/11/12/multiple-snort_inline-processes-with-vuurmuur.html#comment-11369</guid>
		<description>Has anyone tried dynamically reassign queques to different snort_inline instances on the fly based on traffic volume per destination port? Currently we just statically balance between different instances running on different processor cores but this setup leaves much to be desired.</description>
		<content:encoded><![CDATA[<p>Has anyone tried dynamically reassign queques to different snort_inline instances on the fly based on traffic volume per destination port? Currently we just statically balance between different instances running on different processor cores but this setup leaves much to be desired.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debian should update their Snort package by Thijs</title>
		<link>http://www.inliniac.net/blog/2007/06/16/debian-should-update-their-snort-package.html#comment-11243</link>
		<dc:creator>Thijs</dc:creator>
		<pubDate>Fri, 25 Apr 2008 10:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=87#comment-11243</guid>
		<description>Just for the record, some time to develop the rulesets made most of Debian's concerns go away, and Snort 2.7 will be in the next release (lenny / 5.0).</description>
		<content:encoded><![CDATA[<p>Just for the record, some time to develop the rulesets made most of Debian&#8217;s concerns go away, and Snort 2.7 will be in the next release (lenny / 5.0).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by Victor Julien</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11206</link>
		<dc:creator>Victor Julien</dc:creator>
		<pubDate>Fri, 11 Apr 2008 17:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11206</guid>
		<description>Yes, that is correct.</description>
		<content:encoded><![CDATA[<p>Yes, that is correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by chuzhenlin</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11204</link>
		<dc:creator>chuzhenlin</dc:creator>
		<pubDate>Fri, 11 Apr 2008 14:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11204</guid>
		<description>Hi Victor:

When we normalize the window for a stream, the stream becomes slow because the window size is smaller, but the connection remains. This case is different than the former normalizing the wscale.

Is my understanding right?</description>
		<content:encoded><![CDATA[<p>Hi Victor:</p>
<p>When we normalize the window for a stream, the stream becomes slow because the window size is smaller, but the connection remains. This case is different than the former normalizing the wscale.</p>
<p>Is my understanding right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by Victor Julien</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11196</link>
		<dc:creator>Victor Julien</dc:creator>
		<pubDate>Sun, 06 Apr 2008 19:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11196</guid>
		<description>The connection remains, but no data is sent over it anymore. In the post I linked to I described why that makes sense and why the window scaling normalization is broken and should not be used. The concept is just flawed.</description>
		<content:encoded><![CDATA[<p>The connection remains, but no data is sent over it anymore. In the post I linked to I described why that makes sense and why the window scaling normalization is broken and should not be used. The concept is just flawed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by chuzhenlin</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11194</link>
		<dc:creator>chuzhenlin</dc:creator>
		<pubDate>Sun, 06 Apr 2008 14:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11194</guid>
		<description>Lower the wscales of the client and server just make the stream slow, but the connection still remains. Right?
Does the window size tell another host how much space the sender has to receive the packets?
Sorry for my poor commen sense.</description>
		<content:encoded><![CDATA[<p>Lower the wscales of the client and server just make the stream slow, but the connection still remains. Right?<br />
Does the window size tell another host how much space the sender has to receive the packets?<br />
Sorry for my poor commen sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by Victor Julien</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11190</link>
		<dc:creator>Victor Julien</dc:creator>
		<pubDate>Sun, 06 Apr 2008 10:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11190</guid>
		<description>No, please see &lt;a href="http://www.inliniac.net/blog/2007/09/04/window-scaling-normalization-in-snort_inline-broken-by-design.html" rel="nofollow"&gt;this&lt;/a&gt; post. The wscale normalization principle is just flawed.</description>
		<content:encoded><![CDATA[<p>No, please see <a href="http://www.inliniac.net/blog/2007/09/04/window-scaling-normalization-in-snort_inline-broken-by-design.html" rel="nofollow">this</a> post. The wscale normalization principle is just flawed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by chuzhenlin</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11189</link>
		<dc:creator>chuzhenlin</dc:creator>
		<pubDate>Sun, 06 Apr 2008 03:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11189</guid>
		<description>Stream4 65 revision nornalizes the wscale of option in tcp header  while stream4 69 revision normalizes the window size of tcp header. What if we add an option in the configure file. When the cpu is busy, we just normalize the wscale of syn packets because only syn packets of three handshake have the wscale option work. Then we dont have to modify all packets in a steam.

Will it work?</description>
		<content:encoded><![CDATA[<p>Stream4 65 revision nornalizes the wscale of option in tcp header  while stream4 69 revision normalizes the window size of tcp header. What if we add an option in the configure file. When the cpu is busy, we just normalize the wscale of syn packets because only syn packets of three handshake have the wscale option work. Then we dont have to modify all packets in a steam.</p>
<p>Will it work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by Victor Julien</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11184</link>
		<dc:creator>Victor Julien</dc:creator>
		<pubDate>Sat, 05 Apr 2008 15:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11184</guid>
		<description>See &lt;a href="http://www.inliniac.net/blog/2007/11/17/new-snort_inline-tcp-window-normalization-code-in-svn.html" rel="nofollow"&gt;here&lt;/a&gt; and &lt;a href="http://snort-inline.svn.sourceforge.net/viewvc/snort-inline/trunk/src/preprocessors/spp_stream4.c?view=diff&#038;r1=69&#038;r2=65&#038;diff_format=h" rel="nofollow"&gt;here&lt;/a&gt; for the current implementation.

Wrt the speeds, it all depends on the hardware you use. It's hard to make general statements about that...
</description>
		<content:encoded><![CDATA[<p>See <a href="http://www.inliniac.net/blog/2007/11/17/new-snort_inline-tcp-window-normalization-code-in-svn.html" rel="nofollow">here</a> and <a href="http://snort-inline.svn.sourceforge.net/viewvc/snort-inline/trunk/src/preprocessors/spp_stream4.c?view=diff&#038;r1=69&#038;r2=65&#038;diff_format=h" rel="nofollow">here</a> for the current implementation.</p>
<p>Wrt the speeds, it all depends on the hardware you use. It&#8217;s hard to make general statements about that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TCP Window scaling in Snort_inline by chuzhenlin</title>
		<link>http://www.inliniac.net/blog/2007/06/16/tcp-window-scaling-in-snort_inline.html#comment-11182</link>
		<dc:creator>chuzhenlin</dc:creator>
		<pubDate>Sat, 05 Apr 2008 07:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=85#comment-11182</guid>
		<description>What high speed links will snort_inline perform badly when it deal with? 10M? 20M?</description>
		<content:encoded><![CDATA[<p>What high speed links will snort_inline perform badly when it deal with? 10M? 20M?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
