I normally can't initiate dcc anyways, but I was just playing around trying to see if I could fix the problem, and well, I never got that message before (the bot sent it.)
not sure what you mean by 'you can't usually initiate dcc anyways'. That error most likely comes from the listen variable in the conf file, that is, if it is indeed an eggdrop problem, and not a problem on your end (i.e. firewall, router, ect)
# This opens a telnet port by which you and other bots can interact with the
# Eggdrop by telneting in.
#
# There are more options for the listen command in doc/tcl-commands.doc. Note
# that if you are running more than one bot on the same machine, you will want
# to space the telnet ports at LEAST 5 apart, although 10 is even better.
#
# Valid ports are typically anything between 1025 and 65535 assuming the
# port is not already in use.
#
# If you would like the bot to listen for users and bots in separate ports,
# use the following format:
#
# listen 3333 bots
# listen 4444 users
#
# If you wish to use only one port, use this format:
#
# listen 3333 all
#
# You need to un-comment this line and change the port number in order to open
# the listen port. You should not keep this set to 3333.
#listen 3333 all
EnglishExpress wrote:I got that when trying to dcc my friends eggdrop.
I normally can't initiate dcc anyways, but I was just playing around trying to see if I could fix the problem, and well, I never got that message before (the bot sent it.)
I can accept dcc though.
This is usually a result of a setting in your IRC client (I've seen this with mIRC a lot), not the bot.
Check your client's setting for DCC ports.
DCC can be difficult to set up. The DCC ports in your IRC client must match those settings in your router/firewall that pass traffic to your PC.
If you can't get it to work, try /ctcp <botnick> chat
Otherwise you will have to use telnet to get on the bot's partyline (for this you will have to set a port in the bot's .conf file). See one of the posts above which show the line #listen 3333 all. Remove the hash (#) at the start of the line and set a port value (usually something above 7500 to avoid conflict). Restart the bot. Telnet the bot's host/vhost on that port. NOT the host/port you use for SSH to the shell.
I made it, amongst other things, to help users with DCC and CTCP issues. After installation, click connect, create a new connection and select the newly created connection.
A few things,
The dcc chat request is improperly formatted, as there is one parameter too many.
The IP translates to 1.1.1.1, which should not be present on the net. Some soho router/firewalls do use the 1.1.1.0/24 network (improperly, I might add. only 10.0.0.0/8 and 192.168.0.0/16 should be used for private networks).
The port is 0, which is not a valid tcp-port for connections, but can be used in the sockets layer when creating a new socket to let the IP-stack freely select a random port for the socket. This is the cause for your eggdrop complaining.
Actually, now that I think of it, that looks alot like a "Reverse DCC" request. This extension is not supported by eggdrop. Make sure you disable any such features in your irc client when connecting with your eggdrop.