egghelp.org community

[MIODude]

This is new in 1.6.20... as I never had this issue in 1.6.19

When attempting a dcc chat to the bot, it looks for a matching hostmask, which is the VHOST that the IRC servers have (you know..the vanity names).. but when someone does a /ctcp, it doesn't use the vhost, it uses the true hostmask.. this makes it difficult to admin for those that have dynamic IPs that change daily. It also thinks the person is coming from a telnet, as the ident has telnet in it.

Is this a bug in my settings that I haven't found yet? or.. something other than that? Is there a way to make it so its using the IRC Vhost?

[pseudo]

There are two ways to establish DCC chat with the bot: /dcc chat botnick or /ctcp botnick chat. These are different.

/dcc chat bot makes your IRC client open a socket listening for the bot to connect and tells it your IP address and port. If the bot recognizes your IRC hostmask, it will accept the chat and connect to the given address.

/ctcp bot chat, on the other hand, makes your IRC client connect to the bot's telnet port (the one you set in your config). Eggdrop uses a DCC CHAT request to send it to the bot and forgets about it. When the client connects to it, it's like an ordinary telnet connection, so it doesn't matter that your client obtained the address through IRC. This behaviour isn't new, it has always been like this.

If you are unable to set telnet hostmasks for your users, you can turn telnet protection off:

[MIODude]

Thanks for the info pseudo (was this in a doc somewhere? I couldn't find it).

So.. i must have had telnet protect setting different and it changed after upgraded to 1.6.20 then I guess.