egghelp/eggheads community

CTCP doesn't reply - followed all instructions

2006-10-12T09:29:24-04:00

Using nick!*@* as a hostmask is really not advisable, as anyone could use your nick (And no, nickserv won't help you here either).

And please, don't doublepost

Statistics: Posted by nml375 — Thu Oct 12, 2006 9:29 am

CTCP doesn't reply - followed all instructions

2006-10-12T03:17:43-04:00

May be a lame suggestion... But I think its a lot simpler.

in Telnet add .+host X!*@*
and then try /ctcp botnick chat

Regards,
Kash

Statistics: Posted by kash2k — Thu Oct 12, 2006 3:17 am

CTCP doesn't reply - followed all instructions

2006-09-25T12:19:06-04:00

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.

Any rfc-compliant server would not allow any user to hold the nick -telnet, as it does not start with a letter (psyBNC makes use of this aswell when communicating with the user). "-telnet"-hosts would'nt impose any major security issues by themselves, allowing anyone to telnet to it however would.

Most common practice of these would be if you wish to allow telnet-connections from additional hosts (such as localhost, 192.168.x.x that really would'nt make any sence on IRC), as upon any telnet connection, a identd-query is made, and the following hostmask is checked against the userlist: -telnet!@. If the first match has +p, the connection is allowed (assuming require-p is set to 1, otherwize check for +o). Also, if no identd-service responds to the query, "telnet" is used in it's place (mIRC and a few other clients have a habit of only answering identd-queries while connecting to a server).

wether or not to have !*ident/!?ident/!~ident or !ident, that depends on how you set strict-host.

I do find it abit odd that you don't even get a dcc chat-request from your bot when you use /ctcp chat, yet /dcc chat works just fine.

Statistics: Posted by nml375 — Mon Sep 25, 2006 12:19 pm

CTCP doesn't reply - followed all instructions

2006-09-25T08:54:53-04:00

I was thinking of that one 2, but i usualy run kvirc. Cause it didn't work i tried both xchat & konversation. Even on a standalone windows box with mirc he won't reply (from another internetconnection) and yes, changed my stuff via telnet in my user file when I tried that.

But I'll learn to live with it

Statistics: Posted by flyingbaobab — Mon Sep 25, 2006 8:54 am

CTCP doesn't reply - followed all instructions

2006-09-25T01:43:50-04:00

other possibility is that your irc is not allowing it
(bot sends, your client ignores)
such things happen when you are behind a router and your LAN address is different then your WAN address
too many variables and not enough information to accurately assess the situation

Statistics: Posted by DragnLord — Mon Sep 25, 2006 1:43 am

CTCP doesn't reply - followed all instructions

2006-09-24T22:40:11-04:00

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:
Code:
msg bot hellomsg bot pass [password]
the first post shows that flyingbaobab used ctcp, instead of msg, for the "hello" contact

from what I see, the bot is not responding because it does not recognize him

not really, I do did the msg hello / msq pass part
and since i didn't got an answer cq. i had no clue what happened; I telnetted to it to become its master
the bot just doesn't respond to msg or ctcp (while he receives the request as i can see when logged in with telnet).

I still have no clue whats wrong, but at least the bot runs fine and he does what he have to do. Management goes perfectlt via telnet.

Statistics: Posted by flyingbaobab — Sun Sep 24, 2006 10:40 pm

CTCP doesn't reply - followed all instructions

2006-09-24T18:23:37-04:00

- When I telnet from the console to my bot and then try to ctcp him on irc i get following message in telnet

Very true DragnLord, I misread that one line.

Statistics: Posted by Alchera — Sun Sep 24, 2006 6:23 pm

CTCP doesn't reply - followed all instructions

2006-09-24T12:24:27-04:00

looking at the original post, this may be a simple matter to fix
it appears the bot was not correctly identified to

[06:09] CTCP hello: from X (~X@X.users.X.com)
[06:13] CTCP CHAT: from X (~X@X.users.X.com)

the initial contact sequence should be:

Code:

msg bot hellomsg bot pass [password]

the first post shows that flyingbaobab used ctcp, instead of msg, for the "hello" contact

from what I see, the bot is not responding because it does not recognize him

Statistics: Posted by DragnLord — Sun Sep 24, 2006 12:24 pm

CTCP doesn't reply - followed all instructions

2006-09-23T19:18:57-04:00

IRC networks require a response via 113 (AUTH); some will even refuse connection if there is none (is also a common problem when eggdrop cannot connect).

You need to do some reading up on the Gibson Research Corporation site.

Statistics: Posted by Alchera — Sat Sep 23, 2006 7:18 pm

CTCP doesn't reply - followed all instructions

2006-09-22T20:55:36-04:00

I can dcc chat it, was just noting that I could not telnet to it without that entry.

I have identd disabled on purpose, cos I think it's useless for anything (so easily spoofed it serves no legitimate purpose in this day and age) except possibly to show that an IP is connected to a particular port..which should already be evident by being connected!

Statistics: Posted by rosc2112 — Fri Sep 22, 2006 8:55 pm

CTCP doesn't reply - followed all instructions

2006-09-22T19:15:07-04:00

You cannot simply DCC chat the bot?

Try *!rosc@ and you'll still be recognised.

If using *nix as your OS compile linux-identd to take care of your ident "problem".

Statistics: Posted by Alchera — Fri Sep 22, 2006 7:15 pm

CTCP doesn't reply - followed all instructions

2006-09-22T16:51:33-04:00

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.

Ahh I did not know that. I thought it was for allowing telnets :/

*!~rosc@ is best as *!rosc@

I don't have ident so I thought I needed the ~ in there?

Edit:
I just tested, removed the -telnet!*@* and tried telnetting to the bot (which only listens on localhost anyway) and it would not let me connect. I put the mask back in, and could connect? *confused*

Edit again:
Well ok, I have to use *!telnet@localhost.* as a mask apparently.

[bot(dcc)] [16:58] Telnet connection: localhost.epix.net/35066
[bot(dcc)] [16:58] Logged in: rosc (telnet@localhost.epix.net/35066)

Statistics: Posted by rosc2112 — Fri Sep 22, 2006 4:51 pm

CTCP doesn't reply - followed all instructions

2006-09-22T11:07:06-04:00

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.

*!~rosc@ is best as *!rosc@

Statistics: Posted by Alchera — Fri Sep 22, 2006 11:07 am

CTCP doesn't reply - followed all instructions

2006-09-22T11:04:09-04:00

Added that in my userfile, no difference

(my password was just some random text btw, so no need to worry )

Anyhow, thinking of just reinstalling my Eggdrop (prolly older version) and see what happens ...

Edit = typo

Statistics: Posted by flyingbaobab — Fri Sep 22, 2006 11:04 am

CTCP doesn't reply - followed all instructions

2006-09-22T10:42:03-04:00

Aha, you're only allowing telnet!

I have these hosts for example, in my userfile:

--HOSTS -telnet!*@*
--HOSTS *!~rosc@xanadu.rush2112.vh

PS:
(Might wanna change your password now, cos I think that can be decrypted

Statistics: Posted by rosc2112 — Fri Sep 22, 2006 10:42 am