Forums Bug Reports Dcc Port Range Not Working For Me

Dcc Port Range Not Working For Me

hi i just upgraded to mirc 6.35
and im setting my port ranges to 4990~5000
like i always have however when i try to chat my bots
i get invalid port range all in upper 90's lower 100's

CTCP DCC: CHAT chat 2210348535 0 98 <-port

Where are you getting this information from?

eggdrop through telnet shows me the incoming ports on dcc chat that are accepted or rejected
works fine on my mirc 6.21 client

[23:46] -MyNick (MyNick@my.vhost.org)- DCC Chat (131.xxx.xxx.xxx)
[23:46] DCC invalid port: CHAT (MyNick!MyNick@my.vhost.org)
[23:46] CTCP DCC: CHAT chat 2210348535 0 129 from MyNick (MyNick@my.vhost.org)
[23:47] -MyNick (MyNick@my.vhost.org)- DCC Chat (131.xxx.xxx.xxx)
[23:47] DCC invalid port: CHAT (MyNick!MyNick@my.vhost.org)
[23:47] CTCP DCC: CHAT chat 2210348535 0 131 from MyNick (MyNick@my.vhost.org)
[23:47] -MyNick (MyNick@my.vhost.org)- DCC Chat (131.xxx.xxx.xxx)
[23:47] DCC invalid port: CHAT (MyNick!MyNick@my.vhost.org)
[23:47] CTCP DCC: CHAT chat 2210348535 0 133 from MyNick (MyNick@my.vhost.org)
[23:49] -MyNick (MyNick@my.vhost.org)- DCC Chat (131.xxx.xxx.xxx)
[23:49] DCC invalid port: CHAT (MyNick!MyNick@my.vhost.org)
[23:49] CTCP DCC: CHAT chat 2210348535 0 135 from MyNick (MyNick@my.vhost.org)

heres some log with ports 129~135 not in the range i set

The port number being recieved by the eggdrop is 0, not 129-135. This suggests you have passive DCC enabled in mIRC. In passive DCC the initiator sends a CTCP with port 0, the reciever then responds with a port number to connect to (the connection process is reversed).

thank you unchecked passive and its on the proper ports now