All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Differentiating between http downloads and interactive
Date: Sun, 23 Oct 2005 03:31:51 +0000	[thread overview]
Message-ID: <435B0427.20605@riverviewtech.net> (raw)
In-Reply-To: <C2DA8EC72BEE0740BC5C7F5E04D4EB5160503A@holly.mtech.gg>

I would recommend looking at the connrate (http://www.netfilter.org/projects/patch-o-matic/pom-extra.html#pom-extra-connrate) Patch-O-Matic patch.  Your interactive sessions could be long lived and thus pass the connlimit and / or connbytes matches and thus be falsely classified.  Where as if you test for your interactive sessions by looking for an over all average low rate, burst delay burst delay etc, you should have a low average and thus be able to match based on rate to classify them higher.



Grant. . . .

Paul J. Smith wrote:
> Hi,
> 
> I’ve been wondering if anyone has thought of a way to differentiate 
> between an established http download and interactive http traffic?  I 
> would like to give interactive http traffic priority over someone 
> downloading large files. 
> 
> Has anyone any ideas how to detect packets that are part of a download 
> like this?
> 
> Thanks.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-10-23  3:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22  9:17 [LARTC] Differentiating between http downloads and interactive Paul J. Smith
2005-10-22  9:22 ` Andreas Unterkircher
2005-10-22 15:23 ` BUCHMULLER Norbert
2005-10-23  3:31 ` Grant Taylor [this message]
2005-11-02 16:22 ` [LARTC] Differentiating between http downloads and LinuXKiD

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=435B0427.20605@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.