All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] classify incominf traffic
Date: Fri, 07 Nov 2003 18:11:51 +0000	[thread overview]
Message-ID: <marc-lartc-106823020601554@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106812870721527@msgid-missing>

On Thursday 06 November 2003 15:06, Cord Buhlert wrote:
> Hi,
> is it possible to treat incoming traffic different according to eg port
> numbers or source addresses? is there a way to setuop some filters that
> for example prefer incoming mail to incoming http?
>
> i've seen that simply limiting bandwith fer certain kinds of traffic is
> possible - but that wastes a lot of bandwidth if one kind of traffic
> isn't present at a time, not allowing the other traffic use that unused
> bandwidth, doesn't it?
>
> Is there a way to optimize that?
You can try the imq device.  That's a virutal device and you can redirect any 
traffic to it.  Also incoming traffic.  Traffic can be shaped on this device 
with htb.  So you can use htb to shape incoming traffic, but it can create 
also extra overhead and increase the latency.

Stef

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

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

      reply	other threads:[~2003-11-07 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 14:06 [LARTC] classify incominf traffic Cord Buhlert
2003-11-07 18:11 ` Stef Coene [this message]

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-106823020601554@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.