Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!stanonik@nprdc.arpa
From: stanonik@nprdc.arpa (Ron Stanonik)
Newsgroups: net.unix-wizards
Subject: 4.2bsd/rlogin/source port choices
Message-ID: <11620@brl-tgr.ARPA>
Date: Tue, 16-Jul-85 14:18:35 EDT
Article-I.D.: brl-tgr.11620
Posted: Tue Jul 16 14:18:35 1985
Date-Received: Fri, 19-Jul-85 02:08:04 EDT
Sender: news@brl-tgr.ARPA
Lines: 17

4.2bsd/rlogin's use of reserved ports for user authentication
seemed the cause of a little problem here.  While a user was
rlogin'ed from a sun to a vax, the sun crashed.  After the sun
rebooted the user was unable to rlogin to the vax (connection
timed out?), apparently because the vax still thought the previous
connection from the sun was established, and the sun was trying
to reuse the same reserved port.  (rlogin chooses the source port
from the first available port starting at 1023, working downward.)
Of course killing the login on the vax marked the connection closed
and cleared up the problem, but there must be a better/nonmanual
way.  Have we've overlooked a 4.2bsd mod which allows rlogin or
the tcp's to sort this out?

Thanks,

Ron Stanonik
stanonik@nprdc