From: CaT <cat@zip.com.au>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage)
Date: Tue, 11 Jul 2006 09:23:24 +1000 [thread overview]
Message-ID: <20060710232324.GR2344@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0607050743470.30694@chaos.analogic.com>
On Wed, Jul 05, 2006 at 07:54:01AM -0400, linux-os (Dick Johnson) wrote:
> >> running since 8:42pm yesterday. It's 8:37am now. It hasn't progressed
> >> in any way. It hasn't quit. It hasn't timed out. It just sits there,
> >> hung. This leads me to consider the possibility of a DOS, either
> >> intentional or accidental (think about 2.6.17.x running on a mail server
> >> and someone mails/spams from a broken place).
>
> TCP/IP connections can continue forever. That's one of the reasons why
> Berkeley sockets has SO_KEEPALIVE for a socket option. In the absence
> of such an option, the physical connection can be broken for a week,
> reconnected, then the session can continue.
D'oh. I knew that. Sigh. It's one of the things I like about having a
static ip on a bad connection. :)
> In your case, you probably have a real error in which one end of the
> connection crashed. However, until the other end shuts down that
Well not so much crashed but became unreachable due to the wsize thing.
> socket, the connection is logically correct and should not be
> forcefully terminated.
It'll never terminate right now unless I hit ^c.
> A DOS is unlikely because with no data being transferred, little
Not all DOS' are transfer based. Just anything that uses up resources to
the point where a service is no longer able to be performed.
> non-swapable resources are used. You can control the maximum number
> of connections allowed from a host with your firewall software
> (like iptables).
After the fact really. In this case one can send mail to a box and make
it bounce to someplace behind a wsize broken network. Resources taken up
that wont return until someone spots what's wrong. You could make your
own wsize broken network, connect to someplace a few times and then move
on whilst their end hangs around, waiting for the connections to do
somthing.
In my test case I am wondering if there was/is a web process hanging
about doing nothing other then waiting for my end to do something.
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
next prev parent reply other threads:[~2006-07-10 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 1:59 2.6.17.1: fails to fully get webpage CaT
2006-06-29 2:46 ` David Miller
2006-06-29 3:09 ` CaT
2006-06-29 3:47 ` David Miller
2006-06-29 4:18 ` CaT
2006-06-29 14:50 ` Bill Davidsen
2006-06-29 22:50 ` CaT
2006-07-05 0:55 ` possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage) CaT
2006-07-05 11:54 ` linux-os (Dick Johnson)
2006-07-10 23:23 ` CaT [this message]
2006-07-13 12:11 ` possible dos / wsize affected frozen connection length Herbert Xu
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=20060710232324.GR2344@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).