From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP keepalive seems to send to only one port
Date: Sat, 23 Dec 2000 22:38:14 -0200 [thread overview]
Message-ID: <20001223223814.A2281@flower.cesarb> (raw)
In-Reply-To: <20001223213156.A1947@flower.cesarb> <NCBBLIEPOCNJOAEKBEAKKEPOMJAA.davids@webmaster.com>
In-Reply-To: <NCBBLIEPOCNJOAEKBEAKKEPOMJAA.davids@webmaster.com>; from davids@webmaster.com on Sat, Dec 23, 2000 at 04:19:31PM -0800
On Sat, Dec 23, 2000 at 04:19:31PM -0800, David Schwartz wrote:
>
> > This means that keepalive is useless for keeping alive more than
> > one connection
> > to a given host.
>
> Actually, keepalive is useless for keeping connections alive anyway. It's
> very badly named. It's purpose is to detect dead peers, not keep peers
> alive.
Then what do you do when you are behind a NAT? And how do you expire entries in
ESTABLISHED state that could stay lingering forever without some sort of
keepalive? (The FINs might have been lost due to a conectivity transient, so
you can have another perfectly valid and alive connection with the same host,
and application-level timeouts are useless for some applications
(*cough*nc*cough*))
--
Cesar Eduardo Barros
cesarb@nitnet.com.br
cesarb@dcc.ufrj.br
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-24 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 23:31 TCP keepalive seems to send to only one port Cesar Eduardo Barros
2000-12-24 0:19 ` David Schwartz
2000-12-24 0:38 ` Cesar Eduardo Barros [this message]
2000-12-24 1:52 ` James Morris
2000-12-24 2:20 ` Cesar Eduardo Barros
2000-12-25 15:27 ` Igmar Palsenberg
2000-12-25 14:58 ` Cesar Eduardo Barros
2000-12-26 0:33 ` David Schwartz
2000-12-26 0:46 ` Cesar Eduardo Barros
2000-12-26 0:59 ` David Schwartz
2000-12-24 9:14 ` Andi Kleen
2000-12-24 14:12 ` Cesar Eduardo Barros
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 2:00 Bernd Eckenfels
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=20001223223814.A2281@flower.cesarb \
--to=cesarb@nitnet.com.br \
--cc=davids@webmaster.com \
--cc=linux-kernel@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.