From: Toshiro Viera <tviera@arnaldocastro.com.uy>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ problem
Date: Wed, 10 Sep 2003 16:02:23 +0000 [thread overview]
Message-ID: <marc-lartc-106322153231369@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104455258205522@msgid-missing>
> > I tried to make IMQ device to work... So I patched the kernel, patched
> > iptables, made all the stuff, boot to new kernel was ok, module imq was
> > there and it was ok to load it and 'ip link imq0 up' also worked and imq0
> > was present in ifconfig listing. Unitil imq0 was inactive everything was
> > clear and stable.
> >
> > BUT: Anytime I redirected any traffic to imq0 (with the iptables ... -j IMQ
> > comand), then the kernel crashed with "Kernal panic!" message....
> >
> > kernel 2.4.21 patched with linux-2.4.21-imq-1.diff
> > iptables 1.2.8 patched via patch-o-matic-20030107 with pom-20030625.diff
> >
> > Any tips, hints or whatever??
> I don't know if it's the case, but never give the imq device an ip address.
I've been having the same problems (I've also posted it to this list
with no success). I've noticed that (at least for me) the kernel panics
when I try to shape both incoming and outgoing traffic using the same
imq device, if I shape only incoming traffic, everything's OK.
If you find out something, please let me know.
--
Toshiro Viera <tviera@arnaldocastro.com.uy>
_______________________________________________
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-09-10 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 17:23 [LARTC] imq problem Robert Penz
2003-02-06 17:42 ` Robert Penz
2003-09-09 6:29 ` [LARTC] IMQ problem michal
2003-09-09 15:19 ` Stef Coene
2003-09-10 16:02 ` Toshiro Viera [this message]
2003-09-10 17:38 ` 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-106322153231369@msgid-missing \
--to=tviera@arnaldocastro.com.uy \
--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.