From: Rio Martin <rio@martin.mu>
To: netfilter@lists.netfilter.org
Subject: Re: IMQ Replacement
Date: Tue, 20 Jan 2004 08:26:59 +0700 [thread overview]
Message-ID: <200401200826.59437.rio@martin.mu> (raw)
In-Reply-To: <400BDCB6.2000208@pobox.com>
As the network getting bigger, i think IMQ is the good solution to manage
traffic from all internal and outside network.
Could someone point me direction to get IMQ patch for 2.4.24 ?
Thank you.
Regards,
Rio Martin.
On Monday 19 January 2004 20:33, Andre Correa wrote:
> I've being using IMQ with 2.4.23 here with no probs too. I've already
> tried to discuss this topic here and in other lists but got no answer.
> Writting to the last maintainner didn't helped much...
> Some time ago there was a posting, maybe in LARTC, about a guy that
> started a parallell IMQ project, but I've never heard about hin anymore...
> I would like to contribute/coordinate in an effort to put IMQ back on
> its track. It is an important feature that is being left behind.
> Peter, maybe we should join, put a new site up with documentation
> updates, maintain 2.4.x patchs and later think what to do with 2.6. We
> may find other people interrested in coding and helping...
> Anybody else care about it?
> let us know...
> cheers
> Andre
>
> Peter Frischknecht wrote:
> > I have been using IMQ with great success for the last few months. The
> > particular network where this is used has 400+ nodes, and IMQ performs
> > flawlessly.
> >
> > As anyone who uses IMQ will tell you, the only alternatives are:
> > 1 - Install another router, just to perform NAT
> > 2 - Install 2 additional NICs in the Linux gateway with a Xover cable
> > between them
> >
> > Is there another piece of software that performs the job of IMQ?
> > It is great being able to shape traffic AND masquerade packets in one
> > box. How else can it be done?
> >
> > We shape traffic individually for each client. Generic traffic shapping
> > rules that regulate the entire pipe would not work for us.
> >
> > The fact that IMQ is unmaintained is nerve wrecking. It is difficult
> > enough to install the thing with the sources and documentation
> > available. It will only become more difficult as the kernel evolves and
> > we move to 2.6.x.
> >
> > I don't think I have the knowledge to mainatin the source code. But I
> > believe in the concept so much that I might just take up the code
> > maintenance. Hoepefully some other folks will join in. Maybe we can
> > convince enough folks to incorporate it into 2.6.x.
> >
> > Any help, comments or even flames will be appreciated. It is time for a
> > solution to this problem.
> >
> > Peter
next prev parent reply other threads:[~2004-01-20 1:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 15:56 linux-2.4.22, iptables-1.2.9, imq Josh Howlett
2003-11-13 12:45 ` Vigil
2004-01-17 15:15 ` IMQ Replacement Peter Frischknecht
2004-01-19 13:33 ` Andre Correa
2004-01-20 1:26 ` Rio Martin [this message]
2004-01-20 10:28 ` Remus
2004-01-20 22:04 ` Alex Satrapa
2004-01-20 11:05 ` Krystian
2004-01-21 14:52 ` Andre Correa
2004-01-26 12:16 ` Andre Correa
2004-01-26 14:42 ` Sven Schuster
2004-01-26 15:50 ` Andy Furniss
2004-01-27 0:17 ` Andy Furniss
2004-01-27 8:24 ` Andy Furniss
2004-01-27 8:13 ` Remus
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=200401200826.59437.rio@martin.mu \
--to=rio@martin.mu \
--cc=netfilter@lists.netfilter.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.