From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ+HTB problem
Date: Tue, 15 Apr 2003 13:23:10 +0000 [thread overview]
Message-ID: <marc-lartc-105041308216816@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105040846112114@msgid-missing>
> i have patched the IMQ and htb to kernel, but when i do egress filtering,
> iam not able to see any traffic
>
> and excusted the following the commands
>
> modprobe imq numdevs=1
>
> tc qdisc add dev imq0 handle 1: root htb default 1
> tc class add dev imq0 parent 1: classid 1:1 htb rate 100kbit
>
> tc qdisc add dev imq0 parent 1:1 handle 10: htb default 1
> tc class add dev imq0 parent 10: classid 10:10 htb rate 100kbit
> tc qdisc add dev imq0 parent 10:10 handle 20: sfq
Never add a htb qdisc to a htb class. It will only add extra delays.
> iptables -t mangle -A POSTROUTING -p tcp --dport 80 -j IMQ
>
> ip link set imq0 up
>
>
> when i see the Iptables Out Put
>
> [root@bridge root]# iptables -xnvL -t mangle
> Chain PREROUTING (policy ACCEPT 122928 packets, 16888665 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain INPUT (policy ACCEPT 15068 packets, 1185569 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain FORWARD (policy ACCEPT 116790 packets, 16553990 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain OUTPUT (policy ACCEPT 4943 packets, 670996 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain POSTROUTING (policy ACCEPT 121733 packets, 17224986 bytes)
> pkts bytes target prot opt in out source
> destination
Euh. Where is your iptables command ????
> and also out put of tc
>
> [root@bridge root]# tc -s -d qdisc show
> qdisc sfq 20: dev imq0 limit 128p quantum 1500b flows 128/1024
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> qdisc htb 10: dev imq0 r2q 10 default 1 direct_packets_stat 0 ver 3.6
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> qdisc htb 1: dev imq0 r2q 10 default 1 direct_packets_stat 0 ver 3.6
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
So nothing is queued in the imq device. First, you have to get your iptables
command working. So packets are queued in the imq device.
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/
next prev parent reply other threads:[~2003-04-15 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 12:29 [LARTC] IMQ+HTB problem hare ram
2003-04-15 13:23 ` Stef Coene [this message]
2003-04-15 13:57 ` hare ram
2003-04-15 16:51 ` Stef Coene
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 18:31 [LARTC] IMQ & HTB problem Alin Nastac
2002-04-21 1:33 ` Patrick McHardy
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-105041308216816@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.