egghelp/eggheads community

DCC Chat is broken!

2004-08-25T12:20:52-04:00

connect-timeout is set to 15
protect-telnet is set to 1
ident-timeout is set to 5
any other suggestions?

I would suggest increasing the set ident-timeout variable, as this setting defines a time in seconds that the bot should wait before a dcc chat, telnet, or relay connection times out, in your case, after just 5 seconds. Would be prudent to increase this to around 30, when you take into account that there usually is at least 5 seconds of server lag.

I notice that your IP matches the set nat-ip range. I'm certain that your entire DCC problem can be solved by carefully reading the config file and text files included with every eggdrop in the ~/doc directory. While telnetting into the bot, it would probably be helpful if you would .console +dr and observe the error message (if any) that the bot spits out.

Statistics: Posted by YooHoo — Wed Aug 25, 2004 12:20 pm

DCC Chat is broken!

2004-08-23T17:59:24-04:00

connect-timeout is set to 15
protect-telnet is set to 1
ident-timeout is set to 5

hostmask is accurate

im running 2 bots one for internal testing and tinkering and one on a server with channels to look at. neither will accept dcc chats but they both acknowledge them in the logs (or party line if telnetted in).

on the bot for external irc servers i had set reserved portrange to a single port to accept dcc chats on and allowed it thru the firewall but for no reason it just stopped working. please read that i have had it successfully working not 3 weeks ago and it just stopped functioning. as far as i can now tell the set reserved portrange function no longer works. each time i attempt a dcc it seems to be a brand new port. no other processes according to a process search in webmin (nor using any variant of netstat) is using the set port.

this is what the bot returns in its logs (modified for privacy)...
[07:43] [07:42] DCC connection: CHAT (Nick!ident@192.168.0.116)
[07:43] [07:42] CTCP DCC: CHAT chat 3232235528 4747 from Nick (ident@192.168.0.116)
[07:46] [07:45] Password timeout on dcc chat: [Nick]ident@192.168.0.116

and on the client im using it returns:
Chat with Bot
Waiting for acknowledgement...

however after a bit of tweaking and tinkering a /ctcp Bot chat seemed to work without a problem from within the irc client.

ive tried both mirc and xchat with no success. ive also tried to recompile altho it didnt seem to help much.

on a final note i did take some time to run a search however none of the threads i saw were relevant to my problem including the one mentioned. this setup was properly functioning and had another person actually using it. it no longer functions and i dont understand why.

any other suggestions?

Statistics: Posted by Guest — Mon Aug 23, 2004 5:59 pm

DCC Chat is broken!

2004-08-23T12:22:47-04:00

• What do you have set for these conf file variables? :

Code:

set protect-telnet set ident-timeoutset connect-timeout

• Are you using any type of firewall?

• Is your hostmask listed accurately on the bot? (e.g. .channel #your-channel)

• Have a buddy join the partyline and set thier console +d. What error is the bot returning, if any?

• Last, but by no means least....
Have you simply tried /CTCP $botnick CHAT?

Shocker that it may be, but this topic has been covered hundreds and hundreds of times, most recently last Tuesday...

Click Here For Egghelp.Org's Best Kept Secret

Statistics: Posted by YooHoo — Mon Aug 23, 2004 12:22 pm

DCC Chat is broken!

2004-08-23T03:45:54-04:00

Hi,

Recently my eggy was able to accept DCC Chats fine, however lately my only course of connecting to the bot is via telnet. While telnet is ok to use i prefer dcc as it allows me to use the tab key on chan names (yeah im lazy) im currently modifying etc.

The only thing i can think of that may have bearing on the change is an update to my server. i recently ran apt-get upgrade on my debian box, however i didnt notice dcc being broken until well after. mind you i never needed dcc until that time.

the bot acknowledges the connection however it times out with no messages making it to the client.

now before you say its a nat issue the bot has been configured for a local irc server on my internal network where nat is not an issue and it still times out. its as if the bot drops the dcc request for no reason at all. in running a test i have 2 clients of exactly the same configuration on 2 different pcs able to dcc chat fine on the local network but neither can dcc chat the bot. however if the telnet port is open telnet works fine (albeit slower for some reason).

anyone else having issues? anyone know of a potential conflict of interests with running debian?

thanks in advance for your time.

Statistics: Posted by Guest — Mon Aug 23, 2004 3:45 am