All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andraz Sraka <a@aufbix.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Optimization on Bandwidth Management-L7 filtering?
Date: Mon, 26 Jun 2006 17:14:26 +0000	[thread overview]
Message-ID: <1151342066.30132.9.camel@localhost> (raw)
In-Reply-To: <BAY7-F141FB087CD715A7D1D7B8B98E0@phx.gbl>


[-- Attachment #1.1.1: Type: text/plain, Size: 821 bytes --]

re

On Sun, 2006-06-11 at 04:32 +0000, lee weejin wrote:
> Since all the incoming packets was checked one by one-(it is time
> consuming and will cause the processing delay if it is handling more
> than 50 PC at a time), thus i am thinking that is there any way to
> have a random checking on incoming packets ? Scipt or tools? so that
> it wont check all the incoming packets one follow by another one.

Try marking only first/new packages/connections, that will be analyzed
by layer-7 filter in another chain and there do whole connecting mark
(-j CONNMARK --mark XX). Those mark packages/connections can be then
picked up by 'tc' for prioritizing traffic or netfilter for
rejecting/dropping/.. traffic.

regards,
 Andraz

-- 
BOFH excuse #62:

need to wrap system in aluminum foil to fix problem

[-- Attachment #1.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2242 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

  reply	other threads:[~2006-06-26 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11  4:32 [LARTC] Optimization on Bandwidth Management-L7 filtering? lee weejin
2006-06-26 17:14 ` Andraz Sraka [this message]
2006-07-06 16:35 ` lee weejin

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=1151342066.30132.9.camel@localhost \
    --to=a@aufbix.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.