Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: IMQ Replacement
Date: Mon, 26 Jan 2004 15:50:47 +0000	[thread overview]
Message-ID: <40153757.2010108@dsl.pipex.com> (raw)
In-Reply-To: <20040126144206.GA11104@zion.homelinux.com>

Sven Schuster wrote:
> Hi Andre,
> 
> maybe interessting for you: Marcel Sebek recently started a thread
> on netdev about this topic. He has ported the IMQ device to 2.6
> and asked if this might be accepted. Davem contacted Patrick
> McHardy, the original author, who said that the IMQ device was
> buggy.
> This thread still continues, take a look at netdev ml archives for
> more information.

There is also discussion on the LARTC list at the moment - someone 
called roy has rewritten IMQ but still sees crashes. He thinks they are 
related to locally generated traffic, so IMQ for ingress should be OK.

Personally I have used IMQ for locally generated traffic (> a gig/day up 
with bittorrent running on a P200 gateway) without problems, but I only 
have 256kbit/s up and shutdown everything at night.

Andy.


> 
> HTH
> 
> Sven
> 
> On Mon, Jan 26, 2004 at 10:16:55AM -0200, Andre Correa told us:
> 
>>Hi guys, Andy F. pointed out that Alexander Clouter and other guys 
>>ported IMQ to 2.6. The URL to their port is:
>>
>>http://www.digriz.org.uk/jdg-qos-script/#qos-2.6
>>
>>I had no time or resources to test it so far...
>>
>>I've got no answer from the last IMQ maintainer so I'll start a list for 
>>us to discuss what we'll gonna do about it. I'll let you know later today.
>>
>>I'm sorry if this thread is disturbing somebody in this list. I'll just 
>>post 1 or 2 e-mails about it and we'll be out...
>>
>>Meanwhile, anybody interrested in joining us to work with IMQ please 
>>contact me privately.
>>
>>tks...
>>
>>Andre
> 
> 




  reply	other threads:[~2004-01-26 15:50 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
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 [this message]
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=40153757.2010108@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox