Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alin Nastac <mrness@technosoft.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] IMQ & HTB problem
Date: Sat, 20 Apr 2002 18:31:09 +0000	[thread overview]
Message-ID: <marc-lartc-101932755431204@msgid-missing> (raw)

Hi everybody,

I have a strange problem. I recently found IMQ dummy device and I was 
anxious to test this on my router. I have the following configuration:

iptables -t mangle -A PREROUTING -i eth0 -m mark --mark 0 -d $MY_NET -j 
IMQ --todev 0
iptables -t mangle -A POSTROUTING -o eth0 -m mark --mark 0 -s $MY_NET -j 
IMQ --todev 1

insmod imq

tc qdisc add dev imq0 root handle 1: htb default fff
tc qdisc add dev imq1 root handle 1: htb default fff

tc class add dev imq0 parent 1:0 classid 1:1 htb rate 192Kbit
...

tc filter add dev imq0 parent 1:0 protocol ip prio 100 u32 match ip src...
bla bla bla

ip link set imq0 up; ip link set imq1 up

The problem is that when I run this script, those packets that are 
routed via imq* (0 for in and 1 for out) are slowed down to ridiculous 
speeds (1kbit or less for a 64kbit class for eg.)

I read about some bugs that lies in IMQ code but I also read about 
crashes related to this bugs and this is not my case.

Could anyone help me pls? I must finish this script till monday. Could 
it be usage of u32 filters? But still I see that packets are getting to 
the right classes.

Thanks,
Alin Nastac

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-04-20 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 18:31 Alin Nastac [this message]
2002-04-21  1:33 ` [LARTC] IMQ & HTB problem Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 12:29 [LARTC] IMQ+HTB problem hare ram
2003-04-15 13:23 ` Stef Coene
2003-04-15 13:57 ` hare ram
2003-04-15 16:51 ` Stef Coene

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-101932755431204@msgid-missing \
    --to=mrness@technosoft.ro \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox