Subnet Groups
Subnet groups organize multiple subnets into named collections for easier scan configuration. Instead of selecting individual subnets in a scan template, you can reference a single group. Built-in groups cannot be modified or deleted. Groups used in scan templates are protected from deletion.
Inputs
| Name | Description | Allowed Values | Default |
|---|---|---|---|
| Name | Unique label for this group | Non-empty string, must be unique across subnet groups | — |
| Description | Optional free-text note about this group | Any text, max 10,000 characters | Empty |
| Subnets | Which subnets belong to this group | One or more existing subnets | None selected |
Fields & Columns
| Name | Description |
|---|---|
| Name | Editable inline (non-built-in) — the group label. Links to the edit form. |
| Description | Editable inline (non-built-in) — optional note |
| Subnets | Count of subnets currently in this group |
| IPs | Total host count across all member subnets |
| Built-in | Whether this group ships with mipo and is read-only |
Gotchas
- Adding or removing subnets from a group takes effect for all scan templates that reference the group.
- Groups referenced by a scan template cannot be deleted — remove the template reference first.
API Calls (6)
| Method | Path | Description |
|---|---|---|
| GET | /api/config/subnet-groups | List all subnet groups |
| POST | /api/config/subnet-groups | Create a new subnet group |
| PUT | /api/config/subnet-groups/:id | Update an existing subnet group |
| DELETE | /api/config/subnet-groups/:id | Delete a subnet group (if unreferenced) |
| GET | /api/config/subnet-groups/:id/details | Get subnet group details with members |
| GET | /api/config/subnet-groups/filter-values | Get available filter values for the subnet groups table |
Related Pages
- Subnets — Individual subnets that are organized into groups
- Scan Templates — Consume subnet groups to define what gets scanned
- FQDN Groups — Equivalent grouping concept for domain-based targets