servvs wrote:I have used /dcc eggdrop and /ctcp eggdrop chat
Neither of them are working. I have the bot on the same machine that I am using for irc. How can I make ti connect???? plz help
sounds like the bot doesn't recognize you
did you message the bot to set you as owner, and did you set your password? (refer to eggdrop's documentation on how to do this)
My bot ever accepted my dcc chat, but in the 1.6.19 on linux 2.6.24-16 (debian) + TCL 8.5.2, he is accepting only telnet, and when I try a dcc chat, in the telnet I can see my nick trying open chat, but it not reply, until it time out... What may be? It isn't a dcc reject, I know that the bot reply a notice if I haven't access.
Alex-Musicman wrote:My bot ever accepted my dcc chat, but in the 1.6.19 on linux 2.6.24-16 (debian) + TCL 8.5.2, he is accepting only telnet, and when I try a dcc chat, in the telnet I can see my nick trying open chat, but it not reply, until it time out... What may be? It isn't a dcc reject, I know that the bot reply a notice if I haven't access.
If the bot can 'see' the dcc/ctcp chat requests, then the bot isn't the problem. The packet is arriving. It's the acknowledgement the bot sends back to the client requesting the dcc session that is blocked, by your client. I'm quite sure your bot has sent acknowledgement, since it has announced receiving the request. Check your firewall/router/NAT settings of your client, not the bot.
No problems with my client, because another bots, with .18 version is replying the chat.
My guess is it not found the client host.. like some cases in InspIRCD-ipv6 when the ipv4 starts with ::ffff. But not is this case.. This bot is in an UnrealIRCD (ipv4) and I only have vhost but any other bot answer DCC.. It is strange...
Also strange when I check version (./eggdrop -v) and returns 1.6.18+ssl. In others system like BSD return normaly .19 and the bot works good. I only not tested with TCL 8.5.2.