All of lore.kernel.org
 help / color / mirror / Atom feed
From: IP v6 <inet6@mail.be>
To: netfilter-devel@lists.netfilter.org
Subject: Re: raw/NOTRACK + TARPIT = good idea?
Date: Tue, 2 Dec 2003 05:38:44 +0100 (CET)	[thread overview]
Message-ID: <14014030.1070339924765.JavaMail.Administrator@pumbaa> (raw)
In-Reply-To: <Pine.LNX.4.33.0311240903430.12476-100000@blackhole.kfki.hu>

I would like to do this also but I don't quite understand what you mean with "take care both directions for the tarpitted sessions".

I'm a bit confused there, could you explain? :)

Wkr, Robby

> ----------------------------------------
> From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
> Sent: Mon Nov 24 09:11:17 CET 2003
> To: Juan Carlos Castro y Castro <jcastro@vialink.com.br>
> Subject: Re: raw/NOTRACK + TARPIT = good idea?
> 
> 
> On Fri, 21 Nov 2003, Juan Carlos Castro y Castro wrote:
> 
> > I'm thinking about the TARPIT target, and that it's a shame it will
> > use resources if my box does conntrack. But if I previously pass them
> > through -t raw -j NOTRACK, can I have the best of both worlds, i.e., a
> > routing NAT box who is able to tarpit undesired packets itself?
> 
> Yes, but you have to take care both directions for the tarpitted
> sessions. That's the price using the NOTRACK target.
> 
> Best regards,
> Jozsef
> -
> E-mail  : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
> PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
> Address : KFKI Research Institute for Particle and Nuclear Physics
>           H-1525 Budapest 114, POB. 49, Hungary
> 
> 
> 

-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be

  reply	other threads:[~2003-12-02  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21 21:55 raw/NOTRACK + TARPIT = good idea? Juan Carlos Castro y Castro
2003-11-24  8:11 ` Jozsef Kadlecsik
2003-12-02  4:38   ` IP v6 [this message]
2003-12-02  9:13     ` Henrik Nordstrom

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=14014030.1070339924765.JavaMail.Administrator@pumbaa \
    --to=inet6@mail.be \
    --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.