From owner-freebsd-bugs@FreeBSD.ORG Wed May 7 06:04:43 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20DFF37B401; Wed, 7 May 2003 06:04:43 -0700 (PDT) Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CF5443FBF; Wed, 7 May 2003 06:04:41 -0700 (PDT) (envelope-from lars.koeller@uni-bielefeld.de) Received: from rayadm.hrz.uni-bielefeld.de (rayadm.hrz.uni-bielefeld.de [129.70.202.15]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.10.12.16.25.p8) with ESMTP id <0HEI00AECPMEJP@mail.uni-bielefeld.de>; Wed, 7 May 2003 15:03:52 +0200 (MET DST) Received: from rayadm.hrz.uni-bielefeld.de (lkoeller@localhost) h47D3mC08065; Wed, 07 May 2003 15:03:50 +0200 (MEST) Date: Wed, 07 May 2003 15:03:48 +0200 From: Lars =?iso-8859-1?Q?K=F6ller?= X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ Sender: lars.koeller@uni-bielefeld.de To: Mark Cammidge Message-id: <200305071303.h47D3mC08065@rayadm.hrz.uni-bielefeld.de> MIME-version: 1.0 X-Mailer: exmh version 2.6.1 02/18/2003 with nmh-1.0.4 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT cc: freebsd-bugs@freebsd.org cc: freebsd-questions@freebsd.org cc: Lars =?iso-8859-1?Q?K=F6ller?= Subject: Re: HELP: TCP stack problem in 4.8-R with rsh connects (second channel) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 13:04:44 -0000 ---------- Hi, this mail results out of my news group posting concerning PR bin/51586 In reply to Mark Cammidge who wrote: > > > Sporadically the rshd can't open the second tcp connection back > > to the port the rsh-client has announced. > > Hi. I don't have a simple solution for you, but > some things you may want to try: > > - Check whether a FreeBSD-Solaris or Solaris-FreeBSD > combination works. That may not be useful to you, > but I think it will help other people to track > down the source of the problem. I've tested this, it doesen't change anything! > - Try update to FreeBSD-STABLE - the problem may have > been fixed already. > - Try update to FreeBSD-CURRENT - it's pretty stable > and may not suffer from the same problem. Hm, I don't like this, really for production machines. > - Use SSH instead of rsh. I suspect most people are > no longer using rsh, and ssh is meant to be pretty > much a drop in replacement. You can set it up to > avoid needing passwords. It will probably be > somewhat slower though. That's the point, there is no need to crypt, and performance would be too poor! > - Post to one of the mailing lists - the developers > who work on this soft of stuff are more likely to > read about it there than they are in the newsgroup. I have! Thanks and best regards Lars -- E-Mail: Lars.Koeller@Uni-Bielefeld.DE \ Lars Köller lkoeller@FreeBSD.org \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 ----------- FreeBSD, what else? ---- http://www.freebsd.org -------------