egghelp.org community

[EnglishExpress]

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.

[YooHoo]

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)

[DragnLord]

[samhudson]

sorry for bringing up an old topic, but this is the only thread i can find on the internet about this issue!

im getting the same problem when trying to initiate a DCC chat with my bot.

anyone have any ideas?

[arfer]

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.

You might like to try http://defero.ircspeed.org

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.
_________________
I must have had nothing to do

[nml375]

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.
_________________
NML_375, idling at #eggdrop@IrcNET

[nml375]

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.
_________________
NML_375, idling at #eggdrop@IrcNET

[ruckypup]

I was getting this error for the last few days

When I would initiate the chat from mirc it would fail for: invalid port

when I would /ctcp botnick chat it would connect fine

the problem was mirc settings. DCC PASSIVE was ON

/dcc passive off

*fixed*