Like its author, Nping isn't perfect. But you can help make
it better by sending bug reports or even writing patches. If Nping
doesn't behave the way you expect, first upgrade to the latest Nmap
version available from http://nmap.org/download.html. If
the problem persists, do some research to determine whether it has already
been discovered and addressed. Try searching for the error message on our
search page at http://insecure.org/search.html or at Google.
Also try browsing the nmap-dev archives at
Read this full manual page as
well. If nothing comes out of this, mail a bug report to
<firstname.lastname@example.org>. Please include everything
you have learned about the problem, as well as what version of
Nping you are running and what operating system version it is
running on. Problem reports and Nping usage questions sent to
<email@example.com> are far more likely to be answered than
those sent to Fyodor directly. If you subscribe to the nmap-dev
list before posting, your message will bypass moderation and get
through more quickly. Subscribe at
Code patches to fix bugs are even better than bug reports.
Basic instructions for creating patch files with your changes are
available at https://svn.nmap.org/nmap/HACKING. Patches may
be sent to nmap-dev (recommended) or to any of the
authors listed in the next section directly.