All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Layer-7 Filter
Date: Sat, 31 May 2003 15:35:03 +0000	[thread overview]
Message-ID: <marc-lartc-105439541817754@msgid-missing> (raw)

Hi,

Layer 7 filtering was a topic on slashdot !
http://slashdot.org/article.pl?sid\x03/05/30/180224&mode=thread&tid\x106&tid\x185

After reading some slashdot comments, I downloaded the source.  And I have 
some comments on it.  I think these comments also belongs to the faq page of 
the layer 7 filtering page.

First of all, this is not a packet filter, it's a connection filter.  So once 
a connection is classified as http, all following packets beloning to that 
connection are classified as http.  I just wonder if it also works for ftp 
traffic with seperate command and data connections.

And only the first 8 packets of a connection are checked.  If no match is 
found, the packets are not classified.  This also reduce the overhead of 
checking each packet.  But from the patch :
+       if ( currentSockets[hash].hash = hash &&
+            (currentSockets[hash].num_pkts_so_far > 16 ||
+               currentSockets[hash].classified) )
And num_pkts_so_far is incremented each time we see a packet.  But we test for 
"num_pkts_so_far > 16" and "not num_pkts_so_far > 8" ??

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-05-31 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105439541817754@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.