From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] tcp resequence queues
Date: Mon, 9 Aug 2010 14:07:43 -0400 [thread overview]
Message-ID: <447d8bb72a04d66b4d65e139638544ce@ladd.quanstro.net> (raw)
as it turns out, limiting the number of packets
in the resequence queue does catch a few ill
behaved connections that are not sending
tinygrams. in this case, smtp:
Thu Aug 5 20:40:59: resequence queue > packets: 61 60; 81058 bytes
Thu Aug 5 20:40:59: reseq x.x.x.x.54772 -> 12.51.113.7.25
Sun Aug 8 16:57:54: resequence queue > packets: 46 45; 34000 bytes
Sun Aug 8 16:57:54: reseq y.y.y.y.1202 -> 12.51.113.7.25
(window scaling accounts for the different packet limits.)
- erik
reply other threads:[~2010-08-09 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=447d8bb72a04d66b4d65e139638544ce@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).