From owner-freebsd-current@FreeBSD.ORG Fri Sep 30 12:43:20 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DF2116A41F; Fri, 30 Sep 2005 12:43:20 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD8AD43D49; Fri, 30 Sep 2005 12:43:19 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 87DB146B08; Fri, 30 Sep 2005 08:43:19 -0400 (EDT) Date: Fri, 30 Sep 2005 13:43:19 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kevin Lamothe In-Reply-To: <433D0CEB.7000200@animenfo.com> Message-ID: <20050930133845.D71864@fledge.watson.org> References: <433D06D4.2010301@animenfo.com> <433D0924.6090703@FreeBSD.org> <433D0CEB.7000200@animenfo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Doug Barton , current@freebsd.org Subject: Re: identd with FreeBSD 6.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Sep 2005 12:43:20 -0000 On Fri, 30 Sep 2005, Kevin Lamothe wrote: > Yeah I know the inetd one works, but none of the standalone daemons seem > to work with FreeBSD6, I'm using the latest oidentd on my FreeBSD 5 > server. I used the same config on both of them. > > Theres no firewall on the machines its self, and hosts.allow and deny > are blank. The usual steps in debugging are: (1) Make sure that inetd has properly bound the TCP port. Telnet to the port and see if you can connect. (2) If you can connect, see if you can make an ident request -- you can read RFC 1413 to learn about the protocol, but the short of it is that you enter two port numbers, separated by a comma, reflecting server port and client port. (3) If you can connect but the connection closes immediately, check the system logs for an ident-related error from inetd or identd. The inetd man page talks some about error logging, and I assume whatever third party daemon you're using will likewise talk about it. If the third party daemon doesn't document how its logging and debugging works, I recommend against using it. You may find tools like ktrace(1) useful, inetd's -d mode, and so on. Robert N M Watson