NIPAP is a sleek, intuitive and powerful IP address management system built to efficiently handle large amounts of IP addresses.
Having been developed at a fairly large service provider with operations throughout Europe, NIPAP is well suited for large organisations with massive amounts of IP addresses just as well as smaller enterprises with simple needs. The intuitive web interface lowers the barrier of entry considerable for beginner users while also offering advanced search by regexp and IPv4/IPv6 prefix. It features a powerful Google-style search, both a web GUI and a CLI together with client libraries for Python, Java and Oracle for those that want to integrate with other systems.
Features in short:
- Very fast and scalable to hundreds of thousands of prefixes
- A stylish and intuitive web interface
- Native support for IPv6 (full feature parity with IPv4)
- CLI for the hardcore user
- Native VRF support, allowing overlapping prefixes in different VRFs
- Support for documenting individual hosts
- Very powerful search function (featuring regexp)
- Statistics over used and free addresses
- Integrated audit log
- IP address request system for automatically assigning suitable prefixes
- XML-RPC middleware, allowing easy integration with other applications or writing
- Flexible authentication using SQLite and/or LDAP
Check out the webpage for information, screenshots and more: http://SpriteLink.github.com/NIPAP
If you are running Ubuntu / Debian, add the following repo:
deb http://spritelink.github.io/NIPAP/repos/apt stable main extra
And install nipapd for the backend, nipap-cli for the cli and/or nipap-www for the web pages.
Also see "Getting it" at http://SpriteLink.github.io/NIPAP.
Contributions to NIPAP are more than welcome. Please take a moment to review our contribution guidelines to make the contribution process easy and effective for everyone involved!
Keep track of development and community news:
- Follow NIPAP news on Google+
- Chat with other users and the core team on IRC.
While we have messed up some times, we try to adhere to the Semantic Versioning guidelines.
Note how NIPAP hasn't reached 1.0 yet which means there might still be substantial changes to APIs and similar. While we try to keep it to a minimum, there will inevitable be changes to progress development.