mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Simon Peter" <simon.peter@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysctl_tcp_keepalive_time
Date: Thu, 16 Aug 2007 13:23:19 +0200	[thread overview]
Message-ID: <9a8748490708160423g4ae218a3v7738f2c6399369e9@mail.gmail.com> (raw)
In-Reply-To: <20070816125526.9a895d09.simon.peter@gmx.de>

On 16/08/07, Simon Peter <simon.peter@gmx.de> wrote:
> Hi,
>
> is there any reason why sysctl_tcp_keepalive_time (reflected
> by /proc/sys/net/ipv4/tcp_keepalive_time) is set to 7200 seconds? Is
> this specified somewhere?
>
RFC 1122, section 4.2.3.6 - http://www.faqs.org/rfcs/rfc1122.html

"
         4.2.3.6  TCP Keep-Alives

            Implementors MAY include "keep-alives" in their TCP
            implementations, although this practice is not universally
            accepted.  If keep-alives are included, the application MUST
            be able to turn them on or off for each TCP connection, and
            they MUST default to off.

            Keep-alive packets MUST only be sent when no data or
            acknowledgement packets have been received for the
            connection within an interval.  This interval MUST be
            configurable and MUST default to no less than two hours.
"

This page may also be of interrest to you :
http://www.uic.rsu.ru/doc/inet/tcp_stevens/tcp_keep.htm

Also see "man 7 tcp"


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      reply	other threads:[~2007-08-16 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 10:55 sysctl_tcp_keepalive_time Simon Peter
2007-08-16 11:23 ` Jesper Juhl [this message]

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=9a8748490708160423g4ae218a3v7738f2c6399369e9@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.peter@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®