Yeah, this is how it looks like to me:rosc2112 wrote:Checked your userfile for the +p flag to allow connecting to the partyline? Checked your hostmasks for your handle in the userfile?
Using /ctcp or /dcc makes no difference. My client does support both and it works fine. Besides, as said I've tested with multiple clients on both linux & windows.rosc2112 wrote:The other suggestions I have would be:
Most clients use "/dcc chat nick" not /ctcp (although I don't know if that even makes a difference..Never thought to look at the src for my irc client for that.)
I'm thinking that's the problem cos my log shows (and yours does not show the DCC):
[00:32] CTCP DCC: CHAT chat 3454983022 33069 from rosc (~rosc@xanadu.rush2112.vh)
I don't use iptables with my firewall (its the standard firewall that comes with openSUSE and where I've opened the proper port). And since its the same problem from a windows box, I have the slightly feeling its on the Eggdrop side and not on the client side.rosc2112 wrote:The other idea that occurred to me, was to make sure you have the ip_conntrack_irc module loaded for your firewall in linux if you're using iptables.
Ahh I did not know that. I thought it was for allowing telnets :/Alchera wrote:Anyone with the nick -telnet gets recognised as the bot owner (nothing to do with telnet btw); no idea why this is added, maybe a hangover from the first eggdrop. I'd be removing it.
I don't have ident so I thought I needed the ~ in there?*!~rosc@ is best as *!rosc@
the initial contact sequence should be:
Code: Select all
msg bot hello
msg bot pass [password]
not really, I do did the msg hello / msq pass partDragnLord wrote:looking at the original post, this may be a simple matter to fix
it appears the bot was not correctly identified to
the initial contact sequence should be:the first post shows that flyingbaobab used ctcp, instead of msg, for the "hello" contactCode: Select all
msg bot hello msg bot pass [password]
from what I see, the bot is not responding because it does not recognize him