Ping Sweep

ping sweep discovery menu item

Built-in Ping Sweep Autodiscovery

The Ping Sweep discovery tool can be found in the Device42 main menu: Discovery > Ping Sweep.

Device42’s Ping Sweep Auto-discovery performs a series of pings against the specified network(s), performing a quick initial discovery of which IPs are alive [respond to pings], and which are not.

For the time being, the standalone/external ping-sweep utility is also still available (may be deprecated in the future) – scroll to the External Ping Sweep Utility’s section for information on the standalone ping-sweep tool.

Adding a New Ping Sweep Auto-discovery

add ping sweep auto discovery job

  1. Enter a name for the job, and specify your target Network(s) in the “Networks:” field.
  2. Enter a network range using mask bits in slash notation or hyphenated IP ranges (nmap-style syntax). Examples: (slash notation), (hyphenated range):
    • Multiple ranges can be separated via commas, spaces, or new lines.
    • If you want to use reverse DNS values as device names, select that check box; default is unchecked (we recommend leaving it unchecked unless your DNS is perfect to avoid creation of duplicate devices!).
    • An option to strip domain name suffix is also available.
  3. Configure your schedule, if desired, and/or save and kick off the job.

Viewing Ping Sweep Data in Device42

Uploaded data in Device42 appliance.

Configuring ping sweep settings

  1. In the [Settings] section, enter the URL (FQDN or IP) for the Device42 appliance on your network, including credentials. Make sure the credentials have the required access permissions!
  2. In the [Targets] section, enter a network range using mask bits or you can use hyphen ranges(per nmap syntax).
    Examples: for subnet range or (for hyphenated range). Multiple ranges can be separated via spaces.
  3. The [Options] section provides the following options, which have explanations on the line above them.

option_name: explanation = default value

  • get_mac_address: Try to get MAC address for found IP = True
  • get_hostname:Try to get hostname for found IP via DNS (if multiple domains using the
    same IP, only first will be used) = True
  • threads:Number of ping threads = 128
  • timeout:Timeout for each ping = 2000
  • retries:Number of retries (better to keep it higher than 2) = 3
  • print_ips:Print all found IPs = False
  • debug:Print all debug messages = False

Running and scheduling ping sweep jobs

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)

General Ping Sweep Usage Considerations

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.

Other Ping Sweep considerations & best practices:

  • MAC address discovery works only for local LANs.
  • If the reverse DNS option is selected, discovery will take longer.
  • Depending on the behavior of your network devices, some subnets / IP address will show up as used. e.g. some networks that live behind load balancers as some LBs will reply to pings for every IP on a given range.
  • Doing a discovery using wireless card would only find itself.
  • Please note that there exists both a built-in and an external version of the tool that runs as a standalone Windows application.

Using the External 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.

External Ping Sweep Tool

It runs on windows or linux platforms and has no external dependencies.

Download and install:

  1. Download the ping sweep .zip file from
  2. Unzip the downloaded ping_sweep .zip – you will see 3 files:
    • d42pingsweep_windows_vx.x.x.exe
    • d42_pingsweep_linux_vx.x.x
    • ping.cfg.sample.
  3. For Windows, you’ll need to download the .exe. On Linux, you’ll need to set the *_linux file to executable. Do this by setting the executable bit via $ chmod +x.
  4. Copy or move ping.cfg.sample to ping.cfg and add your settings as described below.
  5. Run the appropriate Windows .exe or Linux executable. You’re all set!

During / After an External Ping Sweep

You’ll see a command prompt after you launch the ping sweep. When completed, the Status will change to “Finished”. If successful, you will see “Success” messages in the status box, as should also see new and/or updated Subnet / IP information within Device42.