[lkml]   [2000]   [Dec]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: TCP keepalive seems to send to only one port
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

Cesar Eduardo Barros
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.055 / U:0.692 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site