I am almost pulling my hair out on this one. I have searched through the forum, but could not find anything that seems relevant.
My bot, at times, allows me to /ctcp it and at other times (the majority) it does not. It also seems to affect whether or not I can add to my learn script (I can when I'm able to /ctcp the bot).
I'm determined to find out what is wrong as I would like to develop my knowledge of eggdrop further and also develop my bot into a useful member of my chatroom.
TIA
Last edited by FoxII on Fri Sep 28, 2007 5:21 pm, edited 1 time in total.
set ctcp-mode 0
Set here how the ctcp module should answer ctcps. There are 3 possible operating modes:
0 Normal behavior is used.
1 The bot ignores all ctcps, except for CHAT and PING requests by users with the +o flag.
2 Normal behavior is used, however the bot will not answer more than X ctcps in Y seconds (defined by 'set flood-ctcp').
set ctcp-mode 0
Set here how the ctcp module should answer ctcps. There are 3 possible operating modes:
0 Normal behavior is used.
1 The bot ignores all ctcps, except for CHAT and PING requests by users with the +o flag.
2 Normal behavior is used, however the bot will not answer more than X ctcps in Y seconds (defined by 'set flood-ctcp').
Irrelevant since FoxII's first post states that the DCC connection does work very rarely.
Since it does work from the bot's end, the inconsistency is most lilely that his IRC client is not sending the correct IP address to the bot for connection.
When an IRC client is behind a router it often times picks up the local network IP setting, this requires a manual input of the outgoing IP address.
Thanks. In the preferences I found a network section and they had a bind option there. I have put my ip in there. My computer will be automatically rebooting in a bit so I can check to see if it works when I return
Linux based computer, running eggdrop on my own comp.
I found another setting which was relating to DCC and it had the option of getting my ip from my server. I tried that, restarted and still no joy. I also tried using /dcc chat bot and was presented with;
Failed to bind to any address or port.
Sorry. My head is just swimming over this.
Linux based computer, running eggdrop on my own comp.
NB: I have a similar problem with a handful of bots .i.e. cannot DCC chat to them but am able to CTCP chat to them on a good day. As I have a botnet I simply relay via the hub. It's the (unnecessary) paranoid settings the shell admins have set.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
Thank you Alchera. I have gone through what you suggested, but I still cannot connect to the bot. I even stopped it and restarted it all with no luck.
I cannot dcc chat or ctcp to my bot. Surely if I have set myself up as the owner of the bot, then I should have no problems with it responding to me or am I wrong?
Okay. I didn't find out what was wrong. So I just deleted all the files that eggdrop created and run it again. Once it was up, I was able to register again and connect to my bot without problems.
Thank you all for your help though. I did learn quite a bit
Linux based computer, running eggdrop on my own comp.
for others information: if you do not save your configure file after registering 'hello' and your eggdrop dies or get killed. You are not its master that could be the problem here so do not forget to save userfile with '.save all' in partyline to make sure your infos are saved.