|
|
Joined: Aug 2005
Posts: 4
Self-satisified door
|
OP
Self-satisified door
Joined: Aug 2005
Posts: 4 |
When I try to open 10 more than sockets with different ips and try to close them to open more 10, in mirc really close but when I type netstat -n in the DOS the sockets continues open. I like to know if that is really a bug or has a limit of open sockets with different ips. I am translating the text with a translator then disdains the possible grammatical errors. Thank's ;]
|
|
|
|
Joined: Oct 2003
Posts: 3,918
Hoopy frood
|
Hoopy frood
Joined: Oct 2003
Posts: 3,918 |
well here's the deal
netstat will show WAIT_CLOSE if the socket is closing or in the process of closing, and then a WAIT_TIMEOUT or something
so even if you closed the sockets in mIRC, they might still show up in netstat...
- argv[0] on EFnet #mIRC - "Life is a pointer to an integer without a cast"
|
|
|
|
Joined: Aug 2005
Posts: 4
Self-satisified door
|
OP
Self-satisified door
Joined: Aug 2005
Posts: 4 |
Really with 10 ips it works well, but i tryed with 40 ips for example:
* Open sockets: - scanner29 200.151.130.1:80 tcp connecting scanner194 200.151.130.2:80 tcp connecting scanner314 200.151.130.3:80 tcp connecting scanner91 200.151.130.4:80 tcp connecting scanner522 200.151.130.5:80 tcp connecting ... up to 40
typed netstat -n: TCP 201.8.246.102:6645 200.151.130.10:80 SYN_SENT TCP 201.8.246.102:6646 200.151.130.11:80 SYN_SENT TCP 201.8.246.102:6647 200.151.130.12:80 SYN_SENT TCP 201.8.246.102:6648 200.151.130.13:80 SYN_SENT TCP 201.8.246.102:6649 200.151.130.14:80 SYN_SENT TCP 201.8.246.102:6650 200.151.130.15:80 SYN_SENT TCP 201.8.246.102:6651 200.151.130.16:80 SYN_SENT TCP 201.8.246.102:6652 200.151.130.17:80 SYN_SENT TCP 201.8.246.102:6653 200.151.130.18:80 SYN_SENT TCP 201.8.246.102:6654 200.151.130.19:80 SYN_SENT
well, typed /sockclose * and again netstat -n:
TCP 201.8.246.102:6655 200.151.130.20:80 SYN_SENT TCP 201.8.246.102:6656 200.151.130.21:80 SYN_SENT TCP 201.8.246.102:6657 200.151.130.22:80 SYN_SENT TCP 201.8.246.102:6658 200.151.130.23:80 SYN_SENT TCP 201.8.246.102:6659 200.151.130.24:80 SYN_SENT TCP 201.8.246.102:6660 200.151.130.25:80 SYN_SENT TCP 201.8.246.102:6661 200.151.130.26:80 SYN_SENT TCP 201.8.246.102:6662 200.151.130.27:80 SYN_SENT TCP 201.8.246.102:6663 200.151.130.28:80 SYN_SENT TCP 201.8.246.102:6664 200.151.130.29:80 SYN_SENT
and it continues trying to open the rest of the sockets that I opened and closed before, up to 40, when stops.
I was trying to make a port scanner, but with this speed it will be very slow. =P
I hope that you can understand my problem, thank's. =)
|
|
|
|
Joined: Aug 2005
Posts: 128
Vogon poet
|
Vogon poet
Joined: Aug 2005
Posts: 128 |
I was trying to make a port scanner, but with this speed it will be very slow. =P
Well, mIRC is not for making port scanners, password crackers, bruteforcers. mIRC's speed is slow, and mIRC scripting is used to make your mIRC better, not to scan ports with it. Read a manual of C sockets and make it in C (or C++) if you want speed.
|
|
|
|
Joined: Oct 2003
Posts: 3,918
Hoopy frood
|
Hoopy frood
Joined: Oct 2003
Posts: 3,918 |
again, SYN_SENT does not mean theyre actually 'open'
- argv[0] on EFnet #mIRC - "Life is a pointer to an integer without a cast"
|
|
|
|
Joined: Sep 2003
Posts: 84
Babel fish
|
Babel fish
Joined: Sep 2003
Posts: 84 |
But if you use it for something else, it would be usefully to have more the 40 connections, becuse I was just scripting an IRCD on mIRC and found the same problem. If there are more then 40 รก 50 connection directly trying to join/part or quit the server, mIRC will crash.
I made an bot to, for port scanning, but this one is only scannen joining users for openport (proxy-ports) But if there are to many people connecting add one time.. My bot will crash and all other function's off the bot will be offline :S and that's so bad!
|
|
|
|
|
|