External Ping Sweep Utility
Ping Sweep Utility
The External Ping Sweep utility is a standalone tool that will do a ping sweep on specfied networks, and upload the results to the Device42 appliance.
It runs on windows or linux platforms and has no external dependencies.
Download and install
Once you download the zip file from http://www.device42.com/autodiscovery/, you will see 3 files:
For windows, you need the exe and for linux, you need the *_linux file as executable. Change it to executable mode using chmod +x.
Copy or move ping.cfg.sample to ping.cfg and add your settings as described below.
In the [settings] section, enter the url (FQDN or IP) for the Device42 appliance in your network with credentials. Make sure the credentials have the required access permission.
In [targets] section, you can enter a network range using mask bits or you can use hyphen ranges(per nmap syntax). Examples: 192.168.11.0/24 for subnet range or 192.168.11.1-254 (for hyphenated range).
Multiple ranges can be separated via spaces.
In the [options] section, you have following options, which have explanations on the line above them.
Try to get MAC address for found IP
get_mac_address = True
Try to get hostname for found IP via DNS (if multiple domains using the same IP, only first will be used)
get_hostname = True
Number of ping threads
threads = 128
Timeout for each ping
timeout = 2000
Number of retries (better to keep it higher than 2)
retries = 3
Print all found IPs
print_ips = False
Print all debug messages
debug = False
Running and scheduling
You can start the process by running the executable from the command line. Root or Administrator privileges required. You can also schedule to run this using operating system task scheduler (like crontab or at)
Uploaded data in Device42 appliance.
Please make sure to add the respective subnets in device42 before discovering and uploading IP information, otherwise all IPs will go to an "undefined" subnet.
- MAC address discovery works only for local LANs.
- If reverse DNS option is selected, discovery takes longer.
- Depending on network devices, some subnet IP show up as used. e.g. a network behind a load balancer, where load balancer would reply to ping for any IP in that range.
- Doing a discovery using wireless card will only find itself.