All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage)
Date: Wed, 5 Jul 2006 10:55:41 +1000	[thread overview]
Message-ID: <20060705005540.GL2344@zip.com.au> (raw)
In-Reply-To: <20060629225039.GO2149@zip.com.au>

On Fri, Jun 30, 2006 at 08:50:39AM +1000, CaT wrote:
> Another datapoint to this is that I've had this my netcat web test
> 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).

I'm just wondering if connections hanging around this long are normal.
The above has now been running for 6 days. netstat is still reporting an
established session. netcat has not timed out. It's all just sitting
there doing nothing.

-- 
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby

  reply	other threads:[~2006-07-05  0:54 UTC|newest]

Thread overview: 12+ 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             ` CaT [this message]
2006-07-05 11:54               ` possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage) linux-os (Dick Johnson)
2006-07-05 11:54                 ` linux-os (Dick Johnson)
2006-07-10 23:23                 ` CaT
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=20060705005540.GL2344@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.