From owner-freebsd-bugs Mon Feb 27 12:09:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA04367 for bugs-outgoing; Mon, 27 Feb 1995 12:09:58 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA04360 for ; Mon, 27 Feb 1995 12:09:42 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA02946; Mon, 27 Feb 95 13:02:52 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502272002.AA02946@cs.weber.edu> Subject: Re: your mail To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Mon, 27 Feb 95 13:02:52 MST Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <9502271947.AA15916@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Feb 27, 95 02:47:45 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Are you sure that you have the BSD box set up correctly in your > > local domain name services database? If the CMC telnetd can't do > > a getpeername successfully, it'll probably refuse the connection. > > `telnetd' doesn't have any choice abouty accepting or rejection > connections (if the one in question is anything at all like a standard > Berkeley one), because `inetd' has already accepted it by the time > `telnetd' ever executes. UnixWare also refuses connect when it can't RARP the address. Basically: o getpeername o gethostbyaddr (fails) o close I guess technically you could state "refuse the connection" means a non-acceptance. If so, then telnetd would be refusing to maintain the conection perpetrated by inetd rather than actually rejecting it. I believe, however, that the CMC networking stuff for the 3b2 doesn't have inetd, unless they made a newer version since the last time I saw the 3b2 code. I guess it's possible, though. I'm pretty sure that with the 3b2 being a dead machine and all that this is the case. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.