From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] I thought it was right... please take a look...
Date: Wed, 19 Jun 2002 06:29:52 +0000 [thread overview]
Message-ID: <marc-lartc-102446829620768@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102445456012346@msgid-missing>
On Wednesday 19 June 2002 04:40, Jeremy Nelson wrote:
> Hi
>
> I dont think my script is quite right but I just cant see why. If you could
> have a look at it and let me know if anything is wrong or suggest any
> better ways of making this happen. I have a 256kbit link, I want to give
> half of that (approx 124kbit) to a web site we run and let it burst to the
> full link if the bandwidth is not used (classid 1:10). The other half of
> the link is divided into 4 parts that each have 31kbit. I want these
> classes to be able to burst to half the link (124kbit) if the bandwidth is
> not used (classid 1:20 -> 1:50).
>
> What is happening is that no traffic ever gets over 124kbit/sec even
> traffic that should be in 1:10. My script is below.
The scripts looks ok to me.
Are you sure the filters are working ? You can check with
tc -s -d class show dev eth0
and hopely the counters of bytes/packets are incrementing.
And what if you make 1:10 the default class and remove all the filters so
packets must end in 1:10?
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/
prev parent reply other threads:[~2002-06-19 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 2:40 [LARTC] I thought it was right... please take a look Jeremy Nelson
2002-06-19 6:29 ` 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-102446829620768@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 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.