Nothing happens when I try to telnet to the bot.willyw wrote:It might be an interesting experiment, to try to telnet into your bot, using Putty.yutsi wrote: ...
Alright. I downloaded PuTTY and PuTTYTel. My IRC client is Icechat. I changed listen 3333 all to listen 60537 all. I checked Windows firewall and it is letting windrop through. And I can't get my routers configuration page.
Run Putty.
In the "hostname" box, enter: localhost
In the "port" box, enter: 60537
and try it, when your bot is up and running. Let us know what happens.
I've tried the above... using putty, on my Windows 7 computer, while running Windrop on the same computer. (Using the 'listen' port that my bot is config'd for), and I could log in to my test Windrop.
Ok on Icechat. I'm not familiar with it though.
For your router's configuration:
Examine your router for brand name, model number, etc.
Then visit: http://portforward.com/
At that site, are listed MANY routers, along with step-by-step intructions for forwarding ports. Take some time, and explore that site, before plunging ahead.
I don't know. Sorry. I'm not familiar with it.yutsi wrote:Comcast set up my CG814WG v2 for me, and now I can't access http://192.168.0.1/ with any of the combos I found online, including comcast/1234 and admin/password and many permutations of those. Is there any way for me to find the password without resetting the router? I need to access this for the instructions in portforward.com.
Please be specific - what commands did you try?yutsi wrote:I was able to successfully /ctcp yutsieggdrop chat, although all that happened was [19:54] [yutsieggdrop ERROR Reply] : no password set. I'm still unable to get a response from /msg yutsieggdrop [Command] except for /msg yutsieggdrop help
What /msg and what /ctcp did you try?Great, now that I've set password it won't respond to /msg or /ctcp anymore.
If the bot knows you as owner- I would expect it to reply to those other commands.yutsi wrote:I tried most of the commands listed in /msg yutsieggdrop help and I tried /ctcp yutsieggdrop chatwillyw wrote: What /msg and what /ctcp did you try?
Code: Select all
-botnick- /MSG botnick PASS <password> - This sets a password for your handle. You need a password to use most commands and/or chat the bot.
-botnick- /MSG botnick PASS <oldpass> <newpass> - Allows you to change your password.
Set it to 0# This setting makes the bot squelch the error message when rejecting a DCC
# CHAT, SEND or message command. Normally, Eggdrop notifies the user that the
# command has been rejected because they don't have access. Note that sometimes
# IRC server operators detect bots that way.
set quiet-reject 1
He's not responding when I try to change my password.willyw wrote:If the bot knows you as owner- I would expect it to reply to those other commands.yutsi wrote:I tried most of the commands listed in /msg yutsieggdrop help and I tried /ctcp yutsieggdrop chatwillyw wrote: What /msg and what /ctcp did you try?
I wonder if your password truly was set.
Did it say that it accepted it?
As for the /ctcp botnick chat command, usually that causes the bot to send you a request for chat, that you have to acknowledge.
I don't know what that would appear as, with IceChat.
What happens if you try changing your password?
Just curious if the bot responds to that.Code: Select all
-botnick- /MSG botnick PASS <password> - This sets a password for your handle. You need a password to use most commands and/or chat the bot. -botnick- /MSG botnick PASS <oldpass> <newpass> - Allows you to change your password.
I already did set it to 0.willyw wrote:In your eggdrop.conf, check this setting:
set quiet-reject 1
Set it to 0# This setting makes the bot squelch the error message when rejecting a DCC
# CHAT, SEND or message command. Normally, Eggdrop notifies the user that the
# command has been rejected because they don't have access. Note that sometimes
# IRC server operators detect bots that way.
set quiet-reject 1
Perhaps you'll then get some response, that will be a clue.
Again, I'm not familiar with IceChat, as to where you'd see the response from the bot.... but with quiet-reject set to 0, and a user that is unknown to the bot, I see:yutsi wrote:I already did set it to 0.willyw wrote:In your eggdrop.conf, check this setting:
set quiet-reject 1
Set it to 0# This setting makes the bot squelch the error message when rejecting a DCC
# CHAT, SEND or message command. Normally, Eggdrop notifies the user that the
# command has been rejected because they don't have access. Note that sometimes
# IRC server operators detect bots that way.
set quiet-reject 1
Perhaps you'll then get some response, that will be a clue.
1.) See the first line of your eggdrop.conf. It is:yutsi wrote:Here's my eggdrop.conf: http://www.mediafire.com/file/0n9hjbnix ... gdrop.conf
Code: Select all
#! /path/to/executable/eggdrop
Code: Select all
#!C:/bot/eggdrop
Code: Select all
C:/bot/
Code: Select all
set console "yutsi"
Code: Select all
set console "mkcobxs"
Code: Select all
set nat-ip "69.xxx.xx.xx"