From owner-freebsd-questions Sat Feb 24 23:19:23 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA17491 for questions-outgoing; Sat, 24 Feb 1996 23:19:23 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA17486 for ; Sat, 24 Feb 1996 23:19:19 -0800 (PST) Received: from mordillo (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id IAA07994; Sun, 25 Feb 1996 08:19:00 +0100 (MET) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id SAA01022; Sat, 24 Feb 1996 18:33:16 +0100 From: Thomas Graichen Message-Id: <199602241733.SAA01022@mordillo> Subject: Re: rlogin hangs To: davidg@Root.COM Date: Sat, 24 Feb 1996 18:33:16 +0100 (MET) Cc: questions@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@FreeBSD.org Precedence: bulk >>i'm also nerved by this problem - it's absolutely reproducable (only 2 >>machines connected via ethernet) - it's 2.1.0 and everytime i rlogin - exit - >>rlogin it won't work - hangs a minute then again it works - and it's >>_absolutely_ reproducable - if anybody has a solution i may try it out (i >>haven't seen any fix in the commits of the last months) > > This sounds like the 2MSL ("TIME_WAIT") wait is somehow coming into play. I >believe that inetd sets the "SO_REUSEADDR" socket option for sockets it >manages, so this must be happening on the rlogin client side instead of the >server... > > Can you tell me: Does the problem occur 1) from freebsd to anything, >2) from anything to freebsd, or 3) from freebsd to freebsd ? > > The problem sounds like (1) and is probably because some sockets that were >used previously by someone else are now in a "TIME_WAIT" 2MSL state and this >is 60 seconds long. What to do about it, well, that's another thing. The local >port is supposed to be dynamically assigned to the next available port number >since the local port for rlogin isn't important...HOWEVER, rlogin insists on >having the local port be allocated out of the limited number of reserved ports >(it asks for port numbers between 512 and 1023), while telnet has no such >requirement (it asks for ports >=1024). The problem may very well be related >to this and, if so, may also explain why telnet appears to work okay in the >same environment. argh - now that i'll try it with different machines all works fine also between FreeBSD and FreeBSD (murphy !) - but it definitely happens between FreeBSD and FreeBSD for me - and yes - telnet works just fine in that cases t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery