Dcc-ing issues with 1.6.10

[ripple]

Okay any help on this one would be appreciated. I have just upgraded to a 1.6.10 and can not dcc to the bot. I am behind a linksys router and did enter my outside IP address in the config file.

However when I attempt to dcc I get a The file could not be sent: The IP address specified is not your own.

What the heck and I missing?


P.S. I am also having the same "confused bot" not really on that channel when it is on the channel but one issue at a time.

[ppslim]

First, you did not state where the client was on the network.

Is this behind the router as well?
If not, is it behind another router?

Setting the outside IP address in the config file will not work.

You should set the IP of the local machine in the "my-ip" setting, and the outside IP in the "nat-ip" setting (not sure if this is the name. Just look through advanced.eggdrop.conf for this).

Next, are you trying to send a chat or a file?
Is it the bot sending the DCC, or are you typing it in your client?

DCC connections, in essance, work in reverse. You type the DCC command in your client, but the remote party makes a connection to your client. Rather than you typing the command, and then trying to connect to the remote party.

Thus, if you try to send a file/chat to the bot, the bot must be able to make a connection to your system. This means that any router must be configured to forward packets to the destination, and any ports reserved for this, are setup in the clients concerned.

I your client, have you setup the correct IP/host in the settings.
EG, in mirc, it has a setting that allows you to specify the local IP and host.

These are required for DCC comunications.
Rather than use your host/ip from your IRC whois, your client sends your local IP, for this to happen, it must be setup correctly, and not be using the IP of your internal LAN.

This allows you to mask your hostname on IRC networks, and includes masking it on networks that provide hostname encryption.

[Altor]

I have a similar problem... the bot is ON the router itself (linux router), can't DCC chat to it and setting NAT-IP is a pain (as my IP changes every 36h)

however, sending a /ctcp botname CHAT to it, makes it connect to me, and then DCC chat works...
It can connect to me, I can't connect to it... same problem for someone else behind a firewall, but others (with or without firewall), can DCC it fine... starting to like these strange things :p

[ppslim]

I have a similar problem...

As stated in my previous post, the connection is sent, from the oposite computer, to the one starting the DCC.

EG.
2 nicknames, ppslim and eggdrop (I wonder which is which).

PPSlim types: /dcc chat eggdrop
PPSlim's client, sends a special CTCP command, with his IP, a port number, and a magic number (which is ignored)
Eggdrop then see's if PPSlim is a valid user and has access to the partyline. If yes, then eggdrop attempts to connect to the IP and Port, ppslim sent to him.

The second method, add's a step to the begining of this, which reverses, which client does what.

PPSlim types: /ctcp eggdrop CHAT
The client sends a CTCP encoded message to the eggdrop, with a keyword of CHAT
Eggdrop then looks to see if PPSlim is a valid user (eg, has a matching hostmask), but does not check flags.
If yes, then the eggdrop is the one to send his IP and port. I this case, the eggdrop sends a user port, as specified in listen command in the userfile.
It is then that PPSlim's client attempts to make the connection to this port (if the client allows it).

*Thus, if typeing "/dcc chat eggdrop" fails for you, then your client is setup incorrectly. EG, it is sending the wrong IP, or an IP that can't be routed too by the eggdrop.

**If typeing "/ctcp eggdrop CHAT" fails, then the eggdrop is sending the wrong IP, or an IP that your client can't route it's connectin too.

In your circumstaces, is the first case (marked with a *).

[ripple]

I get what you are saying - but I am not figuring the solution so far. So let me provide more info.

The bot - sits on a shell account server and is binded to a virtual host. That hostmask and IP have been entered into the conf file with #set my-hostname and set my-ip in the basic setting section. In the advanced settings I did enter my (my client - pIRCh) outside IP using the set nat-ip.

My Client - sits behind the linksys router. As stated above I use pIRCh98 and have searched for a place to specify my local IP and host in pIRCh and dont find one. When I connect to the network it does resolve my IP to my actual rather then the 'apparent ip' (I am connecting to and running the bot on webchat.org network)

I am attempting to establish dcc chat to the bot - I am able to telnet to it, but would prefer to be able to dcc. I attempted to ctcp and receive no error messages but the bot does not connect back to me.

Thanks for everything you have posted so far - its appreciated

[ppslim]

That hostmask and IP have been entered into the conf file with #set my-hostname and set my-ip in the basic setting section. In the advanced settings I did enter my (my client - pIRCh) outside IP using the set nat-ip.

I noted a # in the post.

This usualy signifies that the setting is commented out, and is not set.

Remove the # from both infront of the my-hostname and my-ip settings.

[ripple]

Naw thats not it I just copied that from the original conf file before edits were done. It is not commented out in the final and running config file.

[tainted]

Try using mirc and setting the ip field in the options for your client.