From: Nicolas Martin <nico.martin@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Problems to get TARPIT functionnality with iptables
Date: Thu, 14 Oct 2004 22:28:31 +0200 [thread overview]
Message-ID: <487eee5304101413284e973bbb@mail.gmail.com> (raw)
In-Reply-To: <20041014201012.GA4310@bender.817west.com>
No I did not use ./runme pending first.
If I launch it, same things happen for all the patches except if I
force it says :
Applying patch submitted/01_2.4.19.patch...
Failed to patch copy of /usr/src/linux
It's really strange ... I thought that maybe the fact that
/usr/src/linux was a link to the real source directory could screw
this up but if I specify /usr/src/kernel-source-2.6.8, it does not
work any better ....
On Thu, 14 Oct 2004 16:10:12 -0400, Jason Opperisano <opie@817west.com> wrote:
> On Thu, Oct 14, 2004 at 10:05:17PM +0200, Nicolas Martin wrote:
> > Hello,
> >
> > I'm using Debian GNU/Linux and I'd like to get iptables working with
> > the tarpit function.
> > I have my 2.6.8 kernel in /usr/src/linux.
> > I've downloaded patch-o-matic with cvs as told in the netfilter
> > modification tutorial. It created me /usr/src/linux/netfilter and
> > /usr/src/linux/netfilter/patch-o-matic (no
> > /usr/src/linux/netfilter/userspace as told in the tutorial).
> >
> > After that I launch ./runme ./extra/ipt_TARPIT.patch and if I apply the patch :
>
> did you "./runme pending" first?
>
> -j
>
> --
> Jason Opperisano <opie@817west.com>
>
>
next prev parent reply other threads:[~2004-10-14 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 20:05 Problems to get TARPIT functionnality with iptables Nicolas Martin
2004-10-14 20:10 ` Jason Opperisano
2004-10-14 20:28 ` Nicolas Martin [this message]
2004-10-14 21:00 ` Jason Opperisano
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=487eee5304101413284e973bbb@mail.gmail.com \
--to=nico.martin@gmail.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