egghelp.org community Forum Index
[ egghelp.org home | forum home ]
egghelp.org community
Discussion of eggdrop bots, shell accounts and tcl scripts.
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Something changed Bot won't ctcp

 
Post new topic   Reply to topic    egghelp.org community Forum Index -> Eggdrop Help
View previous topic :: View next topic  
Author Message
hope
Voice


Joined: 10 Dec 2006
Posts: 5

PostPosted: Sun Dec 10, 2006 4:06 am    Post subject: Something changed Bot won't ctcp Reply with quote

I have searched and I know these questions are very tiresome to the folks who help out here, but I'm desperate.

The eggdrop was fine except that it's /whois info was /msg botname hello

I changed that, and along with that, somehow it decided to quit speaking to me via /ctcp like it used to. (I never have been able to dcc chat with it due to my router or something but ctcp worked fine til I did whatever it is I did)

I'm not very good with this, but I am thinking I must have done some simple (I hope!) thing to make this bot not speak to me anymore.

I would very much appreciate the folks who know what they are looking at to please please look at the code for this bot and tell me the error of my ways. Pretty please help the idiot here? (I have used asterisks to change the botname, channel and server to protect the stupid bot owner, namely me.)

Config is as follows:

Quote:
#! /path/to/executable/eggdrop
# ^- This should contain a fully qualified path to your Eggdrop executable.
#
# $Id: eggdrop.conf,v 1.40 2004/08/21 22:43:27 wcc Exp $
#
# This is a sample Eggdrop configuration file which includes all possible
# settings that can be used to configure your bot.
#
# The pound signs (#) that you see at the beginning of some lines mean that
# the remainder of that line is a comment, or just for your information. By
# adding or deleting pound signs, you can comment or uncomment a setting,
# respectively.
#
# Arguments for a command or setting may be inclosed in <>'s or []'s in the
# example/description. Arguments in <>'s are required, while [] means optional.
#
# More detailed descriptions of all these settings can be found in
# doc/settings/.


##### BASIC SETTINGS #####

set username "*Bot"
set admin "******* <email: inbox@*.org>"
set network "*******"
set timezone "EST"
#set offset "-5"
#set my-hostname "*********"
set my-ip "**.**.***.***"

##### LOG FILES #####

set keep-all-logs 1
logfile msbxco * "logs/*Bot.log"
set max-logs 50
set max-logsize 0
set quick-logs 0
set log-time 1
set logfile-suffix ".%d%b%Y"
set switch-logfiles-at 300
set quiet-save 0

##### CONSOLE #####

set console "mkcobxs"


##### FILES AND DIRECTORIES #####

set userfile "*Bot.user"
set sort-users 0
set help-path "help/"
set text-path "text/"
set temp-path "/tmp"
set motd "text/motd"
set telnet-banner "text/banner"


##### BOTNET/DCC/TELNET #####

listen 2121 all
set remote-boots 2
set share-unlinks 1
set protect-telnet 0
set dcc-sanitycheck 0
set ident-timeout 5
set require-p 0
set stealth-telnets 0
set use-telnet-banner 1
set connect-timeout 15
set dcc-flood-thr 5
set telnet-flood 5:60
set paranoid-telnet-flood 0
set resolve-timeout 15
set dcc-portrange 1024:65535

##### MORE ADVANCED SETTINGS #####

# Set the time in minutes that temporary ignores should last.
set ignore-time 5
set hourly-updates 15
set notify-newusers "$owner"
set default-flags "hp"

# Comment these two lines if you wish to enable the .tcl and .set
#commands.
# If you select your owners wisely, you should be okay enabling these.
#unbind dcc n tcl *dcc:tcl
#unbind dcc n set *dcc:set

# If you enable this setting, only permanent owners (owner setting) will
#be
# able to use .tcl and .set. Moreover, if you want only let permanent
#owners
# use .dump, then set this to 2.
set must-be-owner 1

# Set here the maximum number of dcc connections you will allow. You can
# increase this later, but never decrease it.
set max-dcc 50

# If your Eggdrop rejects bots that actually have already disconnected
#from
# another hub, but the disconnect information has not yet spread over the
# botnet due to lag, use this setting. The bot will wait dupwait-timeout
# seconds before it checks again and then finally reject the bot.
set dupwait-timeout 5


########## MODULES ##########

# Below are various settings for the modules included with Eggdrop.
# PLEASE READ AND EDIT THEM CAREFULLY, even if you're an old hand at
# Eggdrop, things change.

# This path specifies the path were Eggdrop should look for its modules.
# If you run the bot from the compilation directory, you will want to set
# this to "". If you use 'make install' (like all good kiddies do Wink, this
# is a fine default. Otherwise, use your head Smile
set mod-path "modules/"


#### DNS MODULE ####

# This module provides asynchronous dns support. This will avoid long
# periods where the bot just hangs there, waiting for a hostname to
# resolve, which will often let it timeout on all other connections.
loadmodule dns

#### CHANNELS MODULE ####

# This module provides channel related support for the bot. Without it,
# you won't be able to make the bot join a channel or save channel
# specific userfile information.
loadmodule channels

# Enter here the filename where dynamic channel settings are stored.
set chanfile "#*"

# Set here how long temporary bans will last (in minutes). If you
# set this setting to 0, the bot will never remove them.
set ban-time 0

# Set here how long temporary exempts will last (in minutes). If you
# set this setting to 0, the bot will never remove them. The bot will
# check the exempts every X minutes, but will not remove the exempt if
# a ban is set on the channel that matches that exempt. Once the ban is
# removed, then the exempt will be removed the next time the bot checks.
# Please note that this is an IRCnet feature.
set exempt-time 0

# Set here how long temporary invites will last (in minutes). If you
# set this setting to 0, the bot will never remove them.
# The bot will check the invites every X minutes, but will not remove
# the invite if a channel is set to +i. Once the channel is -i then
# the invite will be removed the next time the bot checks.
# Please note that this is an IRCnet feature.
set invite-time 60

# Set this setting to 1 if you want your bot to expire
#bans/exempts/invites set
# by other opped bots on the channel.
set force-expire 0

# Set this setting to 1 if you want your bot to share user greets with
#other
# bots on the channel if sharing user data.
set share-greet 1

# Set this setting to 1 if you want to allow users to store an info line.
set use-info 1

# The following settings are used as default values when you .+chan #chan
#or .tcl
# channel add #chan. Look in the section below for explanation of every
#option.

set global-flood-chan 0
set global-flood-deop 3:10
set global-flood-kick 0
set global-flood-join 5:60
set global-flood-ctcp 3:60
set global-flood-nick 5:60
set global-aop-delay 5:30
set global-idle-kick 0
set global-chanmode "nt"
set global-stopnethack-mode 0
set global-revenge-mode 1

set global-chanset {
-autoop -autovoice
-bitch +cycle
+dontkickops +dynamicbans
+dynamicexempts +dynamicinvites
-enforcebans +greet
-inactive +nodesynch
-protectfriends -protectops
-revenge -revengebot
-secret -seen
+shared +statuslog
+userbans +userexempts
+userinvites -protecthalfops
-autohalfop
}

# Add each static channel you want your bot to sit in using this command.
# There are many different possible settings you can insert into this
# command, which are explained below.

#channel add #lamest {
# chanmode "+nt-likm"
# idle-kick 0
# stopnethack-mode 0
# revenge-mode 1
# aop-delay 5:30
# need-op { putserv "PRIVMSG #lamest Surprisedp me cos i'm lame!" }
# need-invite { putserv "PRIVMSG #lamest :let me in!" }
# need-key { putserv "PRIVMSG #lamest :let me in!" }
# need-unban { putserv "PRIVMSG #lamest :let me in!" }
# need-limit { putserv "PRIVMSG #lamest :let me in!" }
# flood-chan 10:60
# flood-deop 3:10
# flood-kick 3:10
# flood-join 5:60
# flood-ctcp 3:60
# flood-nick 5:60
#}

# chanmode +/-<modes>
# This setting makes the bot enforce channel modes. It will always add
# the +<modes> and remove the -<modes> modes.
# idle-kick 0
# This setting will make the bot check every minute for idle
# users. Set this to 0 to disable idle check.
#
# stopnethack-mode 0
# This setting will make the bot de-op anyone who enters the channel
# with serverops. There're seven different modes for this settings:
# 0 turn off,
# 1 isoptest (allow serverop if registered op)
# 2 wasoptest (allow serverop if op before split)
# 3 allow serverop if isop or wasop
# 4 allow serverop if isop and wasop.
# 5 If the channel is -bitch, see stopnethack-mode 3
# If the channel is +bitch, see stopnethack-mode 1
# 6 If the channel is -bitch, see stopnethack-mode 2
# If the channel is +bitch, see stopnethack-mode 4
#
# revenge-mode 1
# This settings defines how the bot should punish bad users when
# revenging. There are four possible settings:
# 0 Deop the user.
# 1 Deop the user and give them the +d flag for the channel.
# 2 Deop the user, give them the +d flag for the channel, and kick
#them.
# 3 Deop the user, give them the +d flag for the channel, kick, and
#ban them.
#
# aop-delay (minimum:maximum)
# This is used for autoop, autohalfop, autovoice. If an op or voice joins
#a
# channel while another op or voice is pending, the bot will attempt to
#put
# both modes on one line.
# aop-delay 0 No delay is used.
# aop-delay X An X second delay is used.
# aop-delay X:Y A random delay between X and Y is used.
#
# need-op { putserv "PRIVMSG #lamest Surprisedp me cos i'm lame!" }
# This setting will make the bot run the script enclosed in brackets
# if it does not have ops. This must be shorter than 120 characters.
# If you use scripts like getops.tcl or botnetop.tcl, you don't need
# to set this setting.
#
# need-invite { putserv "PRIVMSG #lamest :let me in!" }
# This setting will make the bot run the script enclosed in brackets
# if it needs an invite to the channel. This must be shorter than 120
# characters. If you use scripts like getops.tcl or botnetop.tcl, you
# don't need to set this setting.
#
# need-key { putserv "PRIVMSG #lamest :let me in!" }
# This setting will make the bot run the script enclosed in brackets
# if it needs the key to the channel. This must be shorter than 120
# characters. If you use scripts like getops.tcl or botnetop.tcl, you
# don't need to set this setting
#
# need-unban { putserv "PRIVMSG #lamest :let me in!" }
# This setting will make the bot run the script enclosed in brackets
# if it needs to be unbanned on the channel. This must be shorter than
# 120 characters. If you use scripts like getops.tcl or botnetop.tcl,
# you don't need to set this setting
#
# need-limit { putserv "PRIVMSG #lamest :let me in!" }
# This setting will make the bot run the script enclosed in brackets
# if it needs the limit to be raised on the channel. This must be
# shorter than 120 characters. If you use scripts like getops.tcl or
# botnetop.tcl, you don't need to set this setting
#
# flood-chan 10:60
# Set here how many channel messages in how many seconds from one
# host constitutes a flood. Setting this to 0 or 0:0 disables
# flood protection for the channel.
#
# flood-deop 3:10
# Set here how many deops in how many seconds from one host constitutes
# a flood. Setting this to 0 or 0:0 disables deop flood protection for
# the channel.
#
# flood-kick 3:10
# Set here how many kicks in how many seconds from one host constitutes
# a flood. Setting this to 0 or 0:0 disables kick flood protection for
# the channel.
#
# flood-join 5:60
# Set here how many joins in how many seconds from one host constitutes
# a flood. Setting this to 0 or 0:0 disables join flood protection for
# the channel.
#
# flood-ctcp 3:60
# Set here how many channel ctcps in how many seconds from one host
# constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
# protection for the channel.
#
# flood-nick 5:60
# Set here how many nick changes in how many seconds from one host
# constitutes a flood. Setting this to 0 or 0:0 disables nick flood
# protection for the channel.
#

#channel set #lamest +enforcebans +dynamicbans +userbans +dynamicexempts
#+greet
#channel set #lamest +userexempts +dynamicinvites +userinvites +protectops
#channel set #lamest +protectfriends +statuslog +revenge -protecthalfops
#+cycle
#channel set #lamest +revengebot +dontkickops +autovoice -autoop
# -autohalfop
#channel set #lamest -bitch -secret -shared

# There are many different options for channels which you can
# define. They can be enabled or disabled by a plus or minus
# in front of them.
#
# A complete list of all available channel settings:
#
# enforcebans
# When a ban is set, kick people who are on the channel and match
# the ban?
#
# dynamicbans
# Only activate bans on the channel when necessary? This keeps
# the channel's ban list from getting excessively long. The bot
# still remembers every ban, but it only activates a ban on the
# channel when it sees someone join who matches that ban.
#
# userbans
# Allow bans to be made by users directly? If turned off, the bot
# will require all bans to be made through the bot's console.
#
# dynamicexempts
# Only activate exempts on the channel when necessary? This keeps
# the channel's exempt list from getting excessively long. The bot
# still remembers every exempt, but it only activates a exempt on
# the channel when it sees a ban set that matches the exempt. The
# exempt remains active on the channel for as long as the ban is
# still active.
#
# userexempts
# Allow exempts to be made by users directly? If turned off, the
# bot will require all exempts to be made through the bot's console.
#
# dynamicinvites
# Only activate invites on the channel when necessary? This keeps
# the channel's invite list from getting excessively long. The bot
# still remembers every invite, but the invites are only activated
# when the channel is set to invite only and a user joins after
# requesting an invite. Once set, the invite remains until the
# channel goes to -i.
#
# userinvites
# Allow invites to be made by users directly? If turned off, the
# bot will require all invites to be made through the bot's console.
#
# autoop
# Op users with the +o flag as soon as they join the channel?
# This is insecure and not recommended.
#
# authalfoop
# Halfop users with the +l flag as soon as they join the channel?
# This is insecure and not recommended.
#
# bitch
# Only let users with +o) flag be opped on the channel?
#
# greet
# Say a user's info line when they join the channel?
#
# protectops
# Re-op a user with the +o flag if they get deopped?
#
# protecthalfops
# Re-halfop a user with the +l flag if they get dehalfopped?
#
# protectfriends
# Re-op a user with the +f flag if they get deopped?
#
# statuslog
# Log the channel status line every 5 minutes? This shows the bot's
# status on the channel (op, voice, etc.), The channel's modes, and
# the number of +m/+o/+v/+n/+b/+e/+I users on the channel. A sample
# status line follows:
#
# [01:40] @#lamest (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
#
# revenge
# Remember people who deop/kick/ban the bot, valid ops, or friends
# and punish them? Users with the +f flag are exempt from revenge.
#
# revengebot
# This is similar to to the 'revenge' option, but it only triggers
# if a bot gets deopped, kicked or banned.
#
# autovoice
# Voice users with the +v flag when they join the channel?
#
# secret
# Prevent this channel from being listed on the botnet?
#
# shared
# Share channel-related user info for this channel?
#
# cycle
# Cycle the channel when it has no ops?
#
# dontkickops
# Do you want the bot not to be able to kick users who have the +o
# flag, letting them kick-flood for instance to protect the channel
# against clone attacks.
#
# inactive
# This prevents the bot from joining the channel (or makes it leave
# the channel if it is already there). It can be useful to make the
# bot leave a channel without losing its settings, channel-specific
# user flags, channel bans, and without affecting sharing.
#
# seen
# Respond to seen requests in the channel? The seen module must be
# loaded for this to work.
#
# nodesynch
# Allow non-ops to perform channel modes? This can stop the bot from
# fighting with services such as ChanServ, or from kicking IRCops when
# setting channel modes without having ops.

# Here is a shorter example:
#
# channel add #botcentral {
# chanmode "+mntisl 1"
# idle-kick 1
# }
# channel set #botcentral +bitch +enforcebans -greet +revenge


#### SERVER MODULE ####

# This module provides the core server support. You have to load this
# if you want your bot to come on IRC. Not loading this is equivalent
# to the old NO_IRC define.
loadmodule server

# What is your network?
# 0 = EFnet (non +e/+I hybrid)
# 1 = IRCnet
# 2 = Undernet
# 3 = DALnet
# 4 = EFnet +e/+I hybrid
# 5 = Others
set net-type 5

# Set the nick the bot uses on IRC, and on the botnet
# unless you specify a separate botnet-nick, here.

set nick "*Bot"

# Set the alternative nick which the bot uses on IRC if the nick specified
# by 'set nick' is unavailable. All '?' characters will be replaced by
# random
# numbers.

set altnick "*BotTwo"

# Set what should be displayed in the real-name field for the bot on IRC.
set realname "NA Works"

# Set here a script to run (if any) when first connecting to a server.
# This is limited to 120 characters.
set init-server { source logon }
#This is a Tcl script to be run #immediately after connecting to a
#server.
bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +iR-ws"
putquick "privmsg nickserv :identify **********"
}

# Set the default port which should be used if none is specified with
# '.jump' or in 'set servers'.
set default-port 6667

# This is the bot's server list. The bot will start at the first server
#listed,
# and cycle through them whenever it gets disconnected. You need to change
# these
# servers to YOUR network's servers.
#
# The format is:
# server[:port[:password]]
#
# Both the port and password fields are optional; however, if you want to
# set a
# password you must also set a port. If a port isn't specified it will
# default to
# your default-port setting.
set servers {
irc.wikkedwire.com:6667
america.wikkedwire.com:6667
atlantis.wikkedwire.com:6667
}

# This setting makes the bot try to get his original nickname back if its
# primary nickname is already in use.
set keep-nick 1

# Set this to 1 if you don't want your the bot to strip a leading '~'
# on user@hosts.
set strict-host 0

# This setting makes the bot squelch the error message when rejecting a
# DCC
# CHAT or SEND. Normally it tells the DCC user that the CHAT or SEND has
# been rejected because they don't have access.
# Please note, sometimes IRC server operators detect bots that way.
set quiet-reject 0

# If you want your bot to answer lower case ctcp requests (non rfc-
# compliant), set this setting to 1. mIRC will do this, most other
# clients will not.
set lowercase-ctcp 1

# Set how many ctcps should be answered at once.
set answer-ctcp 3

# Set here how many msgs in how many seconds from one host constitutes
# a flood. If you set this to 0:0, msg flood protection will be disabled.
set flood-msg 5:10

# Set here how many ctcps in how many seconds from one host constitutes
# a flood. If you set this to 0:0, ctcp flood protection will be disabled.
set flood-ctcp 3:10

# This settings makes the bot cycle forever through the server list until
# it successfully connects to one.
set never-give-up 1

# Often, IRC servers call themselves a name other than their actual
# hostname. If you want Eggdrop to replace your entry in the config
# file with this name, set this to 1. If you set this setting to 0,
# Eggdrop will keep a separate list of what IRC servers call themselves.
set strict-servernames 0

# This setting defines how long eggdrop should wait before moving from one
# server to another on disconnect. If you set 0 here, Eggdrop will not
# wait
# at all and will connect instantly. Setting this too low could result in
# your bot being K:Lined.
set server-cycle-wait 60

# Set here how long Eggdrop should wait for a response when connecting to
# a
# server before giving up and moving on to next server.
set server-timeout 30

# If the number of servers on the net gets below this number, the bot
# will jump to a new server (it will assume it's on the losing end of
# a netsplit). Set this to 0 to turn off. If your bot is running on
# any major IRC network, this should probably be turned off.
set servlimit 0

# Set this to 1 if Eggdrop should check for stoned servers? (where the
# server connection has died, but Eggdrop hasn't been notified yet).
set check-stoned 1

# This setting allows you the logging of all information received from the
# server via console mode 'r'.
# NOTE: This is 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 use-console-r 1

# This setting allows you the logging of all information sent to the
#server
# via console/log mode 'v'. It also allows logging of botnet traffic via
# console/log mode 't'.
# NOTE: This is a large security hole, allowing people to see passwords.
# This is now restricted to +n users only. Please choose your owners with
# care.
set debug-output 0

# If you want your bot to exit the server if it receives an ERROR message,
# set this to 1.
set serverror-quit 1

# Set here the maximum number of lines to queue to the server. If you're
# going to dump large chunks of text to people over IRC, you will probably
# want to raise this. 300 is fine for most people though.
set max-queue-msg 300

# If you want Eggdrop to trigger binds for ignored users, set this to 1.
set trigger-on-ignore 0

# Allow identical messages in the mode queue?
set double-mode 0

# Allow identical messages in the server queue?
set double-server 0

# Allow identical messages in the help queue?
set double-help 0

# This optimizes the kick queue. It also traces nick changes and parts in
# the channel and changes the kick queue accordingly. There are three
# different options for this setting:
# 0 = Turn it off.
# 1 = Optimize the kick queue by summarizing kicks.
# 2 = Trace nick changes and parts on the channel and change the queue
# accordingly. For example, bot will not try to kick users who have
# already parted the channel.
# ATTENTION: Setting 2 is very CPU intensive.
set optimize-kicks 0

### SERVER MODULE - OTHER NETWORKS (net-type 5) ###

# This settings defines how umode +r is understood by Eggdrop. Some
# networks use +r to indicate a restricted connection. If this is your
# case, and you want your bot to leave restricted servers and jump to
# the next server on its list, then set it to 1.
set check-mode-r 1

# This setting allows you to specify the maximum nick-length supported by
# your network. The default setting is 9. The maximum supported length by
# Eggdrop is 32.
set nick-len 32

#### CTCP MODULE ####

# This module provides the normal ctcp replies that you'd expect.
# Without it loaded, CTCP CHAT will not work. The server module
# is required for this module to function.
loadmodule ctcp

# Set here how the ctcp module should answer ctcps. There are 3 possible
# operating modes:
# 0: Normal behavior is used.
# 1: The bot ignores all ctcps, except for CHAT and PING requests
# by users with the +o flag.
# 2: Normal behavior is used, however the bot will not answer more
# than X ctcps in Y seconds (defined by 'set flood-ctcp').
set ctcp-mode 0

# There are also several variables to help make your bot less noticeable.
# They are: ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set
# to set
# them to values you'd like.


#### IRC MODULE ####

# This module provides basic IRC support for your bot. You have to
# load this if you want your bot to come on IRC. The server and channels
# modules must be loaded for this module to function.
loadmodule irc

# Set this to 1 if you want to bounce all server bans.
set bounce-bans 1

# Set this to 1 if you want to bounce all server modes.
set bounce-modes 0

# Set here the maximum number of bans you want the bot to set on a
# channel.
# Eggdrop will not place any more bans if this limit is reached. Undernet
# and IRCnet currently allow 30 bans, EFnet allows 20, and DALnet allows
# 100.
set max-bans 20

# There is a global limit for +b/+e/+I modes. This limit is currently set
# to
# 30 on IRCu 2.10 servers.
set max-modes 30

# Set this to 1 if you want the bot to kick for control character/ctcp
# avalanches to a channel. Remember that if it does, it won't ban them.
# This can start kick floods.
set kick-fun 0

# Set this to 1 if you want the bot to ban for control character/ctcp
# avalanches to a channel. This can prevent kick floods, but it also can
# fill the banlist.
set ban-fun 0

# If you want people to be able to add themselves to the bot's userlist
# with the default userflags (defined above in the config file) via the
# 'hello' msg command, set this to 1.
set learn-users 0

# Set here the time (in seconds) to wait for someone to return from
# a netsplit (i.e. wasop will expire afterwards). Set this to 1500
# on IRCnet since its nick delay stops after 30 minutes.
set wait-split 600

# Set here the time (in seconds) that someone must have been off-channel
# before re-displaying their info line.
set wait-info 180

# Set this to the maximum number of bytes to send in the arguments
# of modes sent to the server. Most servers default this to 200.
set mode-buf-length 200

# Many IRCops find bots by seeing if they reply to 'hello' in a msg.
# You can change this to another word by un-commenting the following
# two lines and changing "myword" to the word wish to use instead of
# 'hello'. It must be a single word.
#unbind msg - hello *msg:hello
#bind msg - myword *msg:hello

# Many takeover attempts occur due to lame users blindly /msg ident'ing to
# the bot and attempting to guess passwords. We now unbind this command by
# default to discourage them. You can enable this command by un-commenting
# the following two lines.
unbind msg - ident *msg:ident
unbind msg - addhost *msg:addhost

# If you are so lame you want the bot to display peoples info lines, even
# when you are too lazy to add their chanrecs to a channel, set this to 1.
# *NOTE* This means *every* user with an info line will have their info
# line displayed on EVERY channel they join (provided they have been gone
# longer than wait-info).
set no-chanrec-info 0

### IRC MODULE - OTHER NETWORKS (net-type 5) ###

# Attention: Use these settings *only* if you set 'net-type' to 5!

# If your network supports more users per kick command then 1, you can
# change this behavior here. Set this to the number of users to kick at
# once, or set this to 0 for all at once.
#set kick-method 1

# Some networks allow you to stack lots of channel modes into one line.
# They're all guaranteed to support at least 3, so that's the default.
# If you know your network supports more, you may want to adjust this.
#set modes-per-line 7

# Some networks don't include the +l limit and +k or -k key modes
# in the modes-per-line (see above) limitation. Set include-lk to 0 for
# these networks.
set include-lk 1

# If your network doesn't use rfc 1459 compliant string matching routines,
# set this to 0.
set rfc-compliant 0


#### TRANSFER MODULE ####

# The transfer module provides dcc send/get support and userfile transfer
# support for userfile sharing. Un-comment the next line to load it if you
# need this functionality.
loadmodule transfer

# Set here the maximum number of simultaneous downloads to allow for
# each user.
set max-dloads 3

# Set here the block size for dcc transfers. ircII uses 512 bytes,
# but admits that may be too small. 1024 is standard these days.
# Set this to 0 to use turbo-dcc (recommended).
set dcc-block 1024

# Enable this setting if you want to copy files into the /tmp directory
# before sending them. This is useful on most systems for file stability,
# but if your directories are NFS mounted, it's a pain, and you'll want
# to set this to 0. If you are low on disk space, you may also want to
# set this to 0.
set copy-to-tmp 1

# Set here the time (in seconds) to wait before an inactive transfer
# times out.
set xfer-timeout 30


#### SHARE MODULE ####

# This module provides userfile sharing support between two directly
# linked bots. The transfer and channels modules are required for this
# module to correctly function. Un-comment the following line to load
# the share module.
loadmodule share

# Settings in this section must be un-commented before setting.

# When sharing user lists, DON'T ACCEPT global flag changes from other
# bots?
# NOTE: The bot will still send changes made on the bot, it just won't
# accept
# any global flag changes from other bots.
#set private-global 0

# When sharing user lists, if private-global isn't set, which global flag
# changes from other bots should be ignored?
set private-globals "mnot"

# When sharing user lists, don't accept ANY userfile changes from other
# bots? Paranoid people should use this feature on their hub bot. This
# will force all userlist changes to be made via the hub.
set private-user 0

# This setting makes the bot discard its own bot records in favor of
# the ones sent by the hub.
# NOTE: No passwords or botflags are shared, only ports and
# address are added to sharing procedure. This only works with hubs that
# are v1.5.1 or higher.
set override-bots 0


#### COMPRESS MODULE ####

# This module provides provides support for file compression. This allows
# the
# bot to transfer compressed user files and therefore save a significant
# amount
# of bandwidth. The share module must be loaded to load this module.
# Un-comment
# the following line to the compress module.
loadmodule compress

# Allow compressed sending of user files? The user files are
# compressed with the compression level defined in `compress-level'.
set share-compressed 1

# This is the default compression level used.
set compress-level 9


#### FILESYSTEM MODULE ####

# This module provides an area within the bot where users can store
# files. With this module, the bot is usable as a file server. The
# transfer module is required for this module to function. Un-comment
# the following line to load the filesys module.
#loadmodule filesys

# Set here the 'root' directory for the file system.
set files-path "/home/mydir/filesys"

# If you want to allow uploads, set this to the directory uploads
# should be put into. Set this to "" if you don't want people to
# upload files to your bot.
set incoming-path "/home/mydir/filesys/incoming"

# If you don't want to have a central incoming directory, but instead
# want uploads to go to the current directory that a user is in, set
# this setting to 1.
set upload-to-pwd 0

# Eggdrop creates a '.filedb' file in each subdirectory of your file area
# to keep track of its own file system information. If you can't do that
# (for
# example, if the dcc path isn't owned by you, or you just don't want it
# to do
# that) specify a path here where you'd like all of the database files to
# be
# stored instead.
set filedb-path ""

# Set here the maximum number of people that can be in the file area at
# once.
# Setting this to 0 makes it effectively infinite.
set max-file-users 20

# Set here the maximum allowable file size that will be received (in kb).
# Setting this to 0 makes it effectively infinite.
set max-filesize 1024


#### NOTES MODULE ####

# This module provides support for storing of notes for users from each
# other. Note sending between currently online users is supported in the
# core, this is only for storing the notes for later retrieval.
loadmodule notes

# Set here the filename where private notes between users are stored.
set notefile "*Bot.notes"

# Set here the maximum number of notes to allow to be stored for
# each user (to prevent flooding).
set max-notes 50

# Set here how long (in days) to store notes before expiring them.
set note-life 60

# Set this to 1 if you want to allow users to specify a forwarding
# address for forwarding notes to another account on another bot.
set allow-fwd 0

# Set this to 1 if you want the bot to let people know hourly if they
# have any notes.
set notify-users 1

# Set this to 1 if you want the bot to let people know on join if they
# have any notes.
set notify-onjoin 1

# Comment out this next line. Otherwise, your bot won't start.
#die "You didn't edit your config file like you were told, did you?"


#### CONSOLE MODULE ####

# This module provides storage of console settings when you exit the
# bot or type .store on the partyline.
loadmodule console

# Save users console settings automatically? Otherwise, they have
# to use the .store command.
set console-autosave 1

# If a user doesn't have any console settings saved, which channel
# do you want them automatically put on?
set force-channel 0

# Enable this setting if a user's global info line should be displayed
# when they join a botnet channel.
set info-party 0


#### SEEN MODULE ####

# This module provides very basic seen commands via msg, on channel or via
# dcc.
# This module works only for users in the bot's userlist. If you are
# looking for
# a better and more advanced seen module, try the gseen module by G'Quann.
# You
# can find it at http://www.visions-of-fantasy.de/gseen.mod/.
loadmodule seen


#### BLOWFISH MODULE ####

# IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
# Eggdrop encrypts its userfile, so users can have secure passwords.
# Please note that when you change your encryption method later (i.e.
# using other modules like a md5 module), you can't use your current
# userfile anymore. Eggdrop will not start without an encryption module.
loadmodule blowfish


#### ASSOC MODULE ####

# This module provides assoc support, i.e. naming channels on the botnet.
# You can load it by un-commenting the following line.
loadmodule assoc

#### WIRE MODULE ####

# This module provides all the standard .wire commands via dcc. It is an
# encrypted partyline communication tool, compatible with wire.tcl. An
# encryption module must be loaded to use this module. Un-comment the
# following line to load the wire module.
loadmodule wire

#### UPTIME MODULE ####

# This module reports uptime statistics to http://uptime.eggheads.org.
# Go look and see what your uptime is! It takes about 9 hours to show up,
# so if your bot isn't listed, try again later.
#
# Information sent to the server includes the bot's uptime, botnet-nick,
# server, version, and IP address. This information is stored in a
# temporary
# logfile for debugging purposes only. The only publicly available
# information
# will be the bot's botnet-nick, version and uptime. If you do not wish
# for this
# information to be sent, comment out the following line.
#loadmodule uptime

##### SCRIPTS #####

# This is a good place to load scripts to use with your bot.

# This line loads script.tcl from the scripts directory inside your
# Eggdrop's
# directory. All scripts should be put there, although you can place them
# where
# you like as long as you can supply a fully qualified path to them.
#
# source scripts/script.tcl
source scripts/egghttp.tcl
source scripts/alltools.tcl
source scripts/action.fix.tcl
source scripts/compat.tcl
source scripts/quote.tcl
source scripts/advertise.tcl
source scripts/weather3.8.tcl
Back to top
View user's profile Send private message
rosc2112
Revered One


Joined: 19 Feb 2006
Posts: 1454
Location: Northeast Pennsylvania

PostPosted: Sun Dec 10, 2006 4:31 am    Post subject: Reply with quote

Connect to your bot by telnet and then while you're logged in telnet, try to dcc connect and see what shows up in the console log, or if you can't connect by telnet, turn on quick-logs and check the logfile, it should show what's going on. Most likely you're having either firewall/nat problems, or you don't have the right usermask for your login.
Back to top
View user's profile Send private message
hope
Voice


Joined: 10 Dec 2006
Posts: 5

PostPosted: Sun Dec 10, 2006 2:07 pm    Post subject: Reply with quote

rosc2112 wrote:
Connect to your bot by telnet and then while you're logged in telnet, try to dcc connect and see what shows up in the console log, or if you can't connect by telnet, turn on quick-logs and check the logfile, it should show what's going on. Most likely you're having either firewall/nat problems, or you don't have the right usermask for your login.


I can connect by telnet, and have found this command: .console +mcobxs (found http://www.egghelp.org/enhance.htm in the "Keep an eye on things
" section) but get command not found.

Also, as stated, I've never been able to dcc chat with bot due to either firewall/nat (router) troubles . Chatting by /ctcp is fine by me, but can't do that either, which is the main trouble.

I don't mean to be dense, but I just don't know what to do next.
Back to top
View user's profile Send private message
rosc2112
Revered One


Joined: 19 Feb 2006
Posts: 1454
Location: Northeast Pennsylvania

PostPosted: Sun Dec 10, 2006 5:05 pm    Post subject: Reply with quote

Did you check the logs? That would give more information about the errors.
Back to top
View user's profile Send private message
hope
Voice


Joined: 10 Dec 2006
Posts: 5

PostPosted: Sun Dec 10, 2006 11:24 pm    Post subject: Reply with quote

This is what I get when I look at the log:

CTCP CHAT: from ******** (IP Here) $
[02:25] #channelname (+strn) : [m/11 o/4 h/0 v/0 n/7 b/9 e/0 I/0]


Question
Back to top
View user's profile Send private message
rosc2112
Revered One


Joined: 19 Feb 2006
Posts: 1454
Location: Northeast Pennsylvania

PostPosted: Mon Dec 11, 2006 12:02 am    Post subject: Reply with quote

Is the ip a 192.* or other LOCAL LAN ip? Are there any other msgs? Seriously, you need to either read documentation to figure out the problem or provide more information, we can't guess what the problem is.
Back to top
View user's profile Send private message
hope
Voice


Joined: 10 Dec 2006
Posts: 5

PostPosted: Mon Dec 11, 2006 1:06 am    Post subject: Reply with quote

That's what the logfile said rosc2112.

I am connecting via a router, my IP address is: 192.168.1.2

Subnet mask is: 255.255.255.0

Default Gateway is: 192.168.1.1

Sorry I"ve not been more clear, I'm trying to. I've been reading documentation for a while now and just don't know where to look anymore, that's why I came here. Nothing has changed with my router or my settings that I'm aware of, and I thought it was the change I had made to the .config. but now I'm not so sure.

I had hoped someone would look at the config and be able to spot right off what I did, but I see that perhaps that's not the problem at all.
Back to top
View user's profile Send private message
rosc2112
Revered One


Joined: 19 Feb 2006
Posts: 1454
Location: Northeast Pennsylvania

PostPosted: Mon Dec 11, 2006 1:14 am    Post subject: Reply with quote

In your eggdrop.conf:

Quote:
# If you have a NAT firewall (you box has an IP in one of the following
# ranges: 192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255,
# 10.0.0.0-10.255.255.255 and your firewall transparently changes your
# address to a unique address for your box) or you have IP masquerading
# between you and the rest of the world, and /dcc chat, /ctcp chat or
# userfile sharing aren't working, enter your outside IP here. Do not
# enter anything for my-ip or my-hostname if you use this setting.
#set nat-ip "127.0.0.1"


Also read:

http://forum.egghelp.org/viewtopic.php?t=10399
Back to top
View user's profile Send private message
hope
Voice


Joined: 10 Dec 2006
Posts: 5

PostPosted: Mon Dec 11, 2006 2:38 am    Post subject: Reply with quote

Thanks so much rosc2112 - I did read that but it's making more sense to me now that I'm reading it over again.

I wonder though, why it would work one day and not the next? Could the router have changed and no one told me?
Back to top
View user's profile Send private message
rosc2112
Revered One


Joined: 19 Feb 2006
Posts: 1454
Location: Northeast Pennsylvania

PostPosted: Mon Dec 11, 2006 4:51 am    Post subject: Reply with quote

May have been a dynamic ip, which get reassigned perioidically.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    egghelp.org community Forum Index -> Eggdrop Help All times are GMT - 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Forum hosting provided by Reverse.net

Powered by phpBB © 2001, 2005 phpBB Group
subGreen style by ktauber