From: Flemming Frandsen <ff@nrvissing.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sharing a DSL between 40 subnets with htb
Date: Sun, 08 Jan 2006 18:08:31 +0000 [thread overview]
Message-ID: <43C1551F.90200@nrvissing.net> (raw)
In-Reply-To: <43BF7898.1070409@nrvissing.net>
gypsy wrote:
> I recommend that you look here. It may not be what you want, but it
> certainly is worth checking out even if it turns out not to be your
> answer: http://www.shurdix.org/
I'm not going to change the entire OS just to get the traffic shaping
set up and the traffic shaper in shuredix does shaping pr. ip (which is
not what I want) .
However, shurdix does use the imq to do ingres shaping (aka policing)
and that's a neat trick that had somehow escaped my attention, so thanks
for the hint.
Someone really ought to start a LARTC cookbook wiki to go with the LARTC
howto.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-08 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 8:15 [LARTC] Sharing a DSL between 40 subnets with htb Flemming Frandsen
2006-01-08 18:08 ` Flemming Frandsen [this message]
2006-01-08 21:16 ` Andy Furniss
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=43C1551F.90200@nrvissing.net \
--to=ff@nrvissing.net \
--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