From: Francisco Pereira <fpereira@lojan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb and iptables marked packets question
Date: Tue, 28 Dec 2004 22:28:31 +0000 [thread overview]
Message-ID: <41D1DE0F.6050908@lojan.com> (raw)
In-Reply-To: <6.1.2.0.2.20041227132651.03c312b8@wheresmymailserver.com>
Hi.
Felipe Ceglia wrote:
> Hi folks,
>
> I have a strange situation. When I add branches to the tree, everything
> goes to the default class.
> The error might be obvious, but I cannot find it. I would really
> appreciate your help.
I think it's the expected behaviour.
>
> this works, nothing goes to "1:9999":
perhaps all the traffic you generate to test was marked by the iptables
rules and then classified by that.
btw in this order the rule for 192.168.200.0/24 never matches, because
the rule for 192.168.0.0/16 matches always first.
> #############################################################################
> /sbin/iptables -F -t mangle
> /sbin/tc qdisc del dev eth1 root > /dev/null 2>&1
> /sbin/tc qdisc add dev eth1 root handle 1: htb default 9999
That's whats the default parameter is for ^^^^
Traffic not classified goes to the default.
> /sbin/tc class add dev eth1 parent 1: classid 1:1 htb rate 100Mbit ceil 100Mbit
> /sbin/tc class add dev eth1 parent 1:1 classid 1:9999 htb rate 128kbit
> /sbin/tc class add dev eth1 parent 1:1 classid 1:4 htb rate 100Mbit
> /sbin/tc class add dev eth1 parent 1:4 classid 1:28 htb rate 510kbit
> #
> /sbin/iptables -A POSTROUTING -o eth1 -t mangle -d 192.168.0.0/16 -j MARK --set-mark 4
> /sbin/tc filter add dev eth1 protocol ip parent 1:0 prio 3 handle 4 fw flowid 1:4
> #
> /sbin/iptables -A POSTROUTING -o eth1 -t mangle -d 192.168.200.0/24 -j MARK --set-mark 28
> /sbin/tc filter add dev eth1 protocol ip parent 1:0 prio 3 handle 28 fw flowid 1:28
> #############################################################################
>
>
>
>
> when I add subclasses to "1:28", traffic goes to "1:34" and "1:35", but
> exceeding traffic goes to "1:9999" instead of being placed at "1:28":
> #############################################################################
>
> /sbin/tc qdisc add dev eth1 root handle 1: htb default 9999
That's whats the default parameter is for ^^^^
Regards,
Francisco.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-12-28 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 15:27 [LARTC] htb and iptables marked packets question Felipe Ceglia
2004-12-28 19:31 ` Stef Coene
2004-12-28 22:28 ` Francisco Pereira [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=41D1DE0F.6050908@lojan.com \
--to=fpereira@lojan.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.