Re: TCP keepalive seems to send to only one port

From: Cesar Eduardo Barros (cesarb@nitnet.com.br)
Date: Sat Dec 23 2000 - 19:38:14 EST

  • Next message: Fabrizio Gennari: "Trouble when linking aic7xxx.c"

    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/

    This archive was generated by hypermail 2b29 : Sat Dec 23 2000 - 20:08:16 EST