EDITED (incorrect information) Now I am not sure this is a bug or a "connection problem" so I might post here, and moderators should decide where it should go.
I've had problems with "Invalid parameters" using aDSL connection and mIRC and trying DCC chat/send on some user (or myself) for a while. Confirmed by two friends so far that also have aDSL connections
Aditional information:
--------------------------
System information:
Windows XP, AMD AthlonXP 2600+ on 1.9GHz.
The bug was also found on my friend's computer using Win2K and AthlonXP,
and on another friend's computer with a P4 and XP sp2
--------------------------
Connection info:
1) mine: aDSL modem AZTECH 355 (DMZ set to my local IP) - using an ethernet card : Via Rhine II Fast ethernet adapter. ISP : MTNet (Macedonia)
2) friend1: Zoom adsl x5 (with latest firmware) (DMZ set to his local ip) - using ethernet card: Intel(R) PRO/100 VE Network Connection ISP: advance group (formerly enterprise.net)
3) friend2: USB Elconm (no DMZ, just port forwarding) - using USB interface/drivers
ISP: MTNet (Macedonia)
--------------------------
Other info:
1) The problem appears when mIRC is connected to ports 6667, 6668, 6662 AND others, but NOT with 6666 (havent tried other ports)
2) When trying to use /debug @test, and doing a //dcc chat $me the following appears:
-> Lelystad.NL.EU.UnderNet.Org NOTICE spion--
CC Chat (62.162.227.232)
-> Lelystad.NL.EU.UnderNet.Org PRIVMSG spion-- :DCC CHAT chat 1050862568 2948
<- :spion--!spion@62.162.227.232 NOTICE spion--
CC Chat (62.162.227.232)
<- :spion--!spion@62.162.227.232 PRIVMSG spion-- :DCC CHAT chat AЊ‘СЏhi
Notice how there is garbage data in the recieved CTCP line instead of the actual ip/port information. The garbage data is IP-address specific, and the same garbage data is sent for different ports. Another example:
-> Lelystad.NL.EU.UnderNet.Org NOTICE spion--
CC Chat (62.162.227.232)
-> Lelystad.NL.EU.UnderNet.Org PRIVMSG spion-- :DCC CHAT chat 1050862568 4129
<- :spion--!spion@62.162.227.232 NOTICE spion--
CC Chat (62.162.227.232)
<- :spion--!spion@62.162.227.232 PRIVMSG spion-- :DCC CHAT chat AЊ‘СЏhi
The same happens on my friends' computers.
I did some additional tests with a mIRC copy connected using port 6666 and :
1) there is no garbage data when I use /dcc chat from mIRC connected to 6666 to mIRC connected to 6666 (the recieved data is normal) Example:
-> graz2.at.Eu.UnderNet.org NOTICE Newk-
CC Chat (62.162.227.232)
-> graz2.at.Eu.UnderNet.org PRIVMSG Newk- :DCC CHAT chat 1050862568 4886
<- :Newk-!newk@62.162.227.232 NOTICE Newk-
CC Chat (62.162.227.232)
<- :Newk-!newk@62.162.227.232 PRIVMSG Newk- :DCC CHAT chat 1050862568 4886
2) there is no garbage data when I use /dcc chat from mIRC connected on port 6667 to mIRC connected on port 6666
3) there IS garbage data recieved when I use /dcc chat from mIRC connected on 6666 to mIRC connected on 6667 (the same garbage data appears in mIRC 6.1's debug @test window, while mIRC 6.16's debug window reports that normal data sent.
On different networks (EFNet) the results are the same
It is could be a mIRC bug, but it also could be something (router?) modifying the INCOMING data when mIRC is connected to port 6667/6668/6662, and not wihen connected to 6666.
Anyway, apperently something is filtering and modifying the incoming data when ports different then 6666 are used.
Dcc options :
1) Bind sockets to IP on/off with the local ip specified DOESNT change anything (the garbage data IS still there)
2) Use random ports, and all the other options DONT change anything (the garbage data IS still there)
3) DCC Server beeing enabled or disabled has NO effects.
