All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] service-based and ip-based shaping
Date: Wed, 03 Aug 2005 14:12:13 +0000	[thread overview]
Message-ID: <42F0D0BD.5000702@dsl.pipex.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAENEVIhFsNkiQ6vTBNVSNQcKAAAAQAAAA20j3JWLFr0Olyhp+B089UwEAAAAA@web-profile.net>

Mihai Vlad wrote:
> Thanks,
> 
> The only issue here is that for each service I need to create 200 child
> classes if I have 200 clients...
> 
> 
> Let me explain the problem better
> 
> I have the following connection from my ISP: (1024/1024) (rate/ceil)
> 
> 1) First, I want to divide the 1024 into smaller pieces based on priority:
> 	256/256 - P2P (I want to limit the P2P traffic as much as possible)
> 	256/1024 - HTTP
> 	256/1024 - FTP
> 	256/1024 - SSH, Games, etc
> (I do not say that this is the best approach but it does not matter - it is
> just an example)
> 
> 2) Second task: Suppose I have previously shaped the traffic the way I want,
> I need 200 classes for 200 clients in which to tell the rate and ceil for
> each of them
> 	16/512 - Client 1
> 	16/256 - Client 2, etc 
> 
> If I would have 200 clients and 10 types of services and childs to service
> classes, this means 2000 client classes...
> 
> I was thinking of a funny setup:
> 
> Route the traffic to 2 IMQ's
> 	-> First: traffic passes imq0 - and is shaped based on services
> 	-> Second: traffic from imq0 is routed to imq1 - where it is shaped
> based on IP of the client.
> 
> What do you think about this? 

I think you will need to use imq but I would just use 1 and do the 
second level shaping on the real interface(s).

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

      reply	other threads:[~2005-08-03 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 16:02 [LARTC] service-based and ip-based shaping Mihai Vlad
2005-08-03 14:12 ` Andy Furniss [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=42F0D0BD.5000702@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.