Skip to main content

IP address space administration module of OpenWISP.

Project description

CI Build status Coverage PyPI Dependency monitoring Feature Highlights

Available Features

  • IPv4 and IPv6 IP address management

  • IPv4 and IPv6 Subnet management

  • Automatic free space display for all subnets

  • Visual display for a specific subnet

  • IP request module

  • REST API for CRUD operations and main features

  • Possibility to search for an IP or subnet

  • CSV Import and Export of subnets and their IPs

Project Goals

  • provide basic features of IP Address management as a reusable django app

  • integrate this module in the rest of the OpenWISP ecosystem

  • allow standalone usage (without the rest of OpenWISP)

  • provide ways to extended the core features in order to create derivatives


  • Python 3.7 or higher

  • Django 3.0 or higher

  • Django REST Framework (for the REST API)

  • openwisp-users

  • swapper

Install stable version

pip install openwisp-ipam

Install development version

Install tarball:

pip install

Alternatively you can install via pip using git:

pip install -e git+git://

Installation for development

Install openwisp-ipam for development using following commands:

git clone
cd openwisp-ipam
pip install -e .
pip install -r requirements-test.txt

Launch the development sever:

cd tests/
./ migrate
./ createsuperuser
./ runserver

You can access the admin interface at

Run Tests

Install test requirements:

pip install -r requirements-test.txt

Then run the test suite:

# options "--keepdb" & "--parallel" are optional but
# improve time required for running tests.
./ --keepdb --parallel
# Run tests for the sample_app
SAMPLE_APP=1 ./ --keepdb --parallel

Visual Display of subnets

openwisp-ipam provides a graphical representation of a subnet which shows the available free space under any subnet.


Live documentation

A general live API documentation (following the OpenAPI specification) is available at /api/v1/docs/.

Browsable web interface

Additionally, opening any of the endpoints listed below directly in the browser will show the browsable API interface of Django-REST-Framework, which makes it even easier to find out the details of each endpoint.


See openwisp-users: authenticating with the user token.

When browsing the API via the Live documentation or the Browsable web page, you can also use the session authentication by logging in the django admin.


All list endpoints support the page_size parameter that allows paginating the results in conjunction with the page parameter.

GET /api/v1/<api endpoint url>/?page_size=10
GET /api/v1/<api endpoint url>/?page_size=10&page=2

List of endpoints

Since the detailed explanation is contained in the Live documentation and in the Browsable web page of each endpoint, here we’ll provide just a list of the available endpoints, for further information please open the URL of the endpoint in your browser.

API Throttling

To override the default API throttling settings, add the following to your file:

        'ipam': '100/hour',

The rate descriptions used in DEFAULT_THROTTLE_RATES may include second, minute, hour or day as the throttle period.

Get Next Available IP

A model method to fetch the next available IP address under a specific subnet. This method can also be accessed via a REST API: openwisp_ipam/base/


Returns the next available IP address under a subnet.

Request IP

A model method to create and fetch the next available IP address record under a subnet.


Creates a record for next available IP address and returns JSON data of that record.

POST /api/v1/ipam/subnet/<subnet_id>/request-ip/




Optional description for the IP address

    "ip_address": "ip_address",
    "subnet": "subnet_uuid",
    "description": "optional description"

IpAddress-Subnet List and Create View

An api endpoint to retrieve or create IP addresses under a specific subnet.


Returns the list of IP addresses under a particular subnet.



Create a new IP Address.





IPv6/IPv4 address value


Subnet UUID


Optional description for the IP address

Subnet List/Create View

An api endpoint to create or retrieve the list of subnet instances.


Returns the list of Subnet instances.



Create a new Subnet.





Subnet value in CIDR format


Master Subnet UUID


Optional description for the IP address

Subnet View

An api endpoint for retrieving, updating or deleting a subnet instance.


Get details of a Subnet instance



Delete a Subnet instance



Update details of a Subnet instance.





Subnet value in CIDR format


Master Subnet UUID


Optional description for the IP address

IP Address View

An api endpoint for retrieving, updating or deleting a IP address instance.


Get details of an IP address instance.



Delete an IP address instance.



Update details of an IP address instance.





IPv6/IPv4 value


Subnet UUID


Optional description for the IP address

Export Subnet View

View to export subnet data.



Import Subnet View

View to import subnet data.



Exporting and Importing Subnet

One can easily import and export Subnet data and it’s Ip Addresses using openwisp-ipam. This works for both IPv4 and IPv6 types of networks.


Data can be exported via the admin interface or by using a management command. The exported data is in .csv file format.

From management command
./ export_subnet <subnet value>

This would export the subnet if it exists on the database.

From admin interface

Data can be exported from the admin interface by just clicking on the export button on the subnet’s admin change view.


Data can be imported via the admin interface or by using a management command. The imported data file can be in .csv and .xlsx format. While importing data for ip addresses, the system checks if the subnet specified in the import file exists or not. If the subnet does not exists it will be created while importing data.

From management command
./ import_subnet --file=<file path>
From admin interface

Data can be imported from the admin interface by just clicking on the import button on the subnet view.

CSV file format

Follow the following structure while creating csv file to import data.

Subnet Name
Subnet Value
Organization Slug


Setup (integrate in an existing Django project)

The of your project should contain the following:

    # openwisp2 modules
    # admin
    # rest framework

AUTH_USER_MODEL = 'openwisp_users.User'

Add the URLs to your main

from django.contrib import admin
from django.urls import include, path
from openwisp_users.api.urls import get_api_urls as get_users_api_urls

urlpatterns = [
    # admin URLs
    # IPAM API
    path('', include('openwisp_ipam.urls')),
    # OpenAPI docs
    path('api/v1/', include('openwisp_utils.api.urls')),
    # Bearer Authentication API URL
    path('api/v1/', include((get_users_api_urls(), 'users'), namespace='users')),

Then run:

./ migrate

Extending openwisp-ipam

One of the core values of the OpenWISP project is Software Reusability, for this reason openwisp-ipam provides a set of base classes which can be imported, extended and reused to create derivative apps.

In order to implement your custom version of openwisp-ipam, you need to perform the steps described in this section.

When in doubt, the code in the test project and the sample app will serve you as source of truth: just replicate and adapt that code to get a basic derivative of openwisp-ipam working.

If you want to add new users fields, please follow the tutorial to extend the openwisp-users. As an example, we have extended openwisp-users to sample_users app and added a field social_security_number in the sample_users/

Premise: if you plan on using a customized version of this module, we suggest to start with it since the beginning, because migrating your data from the default module to your extended version may be time consuming.

1. Initialize your custom module

The first thing you need to do is to create a new django app which will contain your custom version of openwisp-ipam.

A django app is nothing more than a python package (a directory of python scripts), in the following examples we’ll call this django app myipam, but you can name it how you want:

django-admin startapp myipam

Keep in mind that the command mentioned above must be called from a directory which is available in your PYTHON_PATH so that you can then import the result into your project.

Now you need to add myipam to INSTALLED_APPS in your, ensuring also that openwisp_ipam has been removed:

    # ... other apps ...
    # all-auth
    # openwisp2 modules
    # 'myipam',   <-- replace without your app-name here
    # admin
    # rest framework
    # Other dependencies

For more information about how to work with django projects and django apps, please refer to the django documentation.

2. Install openwisp-ipam

Install (and add to the requirement of your project) openwisp-ipam:

pip install openwisp-ipam


Add the following to your

EXTENDED_APPS = ('openwisp_ipam',)

4. Add openwisp_utils.staticfiles.DependencyFinder

Add openwisp_utils.staticfiles.DependencyFinder to STATICFILES_FINDERS in your


5. Add openwisp_utils.loaders.DependencyLoader

Add openwisp_utils.loaders.DependencyLoader to TEMPLATES in your, but ensure it comes before django.template.loaders.app_directories.Loader:

        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'OPTIONS': {
            'loaders': [
            'context_processors': [

6. Inherit the AppConfig class

Please refer to the following files in the sample app of the test project:

You have to replicate and adapt that code in your project.

For more information regarding the concept of AppConfig please refer to the “Applications” section in the django documentation.

7. Create your custom models

For the purpose of showing an example, we added a simple “details” field to the models of the sample app in the test project.

You can add fields in a similar way in your file.

Note: for doubts regarding how to use, extend or develop models please refer to the “Models” section in the django documentation.

8. Add swapper configurations

Once you have created the models, add the following to your

# Setting models for swapper module

Substitute myipam with the name you chose in step 1.

9. Create database migrations

Create and apply database migrations:

./ makemigrations
./ migrate

For more information, refer to the “Migrations” section in the django documentation.

10. Create the admin

Refer to the file of the sample app.

To introduce changes to the admin, you can do it in two main ways which are described below.

Note: for more information regarding how the django admin works, or how it can be customized, please refer to “The django admin site” section in the django documentation.

1. Monkey patching

If the changes you need to add are relatively small, you can resort to monkey patching.

For example:

from openwisp_ipam.admin import IpAddressAdmin, SubnetAdmin

SubnetAdmin.app_label = 'sample_ipam'

2. Inheriting admin classes

If you need to introduce significant changes and/or you don’t want to resort to monkey patching, you can proceed as follows:

from django.contrib import admin
from openwisp_ipam.admin import (
    IpAddressAdmin as BaseIpAddressAdmin,
    SubnetAdmin as BaseSubnetAdmin,
from swapper import load_model

IpAddress = load_model('openwisp_ipam', 'IpAddress')
Subnet = load_model('openwisp_ipam', 'Subnet')

class IpAddressAdmin(BaseIpAddressAdmin):
    # add your changes here

class SubnetAdmin(BaseSubnetAdmin):
    app_label = 'myipam'
    # add your changes here

Substitute myipam with the name you chose in step 1.

11. Create root URL configuration

from .sample_ipam import views as api_views
from openwisp_ipam.urls import get_urls

urlpatterns = [
    # ... other urls in your project ...
    # openwisp-ipam urls
    # path('', include(get_urls(api_views))) <-- Use only when changing API views (dicussed below)
    path('', include('openwisp_ipam.urls')),

For more information about URL configuration in django, please refer to the “URL dispatcher” section in the django documentation.

12. Import the automated tests

When developing a custom application based on this module, it’s a good idea to import and run the base tests too, so that you can be sure the changes you’re introducing are not breaking some of the existing features of openwisp-ipam.

In case you need to add breaking changes, you can overwrite the tests defined in the base classes to test your own behavior.

See the tests of the sample app to find out how to do this.

You can then run tests with:

# the --parallel flag is optional
./ test --parallel myipam

Substitute myipam with the name you chose in step 1.

For more information about automated tests in django, please refer to “Testing in Django”.

Other base classes that can be inherited and extended

The following steps are not required and are intended for more advanced customization.

1. Extending the API Views

The API view classes can be extended into other django applications as well. Note that it is not required for extending openwisp-ipam to your app and this change is required only if you plan to make changes to the API views.

Create a view file as done in

For more information about django views, please refer to the views section in the django documentation.


Please refer to the OpenWISP contributing guidelines.

Support channels | Issue Tracker | License

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

openwisp-ipam-1.0.tar.gz (898.5 kB view hashes)

Uploaded source

Built Distribution

openwisp_ipam-1.0-py2.py3-none-any.whl (903.3 kB view hashes)

Uploaded py2 py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page