From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Newbie: Installing Traffic Shaping
Date: Sun, 24 Nov 2002 20:16:50 +0000 [thread overview]
Message-ID: <marc-lartc-103816922228789@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103816576726739@msgid-missing>
On Sunday 24 November 2002 20:19, Christian Meier wrote:
> Hello List!
>
> My distribution is SuSE 7.3 Prof. I've successfully installed the
> iproute2 packet. If I enter some tc-rules the machine returns no
> errors, but the rules do not affect the bandwidth!
If you have no errors, you have all the support in the kernel you need.
> Does this mean that the kernel is not compiled with the necessary
> options? Where can I see, which options the kernel was compiled with
> (sorry, but I'm newbie)? I didn't change anything, it's a normal SuSE
> 7.3 distribution.
Maybe you can find a config file in the /boot directory.
> If I knew that the modules are working, I could go on trying to
> install some rules, or could anyone be so kind and post a simple rule
> that is slowing down my eth0 interface? I'd just like to see if the
> tc-command and the kernel is working...
I have some scripts on www.docm.org. You can also try to add a tvb qdisc as
root qdisc. This will limit all outgoing traffic.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-24 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-24 19:19 [LARTC] Newbie: Installing Traffic Shaping Christian Meier
2002-11-24 20:15 ` Togan Muftuoglu
2002-11-24 20:16 ` Stef Coene [this message]
2002-11-25 10:02 ` Christian Meier
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-103816922228789@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