From owner-freebsd-net@FreeBSD.ORG Wed Mar 26 11:05:38 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4623B37B404 for ; Wed, 26 Mar 2003 11:05:38 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6AE2B43F93 for ; Wed, 26 Mar 2003 11:05:37 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 96719 invoked from network); 26 Mar 2003 19:05:36 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 26 Mar 2003 19:05:36 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 26 Mar 2003 13:02:10 -0600 (CST) From: Mike Silbersack To: Fran Lawas-Grodek In-Reply-To: <20030326134823.A7029@jamaica.grc.nasa.gov> Message-ID: <20030326130005.A2075@odysseus.silby.com> References: <20030326134823.A7029@jamaica.grc.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-25.9 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-net@freebsd.org cc: Diechi.T.Tran@nasa.gov Subject: Re: persistent tcp connection? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 19:05:39 -0000 On Wed, 26 Mar 2003, Fran Lawas-Grodek wrote: > Does anyone know if there a sysctl parameter or kernel option that > would "clear out" any memory of a previous tcp connection? We've > played with the following sysctl parameters, and these are what > they are currently set -- What you're looking for are the route metrics, stored in the routing table. Use "netstat -nar" to see which routes have been cached. You should be able to delete the metrics associated with a cloned route by doing "route delete ipaddress". > net.inet.tcp.keepidle: 14400 > net.inet.tcp.keepintvl: 150 > net.inet.tcp.always_keepalive: 1 These would have nothing to do with what you're seeing. Keepalive only applies to established connections which are sitting idle. As you are disconnecting and reconnecting, only the route metrics are relevant. Mike "Silby" Silbersack