filesys filetransfers not sending

Golbez · Post by **Golbez** » Tue May 21, 2002 3:46 pm

Ok, this is sort of a weird one. I got the whole file system working it seems, but for some damn strange reason its not sending DCC files to anyone. It will say its sending the file, attempt to even send the file, but when the DCC transfer tries to start the data never comes through on it. I dont think it has anything to do with NAT or routing because I can do a DCC file transfer to the same person on the same box using XChat. The transfer and filesys modules are both on. Could it be a chmod setting wrong on my filesys folder, perhaps?

stdragon · Post by **stdragon** » Wed May 22, 2002 5:37 am

Does it even send the dcc send request to the person? If so, check to make sure the ip and port are correct and will route back to the bot (via nat).

If it doesn't, then watch the dcc console (maybe with .console +d for debug) to see what is stopping the request.

Golbez · Post by **Golbez** » Wed May 22, 2002 11:44 am

well I dont think it really has anything to do with the routing, because from the same linux box I can do an XCHat DCC file transfer, in and out, no problem. The bot actually has no problem receiving DCC files, it's just sending them. I'll try the debug though, thanks for the idea. If anyone else has any input as well feel free to edumacate me plz.

stdragon · Post by **stdragon** » Wed May 22, 2002 5:42 pm

x-chat and eggdrop have different ways of detecting which ip address to use with dcc sends.

Dcc receives work fine because when someone sends you a file, you actually open a connection to them (outgoing).

Dcc sends don't work because it makes the other person try to connect to your ip:port (incoming). If eggdrop is using the wrong ip address or port then it won't work.

(Yes the dcc stuff seems backwards. When you send a file, you actually receive an incoming connection. When you receive a file, you make an outgoing connection.)