From owner-freebsd-current Tue Jun 1 13:17:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (unknown [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 4184015055; Tue, 1 Jun 1999 13:17:01 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA20273; Tue, 1 Jun 1999 14:16:56 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15554; Tue, 1 Jun 1999 14:16:55 -0600 Date: Tue, 1 Jun 1999 14:16:55 -0600 Message-Id: <199906012016.OAA15554@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Matthew Hunt , kip@lyris.com, Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: References: <19990601130331.A21176@wopr.caltech.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid 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. Not true. Only if you're using a dynamic IP address setup. Most business connections have a static connection, so they'll end up with the same IP address everytime. > 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..) I think PHK's one-week KEEPALIVE is acceptable to me. It lets me logon to freefall and have the link go bad overnight, yet still keep me on in the morning when I check it. Nate > > 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