This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

telnet default error [solved]

General support and discussion of Eggdrop bots.
Post Reply
User avatar
shikashinigami
Voice
Posts: 11
Joined: Fri May 26, 2006 2:15 pm
Location: bah

telnet default error [solved]

Post by shikashinigami »

Hi everyone, I've done quite well so far on my own with my eggdrop bot, but I've encountered a problem I haven't been able to find after quite some time of searching around in this forum. So here it is:

My bot starts up but doesn't appear in my room, when I try to telnet to the bot puTTY says : "Trying to connect (with the default eggdrop IP)" after a minute or so the connection time's out.

I have my IP set to the vhost I want, but for some reason my bot has stopped trying to connect on that vhost. It did do it once, but I encountered another error that I've since fixed. *sighs*

Please help. Thanks in advance!
Last edited by shikashinigami on Sun May 28, 2006 10:22 am, edited 1 time in total.
User avatar
De Kus
Revered One
Posts: 1361
Joined: Sun Dec 15, 2002 11:41 am
Location: Germany

Post by De Kus »

is your problem related with that one?
http://forum.egghelp.org/viewtopic.php? ... ibrarypath
if yes, you should really investigate more before posting.
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens...
User avatar
shikashinigami
Voice
Posts: 11
Joined: Fri May 26, 2006 2:15 pm
Location: bah

Post by shikashinigami »

no, it's not related. I'm running -m and my bot is connected to the IRC server. I just can't telnet because my vhost's IP keeps setting to the default. And the default time's out, it won't connect.
Muahaha! Ding I say, ding!
User avatar
De Kus
Revered One
Posts: 1361
Joined: Sun Dec 15, 2002 11:41 am
Location: Germany

Post by De Kus »

well, if its really related to binding to wrong addresse, this would be very strange. Since unless something chances my-ip it doesnt get changed by itself and afaik eggdrop doesn't try to bind to 0.0.0.0 if my-ip fails.
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens...
User avatar
shikashinigami
Voice
Posts: 11
Joined: Fri May 26, 2006 2:15 pm
Location: bah

Post by shikashinigami »

hmm. So strange. The bot itself is 'working' but when I try to telnet to the bot it says:

"Trying 66.252.10.131..." then it time's out/unable to connect.

This address is my shell account's default IP... could it be a problem with my shell account?
Muahaha! Ding I say, ding!
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

Post by Alchera »

shikashinigami wrote:P... could it be a problem with my shell account?
It very well could be.
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
User avatar
DragnLord
Owner
Posts: 711
Joined: Sat Jan 24, 2004 4:58 pm
Location: C'ville, Virginia, USA

Post by DragnLord »

have you tried starting the bot using the -nt switch so you can what goes on from the bot's partyline?
User avatar
De Kus
Revered One
Posts: 1361
Joined: Sun Dec 15, 2002 11:41 am
Location: Germany

Post by De Kus »

how do you define 'working'? Does it show up on IRC? Does it write logfiles? You are confusing, on one side you say the bot doesnt show up and the next post you say it is 'working'. What now?
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens...
User avatar
shikashinigami
Voice
Posts: 11
Joined: Fri May 26, 2006 2:15 pm
Location: bah

Post by shikashinigami »

sorry for being confusing. I don't mean too... it's the whole I'm-a-n00b thing. Anyway the -nt thing worked. Thanks! What happened was I didn't know how to properly close down the telnet connection I had the one time I opened it. So it stayed open. Since I already had a connection with the IP I wanted to use (via the first telnet connection) it wouldn't let me open another. Thanks for your help everyone!
Muahaha! Ding I say, ding!
Post Reply