> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/administrator-docs/network-discovery/ipdiscover.md).

# IPDiscover

The **IPDiscover** scan is an [automated action](/administrator-docs/server-setup/configuration/advanced/automations.md) run directly from the server.\
By scanning subnets, it performs an agentless inventory of networked devices and collects basic information such as IP address, MAC address, and device name when available.

***

## Scantypes

Two scan types are supported: **fping** and **nmap**.

* **fping** is faster but cannot retrieve MAC addresses.
* **nmap** can collect MAC addresses when executed with sufficient privileges, but requires installing the corresponding Python library.

## Configuration

{% stepper %}
{% step %}
Go to **Configurations → Networks → IPDiscover**.
{% endstep %}

{% step %}
Update the configuration:

* **IPDiscover**: must be enabled.
* **Scan type**: choose **nmap** or **fping**.
* **Subnet list**: comma-separated list of subnets in CIDR notation.
* **CSV file (optional)**: path to a CSV file defining network configuration.\
  If provided, it overrides the *subnet list* and uses the file content instead (network, tag, name, description per row).
  {% endstep %}

{% step %}
Click **Save**.
{% endstep %}
{% endstepper %}

**CSV configuration file example**

```csv
network,nettag,name,description
172.18.26.0/24,tag26,NAME26,this is a description
172.18.25.0/24,tag25,NAME25,also a description
172.18.15.0/24,tag15,NAME15,still a description
```

## Launch a scan manually

The IPDiscover scan will run based on the recurrence set for its [automated action](/administrator-docs/server-setup/configuration/advanced/automations.md). If you wish to run it manually, please refer to [Automated actions](/administrator-docs/server-setup/configuration/advanced/automations.md#one-time-run) execution for automated actions.

## Consulting IPDiscover results

On the webconsole, navigate to **Inventory** **→** **Networks** **→** **Network devices**.

Use the **pencil icon** in the Actions column to set a custom name if needed.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FRgpii1GDWPIBM4TvqsPs%2Fimage_2026-04-22_164323969.png?alt=media&amp;token=f7933b9a-c906-48e1-895a-68ad658d5acf" alt="IPDiscover results view"><figcaption><p>IPDiscover results view</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ocsinventory-ng.org/administrator-docs/network-discovery/ipdiscover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
