Topic: irc and identd

[rk]

I have a little experince with IRC, but none with ident.  A couple of users on my network want to use IRC, and I don't have a problem with that.  The problem I am having is figuring out how to configure identd.  This may be a simple matter to someone with experience, but I am pulling my hair out over this.  What do I need to do in order to get identd.masq to work correctly?  I noted that the /etc/indetd.masq has a bunch of entries like:
...
192.168.0.5     user5           UNIX
192.168.0.6     user6           UNIX
192.168.0.7     user7           UNIX
192.168.0.8     user8           UNIX
...
Does that mean the users need to set their identd settings in mIRC to that?  What if I wanted to set up a commandline IRC client on the server itself, what do I need to do with identd there?

Is there a way to get the e-smith server to not masq identd requests, but just reply back with a generic one for all the users on my network.  Can anyone point me to a how-to on any of this?

rk

ps - I'm using SME Server 5.5, and yes, I have checked for the bug.

[Bill Talcott]

The way I understand it, SME will respond to ident requests from the outside with the stuff designated in the identd.masq file. In other words, if there's an ident request from an IRC server for 192.168.0.8, the SME will use "user8" and "UNIX" to respond.

In a wishlist thread, someone else said that you could enable ident relaying (SME passes the request to 192.168.0.8 instead of answering itself) by changing the "user#" entries to "*", and "UNIX" to "RELAY". I wrote up a HowTo at http://www.e-smith.org/bboard//read.php?f=3&i=18519&t=18519 describing how to make a custom template to change the file to * and RELAY. In all honesty, I don't know if that's the proper procedure for relaying. The HowTo does tell how to properly make the changes that the other person said worked...

[Charlie Brady]

Bill Talcott wrote:

> I wrote up a HowTo at
> http://www.e-smith.org/bboard//read.php?f=3&i=18519&t=18519
> describing how to make a custom template to change the file
> to * and RELAY. In all honesty, I don't know if that's the
> proper procedure for relaying. The HowTo does tell how to
> properly make the changes that the other person said worked...

Just a heads-up to you Bill, SME version 5.6 which has just gone into beta test replaces pidentd with oidentd. Oidentd has very similar features to pidentd, but uses different (although similar) configuration files. You might consider making a variant of your Howto, or deal with both variants in the one doc.

Regards

Charlie

[rk]

I did this, and it appears to have worked for the remote machines, thanks.  However I still have a question about the server itself.  If I want to run irc on that server, I shouldn't need to masq the identd call.  However I have tried leaving the in the RELAY as:
192.168.0.1     *               RELAY
and changed it to:
192.168.0.1    Useless         NOOS

but neither work.  When I try to connect to a server that does an identd call (irc.dal.net), I see the call in my log:
Sep 18 12:10:57 www identd[9975]: Returned: 1160 , 6667 : NO-USER

but it refuses my connection.  First off, where does it get 'NO-USER' from?  Next, I found this link: http://www.linuxpeople.cc/howto/identd2howto.htm but it appears old, as it shows changes to the inetd.conf.  I know our servers use xinetd.conf, which is different.  Has anyone gotten irc to work on the server itself?  Obviously I am interested in this, but it's not a high priority.

rk

[sabu]

same problem here rk

anyone know what could be wrong?

sabu