I've recently encountered a problem while attempting to connect my bot to a network using the hybrid ircd.
The bot gets the following notices when trying to connect:
[13:39] Trying server irc.bulgaria.org:6667
[13:39] Connected to irc.bulgaria.org
[13:39] -NOTICE- *** Looking up your hostname...
[13:39] -NOTICE- *** Checking Ident
[13:39] -NOTICE- *** Found your hostname
[13:39] -NOTICE- *** Got Ident response
[13:39] -ERROR from server- Closing Link: botservice.net (Invalid username [])
[13:39] Disconnected from irc.bulgaria.org
I checked a few settings, had the bot log on to a different net, no problems there. We conducted a few more tests on that particular network and discovered that the ircd trys to connect to port 113 to get
an identd responce; if it can't get one, it declares the username to be blank, and hence invalid, even if valid info is being sent by the user in the traditional way. I tried replicating the test using mIRC, and disabling mIRC's identd, and the network let me on, so I suspect there are ways to overcome this.
Although this isn't so much an eggdrop matter, I was hoping somebody might have some suggestions on how I could tackle the problem, perhaps if you have experience using that particular ircd. I've not received
much help from the netadmins thus far, they don't believe identd is required. Any help would be appreciated.
The ircd version is hybrid-7beta5-bg(20020222_2). usa.irc.bg GHcCp TS3ow
the ircd is getting a valid identd response (ie, its getting a 'port, port : USERID : system : username' response - anything else and it would say no identd response). however, the valid identd response is not obeying standard rfc rules for usernames. I suggest you fix the identd daemon to either return proper rfc complient resonses, or turn it off completely
hybrid doesnt parse the username field that you send the server in the USER command if it gets a valid ident response. Since it is getting some kinda response that it deems as valid, anything you set to $username will be silently ignored by the ircd. The problem lies solely with his identd deamon (or possibly he really does have a messed up username on the box, though every adduser script in existance is made to prevent this)
Although I can't say for certain that there isn't a problem shell-side, however unlikely it may seem, I've bots running on dozens of networks and never encountered this problem on any of them. I'm afraid I must lay blame on the IRCd for the inability to connect.