Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!tcp-ip From: tcp-ip@ucbvax.ARPA Newsgroups: fa.tcp-ip Subject: 4.2bsd/rlogin/source port choices Message-ID: <9107@ucbvax.ARPA> Date: Tue, 16-Jul-85 15:31:41 EDT Article-I.D.: ucbvax.9107 Posted: Tue Jul 16 15:31:41 1985 Date-Received: Thu, 18-Jul-85 04:24:51 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 19 From: stanonik@nprdc.arpa (Ron Stanonik) 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