 |
Network-I |
 |
Version 1.4.7
Terminology:
The binary capture file created by niftap is referred to as a log file.
The formatted display created by nifpan (which takes a log file as its input) is referred to as a report file, or text file.
The traffic-measurement table produced by niftap's -r option is called a frequency file.
Note that a copy of this HTML documentation is also distributed with Network-I
(in the GRYBneti package for Solaris,
and the niftap RPM for Linux - see below).
Network-I consists of two Linux packages, niftap and nifgui,
which are distributed as binary RPMs, along with a common foundation package called greybase.
See the
Downloads
page, where all 3 RPMs are bundled up as a tarfile (tar.gz suffix).
Having unpacked your download to obtain the .rpm RPM files,
you need to install them in the required order by entering the following commands from the Unix shell, as the root user:
rpm -iv greybase-version.rpm
rpm -iv niftap-version.rpm
rpm -iv nifgui-version.rpm
If earlier versions of any of these packages exist on your system
(test for this using
rpm -qi package-name)
you can delete them first
(rpm -e package-name)
or upgrade packages using
rpm -Uv
rather than
rpm -iv.
As always, use
rpm -ql package-name
(eg. rpm -ql niftap) to discover the installed pathnames.
Note that the nifgui package has been split off from the rest of Network-I, due to its Motif X11 dependencies as its installation will fail if they are not satisfied.
Depending on your version of Linux, you should be able to obtain the required
Motif/X11 libs by installing one of the
motif-devel, libmotif-dev or lesstif2
packages, or similar.
/usr/lib must be on your LD_LIBRARY_PATH to run the executables after installing. This should already be the case.
To uninstall, run
rpm -e nifgui niftap greybase
as root.
If you don't have an RPM-based system, the Downloads page also provides a simple tarfile, which can be unpacked and run in-situ.
The unpacked lib directory must be on your LD_LIBRARY_PATH to run the binaries.
You will find a small top-level script called nif which serves as a front-end for calling any Network-I binary and sets up the required paths.
Eg.
/path/to/nif nifpan -nv4
is equivalent to running
nifpan -nv4
in a system where the paths were already set up.
For maximum convenience, you can put a symbolic link to this nif script somewhere on your $PATH.
Older versions of Network-I were also distributed in Solaris package format.
Its package name is GRYBneti, and it depends on a foundation package called GRYBbase.
See the
Downloads
page, where both packages are bundled up as a tarfile (tar.gz suffix).
Having unpacked your download to obtain the .pkg package files,
you need to install them in the required order, by entering the following commands from the Unix shell, as the root user:
pkgadd -d GRYBbase-version GRYBbase
pkgadd -d GRYBneti-version GRYBneti
Answer no to any requests to install conflicting files (Solaris throws up spurious warnings about this for existing directories that are actually symbolic links) and let the installation proceed.
Interaction during the pkgadd can be avoided by adding the arguments
-n -a adminfile
to the pkgadd command,
where adminfile is a copy of the default (/var/sadm/install/admin/default) with the following 3 changes:
instance=quit
setuid=nocheck
conflict=nochange
Installation is now complete, and Network-I is ready for use.
The package is installed under /opt/greybsoft, and contains a bin
subdirectory, in which all the executables reside, and a docs
subdirectory, which contains this HTML-formatted documentation.
To uninstall, run
pkgrm GRYBbase GRYBneti
as root.
Questions can be submitted to support@greyware.co.uk
Please read the
Frequently Asked Questions
before reporting a problem.