General Information ------- ----------- IceScan is a free open source network analyzing and security auditing tool for Unix-like and Windows operating systems. It uses libpcap, a packet capture and filtering library. Primarily, I've started this project to have an experience in raw sockets and network channel level programming, and also to learn how to port C/C++ apps to different platforms. The main GOAL of IceScan is "coding and educating while coding" :). I understand, that the IceScan NEVER 'll be like NMap, and always 'll be "ugly program". So don't hit me too much! And sorry for my *BAD* English. Also see AUTHORS file for thanksgiving service. The official home of IceScan is http://sourceforge.net/projects/icescan/ and the latest distribution can be found: http://sourceforge.net/project/showfiles.php?group_id=185109 or, on CVS: cvs -d:pserver:anonymous@icescan.cvs.sourceforge.net:/cvsroot/icescan login cvs -z3 -d:pserver:anonymous@icescan.cvs.sourceforge.net:/cvsroot/icescan co -P IceScan Good luck! Alexander Bolshev[Key] Installation ------------ IceScan is known to compile and run on the following systems: - Linux (2.4 and later kernels, various distributions, gcc 3.x and gcc 4.x) - CygWin - Win32 (2000, XP, 2003, Vista) - OpenBSD Full installation instructions can be found in the INSTALL file. See also the appropriate README. files for OS-specific installation instructions. Usage ----- Please consult the man page for a description of each command-line option and interface feature. IPv6 ---- Unfortunaly, IceScan currently doesn't support IPv6. Sorry. How to Report a Bug ------------------- IceScan is still under constant development, so it is possible that you will encounter a bug while using it. Please report bugs to (http://lists.sourceforge.net/mailman/listinfo/icescan-devs). Be sure you tell us: 1) Operating System and version (the command 'uname -sr' may tell you this, although on Linux systems it will probably tell you only the version number of the Linux kernel, not of the distribution as a whole; on Linux systems, please tell us both the version number of the kernel, and which version of which distribution you're running). 2) Version of libpcap, libdnet and libcre. Compressed config.log file. 3) Version of IceScan (the command 'icescan -V' will tell you, unless the bug is so severe as to prevent that from working, and should also tell you the versions of libraries with which it was built) 4) The command you used to invoke IceScan, and the sequence of operations you performed that caused the bug to appear If the bug is produced by a particular trace file, please be sure to send a trace file along with your bug description. Please don't send a trace file greater than 1 MB when compressed. If the trace file contains sensitive information (e.g., passwords), then please do not send it. If IceScan died on you with a 'segmentation violation', 'bus error', 'abort', or other error that produces a UNIX core dump file, you can help the developers a lot if you have a debugger installed. A stack trace can be obtained by using your debugger ('gdb' in this example), the wireshark binary, and the resulting core file. Here's an example of how to use the gdb command 'backtrace' to do so. $ gdb icescan core (gdb) backtrace ..... prints the stack trace (gdb) quit $ The core dump file may be named "icescan.core" rather than "core" on some platforms (e.g., BSD systems). Mailing Lists ------------- -- IceScan CVS History. Here you can see latest CVS patches and monitor development process of IceScan. -- IceScan Developers and Users list. Write here, if you want to propose a patch, report about wanted feature, or simply ask developers about IceScan work. Also, send bugs here, if you find any. You can subscribe at http://sourceforge.net/mail/?group_id=185109. Disclaimer ---------- There is no warranty, expressed or implied, associated with this product. Use at your own risk.