Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Dave <finalglide@gmail.com>, netfilter@vger.kernel.org
Subject: Re: POM Xtables???
Date: Mon, 30 Jun 2008 22:52:23 +0200	[thread overview]
Message-ID: <48694787.3080906@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0806302218500.30639@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Monday 2008-06-30 18:20, Patrick McHardy wrote:
>   
>>> 3) Still don't know where Xtables-addons fits in with Netfilter?  Why
>>> is Xtables not on the Netfilter site or even mentioned there at all?
>>> What does the core Netfilter team think of Xtables-addons?
>>>       
>> I have no opinion about this except that already mentioned by
>> Jan: useful patches in proper state should be upstream, all
>> others I don't care about.
>>     
>
> Well at least I want to give it some care. POM, and Xtables-addons
> exist because modules were rejected upstream.
> ...
> - the rest: dunno?
>   

Which rest? Is the list at the end of your mail complete?

>>> 6) Currently the extensions and patching systems seems to be a
>>> hodge-podge of items, all with different web sites, maintainers and
>>> writers, from a newbie perspective it's confusing, would be nice if it
>>> was wrapped up into something more straitforward. Hopefully this is
>>> what Xtables-addons is doing, BUT would be really nice if this all
>>> started officially at Netfilter.org.
>>>       
>> Short answer - don't do it, the module provided by the kernel
>> should be enough for 99.99% of all cases. If it isn't, convince
>> us to merge the patch, which usually isn't very hard.
>>
>> History has repeatedly shown that out of tree patches are buggy
>> and cause more problems than they solve, which is why there
>> is no interest from the netfilter team in maintaining external
>> patches.
>>     
>
> Hence I have taken up some and fixed them to be straight.
> Patrick, what's your judgment on the existing
> xt_{LOGMARK,TARPIT,TEE,condition,geoip,ipp2p} modules in xtables-addons?
>   

- LOGMARK - haven't seen it or can't remember
- TARPIT - fine if remaining issues are fixed
- TEE - same as TARPIT
- condition - undecided
- geoip - seems like a toy. Whats the use case?
- ipp2p - last version I've seen was a *horrible* mess, unless I'm
  confusing it with the other l7 classifier module out there.



  reply	other threads:[~2008-06-30 20:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 17:54 POM Xtables??? Dave
2008-06-27 18:58 ` Jan Engelhardt
2008-06-27 20:08   ` Dave
2008-06-27 21:16     ` Jan Engelhardt
2008-06-29  2:20   ` Grant Taylor
2008-06-30 16:04     ` Dave
2008-06-30 16:20       ` Patrick McHardy
2008-06-30 20:46         ` Jan Engelhardt
2008-06-30 20:52           ` Patrick McHardy [this message]
2008-07-01  9:43             ` Jozsef Kadlecsik
2008-07-01  9:46               ` Patrick McHardy
2008-07-01 11:38                 ` Jan Engelhardt
2008-07-01 11:43                   ` Patrick McHardy
2008-07-01 11:50                     ` Jan Engelhardt
2008-07-01 11:57                       ` Patrick McHardy
2008-07-01 14:05                     ` Grant Taylor
2008-07-01 14:10                       ` Patrick McHardy
2008-07-01 14:27                         ` Grant Taylor
2008-07-01 14:34                           ` Patrick McHardy
2008-07-01 14:30                       ` Jan Engelhardt
2008-07-23 20:19             ` Jan Engelhardt
2008-07-23 23:21               ` Patrick McHardy
2008-07-24  8:31                 ` James King
2008-07-24  9:21                   ` Pablo Neira Ayuso
2008-07-24  9:43                     ` Patrick McHardy
2008-08-15  8:17                       ` James King
2008-08-19 11:35                         ` Brent Clark
2008-08-15  8:48                     ` James King
2008-06-30 21:11         ` Jozsef Kadlecsik
2008-06-30 21:47           ` Jan Engelhardt
2008-07-01 10:00             ` Jozsef Kadlecsik
2008-07-01 11:19               ` Jan Engelhardt
2008-06-30 20:18       ` Jan Engelhardt

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=48694787.3080906@trash.net \
    --to=kaber@trash.net \
    --cc=finalglide@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter@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