.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32 .\" .\" Standard preamble: .\" ======================================================================== .de Sh \" Subsection heading .br .if t .Sp .ne 5 .PP \fB\\$1\fR .PP .. .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\} .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\} .\" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .hy 0 .if n .na .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "GENLIST.MAN.1 1p" .TH GENLIST.MAN.1 1p "2006-11-06" "perl v5.8.8" "User Contributed Perl Documentation" .SH "NAME" .Vb 1 \& Genlist \- ping scanner .Ve .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 \& genlist [Input Type] [Scan Options] [General Options] .Ve .SH "DESCRIPTION" .IX Header "DESCRIPTION" .Vb 3 \& Genlist is a program that returns a list of hosts that responding \& to ping probes. Thus, this list can be used to perform an scan of \& these machines using PBNJ or Nmap. .Ve .PP .Vb 1 \& Apart of PBNJ 2.0 suite of tools to monitor changes on a network. .Ve .SH "OPTIONS" .IX Header "OPTIONS" .Vb 3 \& Usage: genlist [Input Type] [General Options] \& Input Type: \& \-s \-\-scan Ping Target Range ex: 10.0.0.\e* .Ve .PP .Vb 3 \& Scan Options: \& \-n \-\-nmap Path to Nmap executable \& \-\-inter Perform scan using non default interface .Ve .PP .Vb 3 \& General Options: \& \-v \-\-version Display version \& \-h \-\-help Display this information .Ve .PP .Vb 1 \& Send Comments to Joshua D. Abraham ( jabra@ccs.neu.edu ) .Ve .SH "EXAMPLE OF GENLIST USED WITH PBNJ" .IX Header "EXAMPLE OF GENLIST USED WITH PBNJ" .Vb 1 \& $ ./genlist \-s 10.0.0.\e* > iplist .Ve .PP .Vb 1 \& $ sudo ./scanpbnj \-i iplist .Ve .SH "EXAMPLE OF GENLIST USED WITH NMAP" .IX Header "EXAMPLE OF GENLIST USED WITH NMAP" .Vb 1 \& $ ./genlist \-s 10.0.0.\e* > iplist .Ve .PP .Vb 1 \& $ sudo ./nmap \-iL iplist .Ve .SH "INPUT TYPE" .IX Header "INPUT TYPE" .Sh "\-s Ping Target Range ex: 10.0.0.*" .IX Subsection "-s Ping Target Range ex: 10.0.0.*" .Vb 5 \& The ping scan is a useful method of only scanning the host that are \& responding to ICMP echo requests. This scan basically takes the host \& that respond to ping and prints them. This is useful in combining \& the result with a PBNJ or Nmap scan because no time is wasted in \& scanning hosts that do not respond. .Ve .SH "SCAN OPTIONS" .IX Header "SCAN OPTIONS" .Sh "\-\-interface " .IX Subsection "--interface " .Vb 3 \& This option sets an alternative interface for performing the scan. \& This is useful when you have multiple interfaces on a machine \& with restrictions on which devices can access certain IP ranges. .Ve .Sh "\-n \-\-nmap " .IX Subsection "-n --nmap " .Vb 7 \& Use an alternative Nmap rather than Nmap located in the your path. \& This is useful if you have multiple version of Nmap installed on \& a system or if you are testing a new version of Nmap. Remember that if \& you are using a newly compiled version of Nmap that you need to \& export NMAPDIR to the location that Nmap was compiled in. Thus, if \& you have compiled Nmap in your homedir, use the following notation to \& run it with Genlist: .Ve .PP .Vb 1 \& $ export NMAPDIR=$HOME/nmap\-VERSION/ .Ve .PP .Vb 1 \& $ sudo genlist \-s 10.0.0.\e* \-\-nmap $HOME/nmap\-VERISON/ .Ve .SH "General Options:" .IX Header "General Options:" .Sh "\-v \-\-version" .IX Subsection "-v --version" .Vb 1 \& Prints the Genlist version number and exits. .Ve .Sh "\-h \-\-help Display this information" .IX Subsection "-h --help Display this information" .Vb 2 \& Prints a short help screen with the most common command flags. \& Running Genlist without any arguments does the same thing. .Ve .SH "FEATURE REQUESTS" .IX Header "FEATURE REQUESTS" .Vb 5 \& Any feature requests should be reported to the online \& feature\-request\-tracking system available on the web at : \& http://sourceforge.net/tracker/?func=add&group_id=149390&atid=774489 \& Before requesting a feature, please check to see if the features has \& already been requested. .Ve .SH "BUG REPORTS" .IX Header "BUG REPORTS" .Vb 5 \& Any bugs found should be reported to the online bug\-tracking system \& available on the web at : \& http://sourceforge.net/tracker/?func=add&group_id=149390&atid=774488. \& Before reporting bugs, please check to see if the bug has already been \& reported. .Ve .PP .Vb 4 \& When reporting PBNJ bugs, it is important to include a reliable way to \& reproduce the bug, version number of PBNJ and Nmap, OS \& name and version, and any relevant hardware specs. And of course, \& patches to rectify the bug are even better. .Ve .SH "SEE ALSO" .IX Header "SEE ALSO" .Vb 1 \& scanpbnj(1) outputpbnj(1), nmap(1) .Ve .SH "AUTHORS" .IX Header "AUTHORS" .Vb 1 \& Joshua D. Abraham ( jabra@ccs.neu.edu ) .Ve .SH "LEGAL NOTICES" .IX Header "LEGAL NOTICES" .Vb 6 \& This program is distributed in the hope that it will be useful, but \& WITHOUT ANY WARRANTY; without even the implied warranty of \& MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU \& General Public License for more details at \& http://www.gnu.org/copyleft/gpl.html, or in the COPYING file included \& with PBNJ. .Ve .PP .Vb 7 \& It should also be noted that PBNJ has occasionally been known to crash \& poorly written applications, TCP/IP stacks, and even operating systems. \& While this is extremely rare, it is important to keep in mind. PBNJ \& should never be run against mission critical systems unless you are \& prepared to suffer downtime. We acknowledge here that PBNJ may crash \& your systems or networks and we disclaim all liability for any damage \& or problems PBNJ could cause. .Ve