From: Alessandro Vesely <vesely@tana.it>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Best way to kill a live TCP connection?
Date: Wed, 12 Jan 2011 09:52:24 +0100 [thread overview]
Message-ID: <4D2D6BC8.80602@tana.it> (raw)
In-Reply-To: <alpine.LNX.2.01.1101112328480.25575@obet.zrqbmnf.qr>
On 11/Jan/11 23:31, Jan Engelhardt wrote:
> On Tuesday 2011-01-11 22:10, Grant Taylor wrote:
>> On 01/11/11 11:39, Pascal Hambourg wrote:
>>> However this sends only one RST to one side of the connection,
>>> leaving the connection half-open - until the other side sends a
>>> packet and gets a RST too. IMO it would be more elegant to send RSTs
>>> to boths sides of the connection.
>>
>> Wouldn't it be possible to send packet to user space and have something else
>> send the reset packets to both ends? I.e. use IPTables to match the packets
>> and have a user space daemon act on what IPTables matched.
>
> Well, you could augment ipt_REJECT to send two packets. It does not have
> to just send one.
Besides practical issues about augmenting modules, RST will never be
as clean as FIN. I mean, aborting will still be different from
cleanly shutting down. This particular difference, the minimal-cost
tarpit that results from sending RST to the local end only, may even
have its merits.
next prev parent reply other threads:[~2011-01-12 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:35 Best way to kill a live TCP connection? Alessandro Vesely
2011-01-11 14:41 ` Jan Engelhardt
2011-01-11 16:21 ` Alessandro Vesely
2011-01-11 17:39 ` Pascal Hambourg
2011-01-11 21:10 ` Grant Taylor
2011-01-11 22:31 ` Jan Engelhardt
2011-01-12 8:52 ` Alessandro Vesely [this message]
2011-01-18 17:50 ` Alessandro Vesely
2011-01-18 18:45 ` Gáspár Lajos
2011-01-19 13:32 ` Alessandro Vesely
2011-01-12 0:20 ` Pablo Neira Ayuso
2011-01-12 0:20 ` Pablo Neira Ayuso
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=4D2D6BC8.80602@tana.it \
--to=vesely@tana.it \
--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 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.