All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Correa <andre.correa@pobox.com>
To: linuximq@yahoogroups.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [linuximq] Re: [PATCH] pom-ng version of IMQ target (file is attached this time)
Date: Thu, 03 Jun 2004 12:24:21 -0300	[thread overview]
Message-ID: <40BF42A5.7070002@pobox.com> (raw)
In-Reply-To: <40BB2C43.90704@dsl.pipex.com>


Hi Andy, I cannot tell about netfilter, but I would like to see you 
patch anyway for testing and maybe include it on IMQ.

Some patchs sent by people are queued and I hope to review and publish 
then soon. Does your patch changes iptables too? Please send it on pvt.

To be honest I'm not willing to get in a "fight" for putting IMQ patch 
into p-o-m. I think it should be there the way IMQ is right now, but we 
better give it some time. I'm not sure too that dummy will satisfy all 
needs. I'm more to the good-old IMQ implementation.

tks

Andre

Andy Furniss wrote:
> Brad Fisher wrote:
> 
>>Patrick McHardy wrote:
>>
>>
>>
>>>Andre Correa already asked me about inclusion of the IMQ target. I would
>>>rather not include at this time it for two reasons:
>>>
>>>- IMQ still has stability problems
>>>- Jamal is working on a netfilter-independant replacement, I would like to
>>>see how it works out first. See
>>>http://marc.theaimsgroup.com/?t=108202471500003&r=1&w=2
>>>
>>>Regards
>>>Patrick
>>
>>
>>That's fine, I wasn't really asking for inclusion quite yet (though I would
>>like to see it happen someday :).  I just wanted to let people who may be
>>interested know that a pom-ng version of the patch existed.
>>
>>-Brad
> 
> 
> I am still not sure whether using Dummy will satisfy other IMQ users 
> though, the thread above just deals with my setup - using ingress IMQ. 
> There must be people on here using IMQ for egress/ multiple IMQs to 
> solve their own problems. I changed IMQ to hook before NAT for egress, 
> just to see if it worked, as someone on the LARTC list wanted to use 
> ESFQ for a large NATed LAN - it appears to be OK - but will a netfilter 
> independent replacement allow this sort of flexability?
> 
> Andy.
> 
> 
> 
> 
> ------------------------ Yahoo! Groups Sponsor --------------------~--> 
> Yahoo! Domains - Claim yours for only $14.70
> http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/dkFolB/TM
> --------------------------------------------------------------------~-> 
> 
>  
> Yahoo! Groups Links
> 
> <*> To visit your group on the web, go to:
>      http://groups.yahoo.com/group/linuximq/
> 
> <*> To unsubscribe from this group, send an email to:
>      linuximq-unsubscribe@yahoogroups.com
> 
> <*> Your use of Yahoo! Groups is subject to:
>      http://docs.yahoo.com/info/terms/
>  
> 
> 
> 

      parent reply	other threads:[~2004-06-03 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 21:59 [PATCH] pom-ng version of IMQ target (file is attached this time) Brad Fisher
2004-05-13  2:13 ` Patrick McHardy
2004-05-13 16:03   ` Brad Fisher
2004-05-31 12:59     ` [linuximq] " Andy Furniss
2004-06-01 23:17       ` Patrick McHardy
2004-06-02  0:18         ` Andy Furniss
2004-06-05 12:56           ` Patrick McHardy
2004-06-03 15:24       ` Andre Correa [this message]

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=40BF42A5.7070002@pobox.com \
    --to=andre.correa@pobox.com \
    --cc=linuximq@yahoogroups.com \
    --cc=netfilter-devel@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.