From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RE: http bandwidth control
Date: Thu, 24 Jun 2004 20:40:14 +0000 [thread overview]
Message-ID: <40DB3C2E.5080306@wildgooses.com> (raw)
In-Reply-To: <1088048331.3736.18.camel@localhost.localdomain>
>Give me sometime to understand what u said !
>I went into the Howto and started reading all over.
>Discovered what imq devices are, and remembered what ESFQ was.
>Also went to the http://digriz.org.uk/jdg-qos-script/ ans started
>studying it.
>
>
You just have to plough through the Howto. Basically though these
things classify the *outgoing* data into a couple of queues, then they
release the packets at a programmable maximum rate. You can either do
the filtering in "tc", or just do it in iptables (more flexible).
The key thing is that its outgoing stuff only, so you either do it on a
machine that is routing (cos then the other interface will effectively
be your "out" one). Or you use IMQ on the incoming interface, which
simulates having something just in front of the normal interface (hence
you can attach outgoing filters to it).
The various qdiscs differ in implementation and number of params, but
that is the basic idea. HTB is the simplest because you just create a
couple of queues and set rates on them - everything else is done in
iptables.
>My kernel is 2.4.18-14 (RH8) and planing to upgrade to FC1 (not yet
>confident with FC2).
>
>How can i know if both IMQ and ESFQ is available in my actual kernel?
>
>
Hmm, well the script will error if you haven't. Redhat has a lot of
stuff compiled in, but if not then you are going to have a lot of
compiling ahead. You need a new kernel, new tc, and each will need
patches because neither of these things is mainstream yet.... It's not
hard if you have done this before (takes 20 mins), but if you haven't
then it's going to need you to set an afternoon aside to learn how to do
it (there are dozens of sites on how to compile the kernel)
Good luck
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-24 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 3:38 [LARTC] RE: http bandwidth control Guillermo Gomez
2004-06-24 11:07 ` Ed Wildgoose
2004-06-24 15:58 ` Guillermo Gomez
2004-06-24 20:40 ` Ed Wildgoose [this message]
2004-06-25 0:21 ` Guillermo Gomez
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=40DB3C2E.5080306@wildgooses.com \
--to=lists@wildgooses.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.