<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Out-of-Order on Inliniac</title>
    <link>https://inliniac.net/blog/tag/out-of-order/</link>
    <description>Recent content in Out-of-Order on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 30 Jul 2007 21:22:56 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/out-of-order/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Snort_inline and out of order packets</title>
      <link>https://inliniac.net/blog/2007/07/30/snort_inline-and-out-of-order-packets/</link>
      <pubDate>Mon, 30 Jul 2007 21:22:56 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/07/30/snort_inline-and-out-of-order-packets/</guid>
      <description>&lt;p&gt;In Snort_inline&amp;rsquo;s stream4 modifications, one of the changes is that out of order TCP packets are treated differently from unmodified stream4. This can cause some new alerts to appear and some unexpected behaviour. So I&amp;rsquo;ll try to explain what happens here.&lt;/p&gt;&#xA;&lt;p&gt;First of all let me explain quickly what out of order packets are. To put it simple, TCP packets are send out by the source host in a specific order but can arrive in a different order at the destination. Packetloss, link saturation, routing issues are among many things that can cause this. A Snort_inline specific issue is that when Snort_inline can&amp;rsquo;t keep up with the packets it needs to process, it will drop packets which causes packetloss. These packets will then have to be resent by the sending host.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
