On Thu, 2003-10-23 at 07:22, Peter Zelezny wrote:
(skip)
>
> If these problems can be fixed, I'd be pretty happy to merge it in.
I'm not sure
> about adding a new /dcc PSEND command, how does mIRC handle it?
The problems of the original patch are now fixed. But if you find
something else I will be very glad to give other comments/explanations.
Now i'll tell the reasons for "/dcc PSEND" command.
mIRC uses Active DCC Send only if you enable "start dcc through
firewall" feature, but if you want to use Active DCC Send without a
socks (useful if you are behind a NAT) you simply cannot (or need to
configure a socks5 server to localhost).
If the /dcc PSEND command is available, one user can choose to use
normal dcc send or active dcc send also without configuring a socks.
IMHO this method would be more useful than the mirc solution that
requires that you change client configuration/set socks every time you
want to change dcc method :)
Example:
USER1(10.0.0.1) --- NAT(195.196.197.198) --- USER2(211.212.213.214)
a) USER1 sends a file to USER2 using DCC SEND
--- Does not work because USER2 cannot connect to 10.0.0.1 that is
a private ip address
b) USER1 sends a file to USER2 using DCC PSEND (or mirc+socks)
--- Does work because USER1 connects to 211.212.213.214 that is
a public ip address.
c) USER2 sends a file to USER1 using DCC SEND
--- Does work because USER1 connects to 211.212.213.214 that is
a public ip address.
d) USER2 sends a file to USER1 using DCC PSEND (or mirc+socks)
--- Does not work because USER2 cannot connect to 10.0.0.1 that is
a private ip address
In case "b" and "c" if the socks supports port listening, mirc maybe
work, but not many socks are configured to do it.
Best regards
--
Daniel Dubois <int24@azzurra.org>
xchat-2.0.5-activedcc-fix1.patch.bz2