Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping services and users (2nd time)
Date: Thu, 09 Oct 2003 16:43:32 +0000	[thread overview]
Message-ID: <marc-lartc-106571808700673@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106562680806874@msgid-missing>

On Thursday 09 October 2003 09:02, Phill wrote:
> Oh, I am sorry, I knew that, it's jsut that I was playing with the numbers
> and I didn't check the sums.
>
> I know how to shape traffic coming from different users,
> ..protocol ip dst IP...etc, And I know how to shape traffic
> from each service. I just don't know how to glue them together.
>
> So what abou this? The point is that I want to be able to shape
> both the services and the IPs.
>
> root(128/128)
> +IP1(32/128)-----WWW(20/128)
>
> |            +---Default(10/128)
> |            +---P2P(1/64)
> |            +---...
>
> +IP2(32/64)------WWW(20/64)
>
> |            +---Default(10/64)
> |            +---P2P(1/64)
> |            +---...
>
> +IP3(32/64)--....
> ...
You need a set of filters attached to the root qdisc so the traffic for the 
different IP's are placed in the IPx class.  Then you need a second set of 
filters attached to the IPx classes and redirect all traffic to the different 
sub classes.

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/

      parent reply	other threads:[~2003-10-09 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 15:25 [LARTC] Shaping services and users (2nd time) Phill
2003-10-09  7:02 ` Phill
2003-10-09 16:43 ` 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-106571808700673@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox