From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: [LARTC] IMQ slows computer to a crawl - SOLVED
Date: Fri, 20 Jan 2006 02:32:03 +0000 [thread overview]
Message-ID: <43D04BA3.A4C37053@iswest.com> (raw)
gypsy wrote:
>
> I am attempting to implement IMQ on a 2.4.31 version kernel with
> iptables 1.3.3.
>
> I am following the example at http://www.linuximq.net/usage.html. When
> I enter the line
> iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev1
>
> (eth1 is the external interface), the computer slows to a crawl. OK,
> the CPU is only an AMD K6 233 which is not the world's greatest CPU, but
> egress shaping is done at acceptable speed.
>
> Neither top nor free is any help. top says the system is using 35% and
> user about 1%, with load averages in the range of 0.2x, 0.2x and 0.1x
> and top itself is at the top of the list. free says 3388 free mem and
> 780 used swap.
>
> Even attaching to a non connected device (change eth1 to eth2 in the
> above iptables line) creates this condition!??
>
> Does anyone have any suggestions as to what might cause this huge
> slowdown? How do I troubleshoot this? I'll have to reimplement
> policing if I can't make IMQ work.
>
> Thanks for any assistance.
> --
> gypsy
The answer is that the wrong IMQ device was specified.
I loaded imq with:
modprobe imq numdevs=1
That makes the --todev 0 not 1. Moreover, I was in the wrong mangle
chain.
WRONG: iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev 1
RIGHT: iptables -t mangle -A PREROUTING -i eth1 -j IMQ --todev 0
So much for the documentation at http://www.linuximq.net/usage.html
<shrug>. Thanks to http://wiki.nix.hu/cgi-bin/twiki/view/IMQ/WebHome
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2006-01-20 2:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43D04BA3.A4C37053@iswest.com \
--to=gypsy@iswest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox