From: Marek Kierdelewicz <marek@piasta.pl>
To: Jorge Bastos <jorge.decimal@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: help on tc with kernels >= 2.6.27
Date: Fri, 2 Jan 2009 20:49:08 +0100 [thread overview]
Message-ID: <20090102204908.7ec18094@catlap> (raw)
In-Reply-To: <37b3b63f0901021046n40962c84mef64cab10153261e@mail.gmail.com>
>Hi,
Hi Jorge & List,
>I just joined the mailing list.
It's mailing list for netfilter not Linux QoS. I think your issue is
more suitable for lartc mailing list (is lartc list alive by the way?
anyone?).
>I'm using tc to do traffic shaping for about 6 years
>Since kernels >= 2.6.27 it just stoped working, and started shaping
>traffic to 1/2kb /sec.
>How could this be debug? I don't see other place to request for help
>other than this one, and I was adviced to ask for help here too.
Try attaching qdiscs (sfp/pfifo/bfifo) below each htb class. Please
send some more information (tc script, scenario, result of "tc -s -d
class sh dev XXX" command).
Regards,
Marek Kierdelewicz
next prev parent reply other threads:[~2009-01-02 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 18:46 help on tc with kernels >= 2.6.27 Jorge Bastos
2009-01-02 19:49 ` Marek Kierdelewicz [this message]
2009-01-02 20:44 ` bsilva
[not found] ` <00c301c96d17$750ea820$5f2bf860$@jorge@decimal.pt>
2009-01-02 20:53 ` Marek Kierdelewicz
2009-01-02 20:57 ` LARTC (was: Re: help on tc with kernels >= 2.6.27) /dev/rob0
2009-01-03 10:11 ` help on tc with kernels >= 2.6.27 Michele Petrazzo - Unipex srl
[not found] ` <001701c96d92$43c4e600$cb4eb200$@jorge@decimal.pt>
2009-01-03 11:47 ` Michele Petrazzo - Unipex srl
[not found] ` <002701c96d9b$53a5c0e0$faf142a0$@jorge@decimal.pt>
2009-01-03 12:29 ` Michele Petrazzo - Unipex srl
[not found] ` <003101c96ddb$9d991310$d8cb3930$@jorge@decimal.pt>
2009-01-05 11:39 ` Michele Petrazzo - Unipex srl
[not found] ` <01ee01c96f3b$eee74fa0$ccb5eee0$@jorge@decimal.pt>
2009-01-05 14:21 ` Michele Petrazzo - Unipex srl
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=20090102204908.7ec18094@catlap \
--to=marek@piasta.pl \
--cc=jorge.decimal@gmail.com \
--cc=netfilter@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.