From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Filter in HTB not working
Date: Fri, 20 Dec 2002 21:13:47 +0000 [thread overview]
Message-ID: <marc-lartc-104041889807035@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104029961502754@msgid-missing>
On Friday 20 December 2002 03:31, Miguel Figueiredo wrote:
> Em Qui, 2002-12-19 às 10:06, Nestor S A Melo escreveu:
>
> Nestor,
>
> First: If my english is poor, you can contact me direct by email in
> portuguese since I`m Brazilian too :)
>
> So, somebody correct me if I`m wrong ( Stef? ):
>
> 1 - I think you share more bandwidth than you have allocated.
That's no problem. Rate of class 1:10 and 1:20 = 26+220=246kbit and rate of
parent class is 256kbit.
> 2 - In sfq directive, you should write:
> #tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
His command will work too.
> 3 - You've marked packets with iptables -t mangle, but you're using u32
> instead fw.I'm not sure if you did the correct u32 configuration too.
>
> Probably you must use:
>
> #tc filter add dev eth0 parent 1: protocol ip prio 100 handle 6 fw classid
> 1:10
>
> The handle is the parameter that says to tc what mark you're using and
> fw is the parameter that says to tc that you're using a firewall mark.
And it's all in hex.
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/
prev parent reply other threads:[~2002-12-20 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 12:06 [LARTC] Filter in HTB not working Nestor S A Melo
2002-12-19 12:50 ` Corey Rogers
2002-12-20 2:31 ` Miguel Figueiredo
2002-12-20 21:13 ` 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-104041889807035@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.