From owner-freebsd-isp Sun Jan 14 10:25:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14855 for isp-outgoing; Sun, 14 Jan 1996 10:25:57 -0800 (PST) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA14850 Sun, 14 Jan 1996 10:25:53 -0800 (PST) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id MAA11463; Sun, 14 Jan 1996 12:25:46 -0600 Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 14 Jan 96 12:25 CST Message-Id: Subject: Re: A few other concerns from a FreeBSD ISP To: taob@io.org (Brian Tao) Date: Sun, 14 Jan 1996 12:25:45 -0600 (CST) From: "Karl Denninger, MCSNet" Cc: fenner@parc.xerox.com, msmith@atrad.adelaide.edu.au, freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: from "Brian Tao" at Jan 14, 96 12:38:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk > > On Wed, 10 Jan 1996, Bill Fenner wrote: > > > > I have always thought that this situation could only be attributed to > > one or the other end not waiting for 2*MSL before deleting connection > > information. In particular, if the source end cut its TIME_WAIT state > > short for some tcpcb, that port number could get reused while the > > server end was still in TIME_WAIT and thus completely ignoring all > > packets. > > Hmmmm, okay, whatever you say. ;-) > > > But I haven't yet gotten around to testing this theory; I can't say > > that I recall seeing this problem, so it may also be load-related, > > etc. > > I don't think it is. I've seen it happen to individual > workstations as well as to shell servers with 100+ people on it. The > really irritating thing is that it works *most* of the time, under > either extreme of load condition. :( > -- > Brian Tao (BT300, taob@io.org) > Systems Administrator, Internex Online Inc. > "Though this be madness, yet there is method in't" Run a few hundred "rshs" from a Freebsd machine to anything else. At least some small number will *HANG PERMANENTLY*. We have had to modify "rsh" to have a timeout parameter option (yeeeech!) and retry in the calling script to fix this here. That sucks; I would love to understand EXACTLY what is going on when this happens. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity Modem: [+1 312 248-0900] | T1 from $600 monthly; speeds to DS-3 available Voice: [+1 312 803-MCS1] | 21 Chicagoland POPs, ISDN, 28.8, much more Fax: [+1 312 248-9865] | Email to "info@mcs.net" WWW: http://www.mcs.net/ ISDN - Get it here TODAY! | Home of Chicago's only FULL Clarinet feed!