Date: Fri, 30 Sep 2005 13:43:19 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Kevin Lamothe <kevin@animenfo.com> Cc: Doug Barton <dougb@FreeBSD.org>, current@freebsd.org Subject: Re: identd with FreeBSD 6.0? Message-ID: <20050930133845.D71864@fledge.watson.org> In-Reply-To: <433D0CEB.7000200@animenfo.com> References: <433D06D4.2010301@animenfo.com> <433D0924.6090703@FreeBSD.org> <433D0CEB.7000200@animenfo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050930133845.D71864>