DCC RESUME protocol - 04/06/04 08:01 PM
Hi everybody,
After a little look @ http://www.mirc.co.uk/help/dccresum.txt
I have maybe found a bug in the DCC RESUME protocol.
No matter what we write in DCC PORT, mIRC try to resume the file by the port 1024.
It's a heavy problem when you are behind a firewall or a router: you listen one port and mIRC ignore that and try on the port 1024.
If someone can explain me how to force mIRC to request the resume by a port that we can specifie (another than 1024)
The correct syntaxe is:
PRIVMSG User1 CC RESUME filename port position
but in reality, mIRC does:
PRIVMSG User1 CC RESUME filename 1024 position
cu
After a little look @ http://www.mirc.co.uk/help/dccresum.txt
I have maybe found a bug in the DCC RESUME protocol.
No matter what we write in DCC PORT, mIRC try to resume the file by the port 1024.
It's a heavy problem when you are behind a firewall or a router: you listen one port and mIRC ignore that and try on the port 1024.
If someone can explain me how to force mIRC to request the resume by a port that we can specifie (another than 1024)
The correct syntaxe is:
PRIVMSG User1 CC RESUME filename port position
but in reality, mIRC does:
PRIVMSG User1 CC RESUME filename 1024 position
cu