| 1 |
|
| 2 |
================================================================= |
| 3 |
NOTE: These instructions are from the 2006 release of ngrep 1.45. |
| 4 |
They are sparse but will still give you the gist. Otherwise |
| 5 |
try ngrep from your favorite package manager! |
| 6 |
================================================================= |
| 7 |
|
| 8 |
ngrep Installation Guide |
| 9 |
------------------------ |
| 10 |
|
| 11 |
1. Install the latest Packet Capture Library |
| 12 |
|
| 13 |
In orer to compile ngrep on any platform, the relevant packet capture |
| 14 |
(PCAP) client support library must be installed. |
| 15 |
|
| 16 |
On UNIX, this is called ``libpcap'' and can be installed either from |
| 17 |
source or from a distribution's particular package management system. |
| 18 |
Some distributions separate the library itself from its development |
| 19 |
headers (i.e. libpcap-devel), so make sure to install both if this is |
| 20 |
the case. |
| 21 |
|
| 22 |
On Windows, the client support library is called ``WinPcap Developer's |
| 23 |
Pack'' and should be unpacked inside the parent directory of the ngrep |
| 24 |
source tree. |
| 25 |
|
| 26 |
The latest versions can be found at: |
| 27 |
|
| 28 |
UNIX: http://tcpdump.org/release/ |
| 29 |
Win32: http://www.winpcap.org/ |
| 30 |
|
| 31 |
|
| 32 |
2. Unpack the ngrep source |
| 33 |
|
| 34 |
Once the client packet capture client support library is installed, |
| 35 |
unpack the ngrep source to a directory. |
| 36 |
|
| 37 |
On Windows, this must be under the same parent directory as the |
| 38 |
WinPcap Developer's Pack. |
| 39 |
|
| 40 |
|
| 41 |
3. Compile the ngrep program |
| 42 |
|
| 43 |
On UNIX, type the following from the root of the ngrep source tree: |
| 44 |
|
| 45 |
% ./configure && make |
| 46 |
|
| 47 |
On Windows, open the ``ngrep.sln'' file located in the ``win32'' |
| 48 |
subdirectory of the ngrep source tree using Visual Studio.NET. From |
| 49 |
there you should be able to Build the solution in either Debug or |
| 50 |
Release mode. Once this is done, copy the resulting ``ngrep.exe'' |
| 51 |
(located in either the ``Debug'' or ``Release'' subdirectory depending |
| 52 |
on compile configuration) into any directory in your path for easy |
| 53 |
usage (``c:\windows'', for instance). |
| 54 |
|
| 55 |
Please ignore the warnings associated with the GNU Regex library |
| 56 |
included in the ngrep source tree. |
| 57 |
|
| 58 |
|
| 59 |
4. Install the PCAP kernel driver |
| 60 |
|
| 61 |
ngrep is a PCAP-based program and therefore requires the PCAP kernel |
| 62 |
driver to be installed before it will function properly. |
| 63 |
|
| 64 |
The PCAP Driver is already integrated into the vast majority of UNIX |
| 65 |
and Linux kernels released within the last ~20 years. |
| 66 |
|
| 67 |
The Windows Platform, however, does not come with an integrated PCAP |
| 68 |
kernel driver by default, so it is necessary to install one before |
| 69 |
ngrep will work. |
| 70 |
|
| 71 |
|
| 72 |
Getting Help |
| 73 |
------------ |
| 74 |
|
| 75 |
On UNIX, if you still have problems compiling or are compiling on an |
| 76 |
unsupported OS, try playing with other build types -- i.e. if you have |
| 77 |
a BSD derived system, try the BSD build type. |
| 78 |
|
| 79 |
If you still have problems, please submit an issue on GitHub or feel |
| 80 |
free to email me, however please try to help yourself first and search |
| 81 |
Google for possible answers before reaching out. |
| 82 |
|
| 83 |
Jordan Ritter <[email protected]> |