Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Simon Oosthoek <simon.oosthoek@ti-wmc.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wondershaper, host *exclusion*?
Date: Thu, 22 Apr 2004 13:42:36 +0000	[thread overview]
Message-ID: <4087CBCC.7020604@ti-wmc.nl> (raw)
In-Reply-To: <4087C283.2090504@virage.com>

Marc Reichman wrote:

> I will research in the howto, but I must say a lot of the terminology 
> goes over my head.
>
> To summarize, my steps are:
> 1. create a queue with no bw limitations
> 2. create a filter for the 192.168.0.0/24 and point it at that queue.
>
> Correct?

yes, however, now I think about it some more, you probably have a 
similar problem as myself (see my other (double) posting). The problem 
is that you want to shape the traffic in 2 directions, but the ingress 
queue (interface _before_ routing) is less flexible to manage than the 
egress queue (interface _after_ routing).

On the egress side, it's quite easy to add queues and make filters to 
it, but I'm not so sure about the ingress side. It might be possible to 
simply bypass the ingress bandwidth limiting queue for a certain 
ip-range (so you then don't have to add another queue for that). But if 
you want (like I do) to apply different restrictions to certain remote 
addresses, than the default, I don't have answers for that (only 
questions ;-)

Cheers

Simon

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

  parent reply	other threads:[~2004-04-22 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 13:02 [LARTC] wondershaper, host *exclusion*? Marc Reichman
2004-04-22 13:27 ` Simon Oosthoek
2004-04-22 13:33 ` Marc Reichman
2004-04-22 13:42 ` Simon Oosthoek [this message]
2004-04-22 13:53 ` Marc Reichman
2004-04-22 14:08 ` Simon Oosthoek
2004-04-22 14:15 ` Marc Reichman

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=4087CBCC.7020604@ti-wmc.nl \
    --to=simon.oosthoek@ti-wmc.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox