From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
Nicola <nicola.padovano@gmail.com>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Tarpit target for the last stable (2.6.35.7): right version
Date: Sat, 09 Oct 2010 08:10:50 +0200 [thread overview]
Message-ID: <1286604650.2692.1.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.LNX.2.01.1010090609350.1542@obet.zrqbmnf.qr>
Le samedi 09 octobre 2010 à 06:21 +0200, Jan Engelhardt a écrit :
> I must say I am surprised.
>
> There already exists a maintained xt_TARPIT in Xtables-addons, and
> it seems like your patch is a duplicate effort of it.
>
> If you have any updates to xt_TARPIT, I would recommend the strategy
> that Luciano Coelho used when he wanted to have xt_condition in
> the main kernel:
>
> 1. take the maintained version from Xt-a
> 2. submit any updates to the Xt-a file, if feasible
> 3. once processed, submit that then for Linux kernel inclusion
> 4. apply further updates to the LK file, if needed
>
> That way it is way easier to know what specifically new features you
> have added to xt_TARPIT, if any.
>
Agreed, so much messages on netdev and netfilter-devel, only to rewrite
a TARPIT module :-(
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-10-09 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 19:01 [PATCH] Tarpit target for the last stable (2.6.35.7): right version Nicola
2010-10-08 19:10 ` Ben Hutchings
2010-10-09 4:21 ` Jan Engelhardt
2010-10-09 6:10 ` Eric Dumazet [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=1286604650.2692.1.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=jengelh@medozas.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nicola.padovano@gmail.com \
/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