From owner-freebsd-current Tue Jun 1 13:14:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 26A1915802; Tue, 1 Jun 1999 13:14:19 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA20523; Tue, 1 Jun 1999 13:14:07 -0700 (PDT) Date: Tue, 1 Jun 1999 13:14:05 -0700 (PDT) From: Julian Elischer To: Matthew Hunt Cc: kip@lyris.com, Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <19990601130331.A21176@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is less and less of a problem because if you lose your link on PPP you are liable to get a differetn IP address on your redial. for network outages in the middle it works though.. but I'd rather have a keepalive of 10 x 4 hour pings before failure.. (or something as long..) It's really a per-connection decision on what makes sense julian On Tue, 1 Jun 1999, Matthew Hunt wrote: > On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > > > declared dead. I think it somewhat silly to say that this is consuming a > > lot of bandwidth. The average mail message (4k) is 4 packets, the average > > The other issue is that you don't necessarily want the TCP connection > to close just because you lose connectivity for a few hours. If we > send keepalives by default, might that not surprise users who don't > expect it? > > I'm thinking of long-lived connections like telnet and ssh; if you're > doing work over such a connection, it would be nice if the connection > endured an outage while you're away sleeping, like it does without > keepalives. > > -- > Matthew Hunt * UNIX is a lever for the > http://www.pobox.com/~mph/ * intellect. -J.R. Mashey > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message