gem-hunter

$ pip install django-netfields

Getting started

Make sure netfields is in your PYTHONPATH and in INSTALLED_APPS.

InetAddressField will store values in PostgreSQL as type INET. In Python, the value will be represented as an ipaddress.ip_interface object representing an IP address and netmask/prefix length pair unless the store_prefix_length argument is set to False, in which case the value will be represented as an ipaddress.ip_address object.

from netfields import InetAddressField, NetManager

class Example(models.Model):
    inet = InetAddressField()
    # ...

    objects = NetManager()

CidrAddressField will store values in PostgreSQL as type CIDR. In Python, the value will be represented as an ipaddress.ip_network object.

from netfields import CidrAddressField, NetManager

class Example(models.Model):
    inet = CidrAddressField()
    # ...

    objects = NetManager()

MACAddressField will store values in PostgreSQL as type MACADDR. In Python, the value will be represented as a netaddr.EUI object. Note that the default text representation of EUI objects is not the same as that of the netaddr module. It is represented in a format that is more commonly used in network utilities and by network administrators (00:11:22:aa:bb:cc).

from netfields import MACAddressField, NetManager

class Example(models.Model):
    inet = MACAddressField()
    # ...

MACAddress8Field will store values in PostgreSQL as type MACADDR8. In Python, the value will be represented as a netaddr.EUI object. As with MACAddressField, the representation is the common one (00:11:22:aa:bb:cc:dd:ee).

from netfields import MACAddress8Field, NetManager

class Example(models.Model):
    inet = MACAddress8Field()
    # ...

For InetAddressField and CidrAddressField, NetManager is required for the extra lookups to be available. Lookups for INET and CIDR database types will be handled differently than when running vanilla Django. All lookups are case-insensitive and text based lookups are avoided whenever possible. In addition to Django's default lookup types the following have been added:

__net_contained

is contained within the given network

__net_contained_or_equal

is contained within or equal to the given network

__net_contains

contains the given address

__net_contains_or_equals

contains or is equal to the given address/network

__net_overlaps

contains or contained by the given address

__family

matches the given address family

__host

matches the host part of an address regardless of prefix length

__prefixlen

matches the prefix length part of an address

These correspond with the operators and functions from http://www.postgresql.org/docs/9.4/interactive/functions-net.html

CidrAddressField includes two extra lookups (these will be depreciated in the future by __prefixlen):

__max_prefixlen

Maximum value (inclusive) for CIDR prefix, does not distinguish between IPv4 and IPv6

__min_prefixlen

Minimum value (inclusive) for CIDR prefix, does not distinguish between IPv4 and IPv6

from django.db.models import F

from netfields import CidrAddressField, NetManager
from netfields.functions import Family, Masklen

class Example(models.Model):
    inet = CidrAddressField()
    # ...

ipv4_with_num_ips = (
    Example.objects.annotate(
        family=Family(F('inet')),
        num_ips=2 ** (32 - Masklen(F('inet')))  # requires Django >2.0 to resolve
    )
    .filter(family=4)
)

from django.contrib.postgres.indexes import GistIndex
from netfields import CidrAddressField, NetManager

class Example(models.Model):
    inet = CidrAddressField()
    # ...

    class Meta:
        indexes = (
            GistIndex(
                fields=('inet',), opclasses=('inet_ops',),
                name='app_example_inet_idx'
            ),
        )

from django.db import migrations

class Migration(migrations.Migration):
    # ...

    operations = [
        # ...
        migrations.RunSQL(
            "CREATE INDEX app_example_inet_idx ON app_example USING GIST (inet inet_ops);"
        ),
        # ...
    ]