From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: linux-kernel@vger.kernel.org
Subject: TCP keepalive seems to send to only one port
Date: Sat, 23 Dec 2000 21:31:56 -0200 [thread overview]
Message-ID: <20001223213156.A1947@flower.cesarb> (raw)
I've been doing some experiments with the keepalive code in 2.4.0-test10 here
(I want to avoid the 2.2.x NAT I'm using (for which I don't have root) from
timing out my connections). To test it, I reduced both tcp_keepalive_time and
tcp_keepalive_intvl to 1. Using ethereal, I saw that the keepalives were sent
as expected, but only for one of the two idle TCP connections I had to a given
host (I was testing with two remote hosts, each with two idle TCP connections,
one in port 5500 and the other in port 5501). I only saw activity on 5500, yet
netstat told me both were still active.
This means that keepalive is useless for keeping alive more than one connection
to a given host.
--
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 reply other threads:[~2000-12-24 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 23:31 Cesar Eduardo Barros [this message]
2000-12-24 0:19 ` TCP keepalive seems to send to only one port David Schwartz
2000-12-24 0:38 ` Cesar Eduardo Barros
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=20001223213156.A1947@flower.cesarb \
--to=cesarb@nitnet.com.br \
--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.