| 1 |
INTRODUCTION |
| 2 |
|
| 3 |
The Windows-32 version of ike-scan uses Cygwin to provide Posix compatibility. |
| 4 |
|
| 5 |
You can run ike-scan in two different ways on a Windows-32 system: |
| 6 |
|
| 7 |
a) Use the precompiled Windows-32 binary version of ike-scan. |
| 8 |
This is the easiest way to get ike-scan running on a Windows-32 system. |
| 9 |
The binary package includes the Cygwin DLL. |
| 10 |
For the binary package, you just need to extract the contents of the zip |
| 11 |
file into an empty directory and run IKE-SCAN.EXE from this directory. There |
| 12 |
are no registry settings, ini files, or start menu items so uninstalling just |
| 13 |
involves removing the directory that you installed ike-scan in. |
| 14 |
|
| 15 |
b) Compile ike-scan from source using the Cygwin system. |
| 16 |
To do this, you'll need to download the Cygwin Unix environment from |
| 17 |
http://www.cygwin.com/. In addition to the default installation, you'll need |
| 18 |
GCC and Make. Once Cygwin is installed, you can compile ike-scan in the |
| 19 |
normal way: ./configure, make, make install. |
| 20 |
|
| 21 |
The Windows-32 version of ike-scan is a command-line tool. It does not |
| 22 |
run as a Windows GUI application. You should run it from a DOS box (e.g. |
| 23 |
cmd.exe on NT,2000 and XP; or command.exe on 9x). |
| 24 |
|
| 25 |
DIFFERENCES BETWEEN UNIX AND WINDOWS VERSIONS |
| 26 |
|
| 27 |
The main difference between the Unix and Windows versions of ike-scan is |
| 28 |
that the default directory for the backoff patterns and vendor id patterns |
| 29 |
files on Windows is the directory where the ike-scan.exe executable resides, |
| 30 |
whereas on Unix it is /usr/local/share/ike-scan. |
| 31 |
|
| 32 |
It is possible to specify the location of the patterns files on both Windows |
| 33 |
and Unix systems with the --patterns and --vidpatterns options. |
| 34 |
|
| 35 |
All the text files, apart from this one, use the Unix line-ending convention, |
| 36 |
where each line ends with a single linefeed character. Because of this, they |
| 37 |
will not display correctly in notepad. However, wordpad and Microsoft Word |
| 38 |
will both display the files correctly. |
| 39 |
|
| 40 |
The configuration files, such as ike-backoff-patterns and ike-vendor-ids, |
| 41 |
are all supplied in Unix line ending format. However, ike-scan supports both |
| 42 |
Unix and Windows line ending conventions. |
| 43 |
|
| 44 |
SUPPORTED PLATFORMS |
| 45 |
|
| 46 |
Currently, the Windows-32 version of ike-scan is known to run on the following |
| 47 |
platforms: |
| 48 |
|
| 49 |
Windows NT Server 3.51 |
| 50 |
Windows 98 SE |
| 51 |
Windows NT Workstation 4.0 SP6a |
| 52 |
Windows 2000 Server SP1 |
| 53 |
Windows XP Professional SP1 |
| 54 |
|
| 55 |
I suspect that it will also run on any Intel-based Windows-32 platform. I |
| 56 |
doubt that it will run on Windows 3.1 even with win32s. |
| 57 |
Please let me know if you know of a Win-32 system that it doesn't run on. |
| 58 |
|
| 59 |
KNOWN ISSUES |
| 60 |
|
| 61 |
a) Windows 2000 Server runs the "IPSEC Policy agent" service which listens on |
| 62 |
UDP port 500. If this service is running, it will prevent ike-scan from |
| 63 |
binding to UDP port 500 which is its default source port. |
| 64 |
|
| 65 |
You can either stop the IPSEC Policy agent service or bind ike-scan to a |
| 66 |
different source port. Note that using a source port other than 500 for |
| 67 |
ike-scan may not work with all IKE hosts because some only answer requests |
| 68 |
from source port 500. |