I am now working on the second version of my port scanner; My main aim in the new version is to increase the speed that it works at. I know allot of the simple ways of increasing scan speeds.

But I would appreciate it if anyone knew any other ways that could improve the speed of my scanner.

VIPER


[This message has been edited by Viper2002 (edited 05-26-2002).]

Fork.

Spork. Put two uses in one tool, much more efficient.

*smacks spock*

seriously, fork the process and create a couple concurrent sockets. Also you could reduce the timeout, but theres a limit to how much you can do...

Jaded so in your view what is the best ammount of threads to have running at once?

Ive been told five works well but I am really not sure.

VIPER

What OS are you writing this scanner for? Threads a little dangerous in linux and you need to have the libraries installed unless you compile static. Im assuming windows because of the threading.

Threads are different then multiple processes such as using fork()... i think.

and im not going to answer your question for jaded because I really dont know the answer.

--
cEnsE

I think jaded is refering to a new thread per connection you attempt to scan. This way you would just need to wait for all of them to get done in about the same amount of time instead of sequencially. Once all the children report back to the parent process, it can stop taking it's nap and spit out the output.

I wouldn't do any more than four forked processes, and give all the probes an equal timeout length. If you really wanna do it right, you could look to how nmap handles it...

I was fairly certain that threads and child processes were different things, maybe im wrong.