From owner-freebsd-current Wed Jun 26 06:42:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA09197 for current-outgoing; Wed, 26 Jun 1996 06:42:42 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA09192 for ; Wed, 26 Jun 1996 06:42:37 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id JAA01142; Wed, 26 Jun 1996 09:38:32 -0400 (EDT) Date: Wed, 26 Jun 1996 09:39:27 -0400 (EDT) From: Brian Tao To: Lyndon Nerenberg VE7TCP cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: Has anyone noticed a problem with rshd in -current? In-Reply-To: <199606250412.VAA07543@multivac.orthanc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Jun 1996, Lyndon Nerenberg VE7TCP wrote: > > If so, this is a symptom of a long-standing bug (since 2.1-RELEASE at > the very least) related to reuse of addr/port pairs that I haven't > been able to track down. (And lots of other people have seen.) I've been seeing it since my first FreeBSD installation, just after 2.0 was released. I've personally only seen it happen with rlogin only, and Jordan reports a similar or identical problem with rsh. I've *never* seen it happen with any other inetd service. On top of that, rlogins from our Livingston PM-2e termservers to our FreeBSD servers have never failed either. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"