From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: [LARTC] IMQ stability
Date: Wed, 26 May 2004 23:56:01 +0000 [thread overview]
Message-ID: <40B52E91.4020103@snapgear.com> (raw)
In-Reply-To: <marc-lartc-105066408632475@msgid-missing>
Hi,
I've never actually even tried to use the IMQ device before,
but I've watched the emails go back and forth on various problems associated with it,
and what looks like some general instability.
How stable is it really ? Is it suitable for full-time use on a large number of
routers ?
Has anyone used it on ipsec0 + eth0 devices for shaping ?
and lastly, any difference between the IMQ implementation on 2.4, and that on 2.6 ?
Are they both still being developed ?
thanks,
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
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-05-26 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 11:28 [LARTC] IMQ Stability hare ram
2004-01-23 17:29 ` Michael S. Kazmier
2004-01-24 23:24 ` Roy
2004-01-24 23:38 ` mkazmier
2004-01-25 2:04 ` Alexander Clouter
2004-01-25 3:49 ` Roy
2004-01-25 8:56 ` Aron Brand
2004-01-26 10:36 ` Remus
2004-01-26 15:53 ` Michael S. Kazmier
2004-01-26 18:49 ` rubens
2004-01-27 0:39 ` Alexander Clouter
2004-01-28 8:25 ` Alexander Trotsai
2004-05-26 23:56 ` Damion de Soto [this message]
2004-05-28 22:21 ` [LARTC] IMQ stability Andre Correa
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=40B52E91.4020103@snapgear.com \
--to=damion@snapgear.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 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.