And, correct me if I'm wrong, but, shouldn't it be the other way around as well? Why is it that I can send to someone who is behind a firewall, but they can't send to me? That seems very backwards to me.. :\
As the others are rambeling about the other stuff I take this one
-----
DCC might seem backwards... but it's logic...
If
UserA wants to send something to
UserB, he/she then types the
/dcc send UserB FILENAME command.
This in turns starts to listen to a random port (you can specify the range of this) ... and sends a
CTCP to
UserB, the CTCP goes through the IRC server just like normal messages/notice ..
The CTCP looks something like this:
dcc send 40.72_win9x.exe 3654426342 4944 12528219The first set of numbers being the IP (in long/sort format, don't really know which if which ... check $longup)
The second set of numbers is the port
The Third set of numbers is the filesize in byte
UserB (the one that gets the file from
UserA) now has a choice to either connect to the IP PORT and begin saving the file ... or dismiss the whole thing
---
UserA UserB
------------------------------------------------------------
Listen to port
Send CTCP -----> IRC -----> Read CTCP
Accept Con. <---- DIRECT <--- Connect to IP/PORT
Send File ----> DIRECT ---> Save File
-----
