All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Packets Going to default class
Date: Fri, 29 Apr 2005 19:08:57 +0000	[thread overview]
Message-ID: <42728649.9070402@dsl.pipex.com> (raw)
In-Reply-To: <002601c54bc0$848f6040$097d3fca@southern>

hareram wrote:
> Hi
> 
> I have tested with FC3 but iam not able get any good results on that.
> in the list some one recomend me that  > 3.17 HTB should work
> 
> I saw latest FC4 test2 has the HTB 3.17 with iptables 1.3.0
> 
> i have install in my P4 box, and trying to test
> 
> when iam uploading its working perfect, but when iam downloading its 
> going to default class
> can some one experinced the same problem
> 
> below is the my config
> 
> $TC qdisc add dev $IFACE root handle 1: htb default 15
> $TC class add dev $IFACE parent 1: classid 1:1 htb rate ${CEIL}kbit ceil 
> ${CEIL}kbit
> $TC class add dev $IFACE parent 1:1 classid 1:10 htb rate  512kbit ceil 
> 512kbit prio 0
> $TC class add dev $IFACE parent 1:1 classid 1:15 htb rate 256kbit ceil 
> 256kbit prio 0
> $TC qdisc add dev $IFACE parent 1:10 handle 10: sfq perturb 10
> $TC qdisc add dev $IFACE parent 1:15 handle 15: sfq perturb 10
> $TC filter add dev $IFACE parent 1:0 protocol ip prio 0 handle 10 fw 
> classid 1:10
> $TC filter add dev $IFACE parent 1:0 protocol ip prio 0 handle 15 fw 
> classid 1:15
> 
> $TC qdisc add dev $NFACE root handle 2: htb default 40
> $TC class add dev $NFACE parent 2: classid 2:1 htb rate ${CEIL}kbit ceil 
> ${CEIL}kbit
> $TC class add dev $NFACE parent 2:1 classid 2:20 htb rate 512kbit ceil 
> 512kbit prio 0
> $TC class add dev $NFACE parent 2:1 classid 2:40 htb rate 256kbit ceil 
> 256kbit prio 0
> $TC qdisc add dev $NFACE parent 2:20 handle 20: sfq perturb 10
> $TC qdisc add dev $NFACE parent 2:40 handle 40: sfq perturb 10
> $TC filter add dev $NFACE parent 2:0 protocol ip prio 0 handle 20 fw 
> classid 2:20
> $TC filter add dev $NFACE parent 2:0 protocol ip prio 0 handle 40 fw 
> classid 2:40
> 
> $I -t mangle -A FORWARD  -s a.b.c.d/24 -d 0/0 --j MARK --set-mark 10 #
> $I -t mangle -A FORWARD  -s 0/0 -d a.b.c.d/24 --j MARK --set-mark 20 #
> 
> the out put show like below for the download... here can observe that 
> all the traffic going to 2:40 instead of 2:20

<snip>

> could some one telling what is wrong, or is still problem with 3.17 too 
> or any problem with iptables
> 
> any suggestions will be great

I can't see why that doesn't work for you - A copy and paste of it works 
OK for me.

You don't really need the filters for default classes and it's best to 
delete the root qdisc before you add a new one.

Maybe you still had some filters around from an earlier test that 
messesd things up.

I am using the latest TC, iptables and 2.6.12-rc1.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2005-04-29 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  7:16 [LARTC] Packets Going to default class hareram
2005-04-29 19:08 ` Andy Furniss [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=42728649.9070402@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.