willyw wrote:I don't know.
I was expecting for there to be more to the error message - to help give us some clues.
I wouldn't have been surprised if it had been something like : too many connections from your ip , if your bot is on a popular shell.
If you've tried it with the bot, using -n switch, you could then take it to an Eggdrop channel and ask there. You could pastebin whatever eggdrop shows you, and perhaps somebody might have some ideas. Freenode irc network is good. And the channel is: #eggdrop .
You could also - as an irssi problem - find some "help" type channel on Dalnet itself, and ask there.
I'm sorry that I don't have a direct answer for you.
When you do find it, please let us know what it was - it might be helpful info for somebody else someday.
I have already asked on the #eggdrop channel on freenode but I haven't received any answer.
willyw wrote:Just remembered :
Besides watching it try to log in, when launched with the -n switch, you might want to experiment with the logging flags too.
They are listed in the eggdrop.conf that came with your bot.
Perhaps adding some would get it to log more, and you might spy a clue in the log.
Here's my log settings, just in case:
Code: Select all
# This setting allows you the logging of raw incoming server traffic via
# console/log flag 'r', raw outgoing server traffic via console/log mode 'v',
# raw botnet traffic via console/log mode 't', and raw share traffic via
# console/log mode 'h'. These flags can create a large security hole,
# allowing people to see user passwords. This is now restricted to +n users
# only. Please choose your owners with care.
set raw-log 1
# This creates a logfile named eggdrop.log containing private msgs/ctcps,
# commands, errors, and misc. info from any channel.
logfile bdhorstvwx * "logs/dalnet"
# This creates a logfile named lamest.log containing joins, parts,
# netsplits, kicks, bans, mode changes, and public chat on the
# channel #lamest.
logfile m * "logs/private-dalnet"
ComputerTech wrote:ALSO this may sound stupid but how do you know the bot is NOT connecting to dalnet
try /whois botnick
and
have you did /msg botnick hello yet to it or is this bot brand new?
The eggdrop keeps trying to reconnect, constantly, and the /whois doesn't find it.
ComputerTech wrote:did you use the address us.dal.net as i suggested above ? could be a problem since thats the only address my bot uses
Code: Select all
Just remembered :
Besides watching it try to log in, when launched with the -n switch, you might want to experiment with the logging flags too.
They are listed in the eggdrop.conf that came with your bot.
Perhaps adding some would get it to log more, and you might spy a clue in the log
this also is a great idea of willyw
i recommend doing that also along with using address us.dal.net port 6667
and if you like come chat with us at #eggdrop dalnet or my channel on dalnet #computertech123
I have also tried to connect to us.dal.net 6667 to the same results on both eggdrop and irssi:
Code: Select all
17:07 -!- Irssi: Looking up us.dal.net
17:07 -!- Irssi: Connecting to us.dal.net [154.35.138.250] port 6667
17:07 -!- Irssi: Connection to us.dal.net established
17:07 -!- Irssi: Connection lost to us.dal.net
