TCP keepalive seems to send to only one port

From: Cesar Eduardo Barros (cesarb@nitnet.com.br)
Date: Sat Dec 23 2000 - 18:31:56 EST

Next message: Kai Germaschewski: "Re: test13-pre4 fails to compile"

Previous message: Matthias Schniedermeyer: "Re: About Celeron processor memory barrier problem"
Next in thread: David Schwartz: "RE: TCP keepalive seems to send to only one port"
Reply: David Schwartz: "RE: TCP keepalive seems to send to only one port"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 message: Kai Germaschewski: "Re: test13-pre4 fails to compile"
Previous message: Matthias Schniedermeyer: "Re: About Celeron processor memory barrier problem"
Next in thread: David Schwartz: "RE: TCP keepalive seems to send to only one port"
Reply: David Schwartz: "RE: TCP keepalive seems to send to only one port"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Dec 23 2000 - 19:11:02 EST