Usage:

 $ java -jar ipterate.jar -h
ipiterate  <start_ip>   <end_ip>

Example:

$ java -jar ipiteratre.jar 192.168.0.0 192.168.0.10
ip addresses checked: 11
192.168.0.10
192.168.0.2
192.168.0.3
192.168.0.4

Name: IPCheck© Perl

Usage:

./ipiteratre.pl -h
ipiterate <startip>  <endip>
 

Example: 

./ipiterate.pl 192.168.0.2 192.168.0.200

checking ip: 192.168.0.2 ping success
checking ip: 192.168.0.3 ping success
checking ip: 192.168.0.4 ping success
checking ip: 192.168.0.5
checking ip: 192.168.0.6
checking ip: 192.168.0.7
checking ip: 192.168.0.8
checking ip: 192.168.0.9
checking ip: 192.168.0.10 ping success
checking ip: 192.168.0.11
checking ip: 192.168.0.12 ping success
checking ip: 192.168.0.13
checking ip: 192.168.0.14
checking ip: 192.168.0.15
checking ip: 192.168.0.16
checking ip: 192.168.0.17
checking ip: 192.168.0.18
checking ip: 192.168.0.19
checking ip: 192.168.0.20

Do you know when a new server or network device is added to your network? Does someone else let you know a week later that a new device needs to be monitored? Are you still searching and putting together a list of ip addressed to iterate through for availability? Run this script once or twice a day for auto-network discovery 

*sweep through a range of IP addresses for availability from the command line.

*quick response times for sweeping through tens of thousands of servers.

- Linux

- Windows

- Solaris

- AIX