From: Robert Walker <robert_mt_walker@yahoo.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ problems :-(
Date: Sun, 04 Jan 2004 15:47:09 +0000 [thread overview]
Message-ID: <219601369.20040104154709@yahoo.co.uk> (raw)
In-Reply-To: <1045377672.20040104004813@yahoo.co.uk>
Hi Roy,
Thanks for getting back to me so promptly.
> Imq is very invasive componemt which requires to recompile almost everyhing
> this diver is very unstable and will crash for sure, sooner or later
> depending on load.
I have read about people having lots of problems with IMQ. So I just wanted to
try it and see how stable it is on my box. I gather it could actually
be problems with the Kernel and not the IMQ code??
> I sugest you to leave iptables alone and just modify imq.c source to catch
> what you need.
> ir you dont have too much trafic it may not crash for all day. ( if you will
> use it for download shaping)
I think that sounds even more messy :-)
I only wanted to ingress shape with IMQ to ensure that I don't drop UDP
or small TCP ACK packets for upload streams. I guess I will just give
up on the idea and using ingress policing... Its not so important anyway as my
DSL connection is very asymetric (2mbit D/L & 256kbit U/L) and upload
shaping is more important.
Even if IMQ is fixed in kernel 2.6 (is it??) I won't be able to use it until I
can update the driver for my conexant PCI ADSL modem (which works fine
just now under kernel 2.4.22)....
--
Best regards,
Robert
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-04 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 0:48 [LARTC] IMQ problems :-( Robert Walker
2004-01-04 2:12 ` Roy
2004-01-04 15:47 ` Robert Walker [this message]
2004-01-04 17:33 ` Roy
2004-01-06 21:43 ` Andy Furniss
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=219601369.20040104154709@yahoo.co.uk \
--to=robert_mt_walker@yahoo.co.uk \
--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