DCC chat problems

Xtianu · Post by **Xtianu** » Wed Apr 02, 2003 10:43 am

I know this has been dug over and over and over, so excuse me for asking again - but I've tried every solution talked about, but it still doesn't work for me.

Here's the setup ..

Router with NAT - 193.254.225.6 / 192.168.0.1
Linux box running the eggdrop - 192.168.0.4
Workstation runing IRC client - 192.168.0.3

I've set my-ip to 192.168.0.4 and nat-ip to 193.254.225.6 in the config file. Some people can connect to the bot using a DCC Chat, others can't - myself included.

I can connect over telnet, and thus "monitor" what happens and this is the lines that get dug up when I try to initiate a DCC chat myself:

Code: Select all

[15:35] -[MI]Xtianu (isayo.arki@193.254.225.6)- DCC Chat (193.254.225.6)
[15:35] CTCP DCC: CHAT chat 3254706438 4222 from [MI]Xtianu (isayo.arki@193.254.225.6)
[15:35] DCC connection: CHAT ([MI]Xtianu!isayo.arki@193.254.225.6)
[15:35] Lost dcc connection to [MI]Xtianu (isayo.arki@193.254.225.6/4222)

Any ideas on what could be wrong?

Thanks in advance ..

ppslim · Post by **ppslim** » Wed Apr 02, 2003 11:06 am

This sounds like one of two possible issues, one of which involves money.

1: You know the way dcc chat works. ClientA makes a request, but it is ClientB that makes the actual network connection.

As such, any port number that ClientA sends out needs to be in the router, to be forwarded to the IP address of ClientA.

In the bottom case, your router must point port 4222 (and the rest of the range setup), to the IP address 192.168.0.3

2: If number 1 is working correctly, then it is likely that your router doesn't loop back requests.

IE, the NAT converter in the router, will not port forward the connection, if made to your external IP address. In this case, the eggdrop is trying to connect to 193.254.255.6 and the router isn't performing a loop back.

This is very common in routers, and catches a lot of people out (including myself). The only way around it, is to spent more on equipment, that can be programed around it.

As for some, but not others (outside of your network) not being able to connect to the bot. This is a issue on there side of the connections.

They may need to setup port forwarding, disable firewalls. They may also need to check that there machiens are sending a port number, in the correct range setup in the IRC client.

Xtianu · Post by **Xtianu** » Fri Apr 04, 2003 4:08 am

Thank you for your help ppslim.

Got it working after having a look at those ports in the router.