Stream

Join this community to post or comment

Jose Adrian Peña

General Discussion  - 
 
Recently install nipap. But I do not know how to start it. Is there any guide?
1
Add a comment...

Jose Adrian Peña

General Discussion  - 
 
Install NIPAP in UBUNTU 14.04

Hi, all. I have a problem install NIPAP. the terminal display the next oot@ipam:~# nipap-passwd add --user IPAM --password Barcelona2--NAME
Please specify name with --name

Please your help
Thank you.!

1
Kristian “kll” Larsson's profile photo
 
Did you miss a space before - - name? 
Add a comment...

Kheder Habachi

Questions  - 
 
xmlrpc_uri: command not found

how to resolve this in debian 14
2
Add a comment...
 
Hi,

I'm new to Linux in general and have to evaluate different IPAM-systems. NIPAP looks very promising, but for me it is utterly frustrating. I tried to set it up on Debian Jessie and even got the GUI running (now how do i use it?), but only with paster. On the config-www page it says: Then, add a new virtual host or configure the default one with the line: WSGIScriptAlias / /etc/nipap/nipap-www.wsgi ... that's really nice, but where do i do this? Or where do i put that xmlrpc_uri = http://nipap-www@local:s3cret@127.0.0.1:1337??? And there were more WTF-moments where the installation guide just didn't work, because the described command forced errors and so on.

Could someone please produce an (Debian) installation guide for absolute newbies? Some screenshots how to use the GUI would be pretty nice as well. Right now i'm testing phpipam, too. I don't know which of the tools is better, but even if NIPAP rocks i won't use it, because i can't install it without years of linux knowledge.
3
Add a comment...

NIPAP
owner

Announcements  - 
 
#NIPAP  Hades (v0.28.4) is out and marked as stable! Never before have we squashed as many bugs in a release.

The LDAP support has been improved substantially and now works together with a Windows AD server.

New features/fixes:
● Note how this version makes VRF and pool names case-insensitive. Make sure you do have any collisions!
● Improved LDAP support, now does proper TLS and is able to work with a Windows AD server (#697, #726, #737)
● Improve LDAP configuration flexibility by allowing separate LDAP search credentials which is useful in LDAP environments where the ordinary user accounts are not permitted to search the LDAP database (#794)
● Addition of a generic export script that can be used to render configuration files for other daemons, for example a DHCP or DNS server (#815)
● Documentation on nipap.readthedocs.org is now up to date and working (#754)
● whoisd can now listen on IPv6 (#718, #719)
● pynipap is available via PyPi (#710)
● pynipap is now py3 compatible (#579)
● optparse has been replaced with argparse in some places, moving us closer to py3 compatibility (#746)
● Added example import script from Infoblox (#741)
● Improved query interpretation format which lays the foundation for enabling more complex queries using boolean operators, groupings and similar (#683)
● Fix of last_modified timestamp not being updated (#753)
● Fix of web-ui expires field for infinity value (#721, #752)
● Fix of backend for db port not being passed from config file (#742)
● Fix of init script status now having LSB compliant return codes (#739)
● Fix of SQL upgrade script
● Fix of web-ui bug where VRF & pool selector would close when clicked (#728)
● Search fields in web-ui now receive focus on page load (#744)
● Fix of web-ui so that pool can be deselected for new prefixes (#732)
● Fix query interpretation order to align with order in query (#764)
● All smart search tag searches are now case-insensitive (#743)
● Smart search using tag search now works for VRFs and pool (#773, #774)
● CLI prefix view now accepts natural prefix mask as argument (#738)
● Fix of API attributes accepted by add_prefix/edit_prefix (#667)
● Fix VRF RT value using IP:id notation where IP would get converted to integer (#767)
● Fix psutil exception handling. nipapd now starts on Debian Jessie (#760)
● Fix database upgrade script (#759)
● Fix install problem with nipap-www (#775)
● Fix missing attributes inherited_spec in prefix spec (#790)
● Fix missing exception AuthError (#789)
● Fix prefix smart search bug due to merge conflict mistake
● Rework of attribute check for VRF & pool add / edit commands (#784, #785)
● Fix prefix type automatic guessing so it doesn't override the input type for certain scenarios (#800)
● Fix parent prefix selection in database so that it is now possible to shrink assignments (#817)
● Fix update of VRF filter list in web-ui to catch corner case where VRF has been removed (#811)
● Updates to requirements.txt for backend
● Update boilerplate - update your scripts based on the boilerplate! (#821)
● Documentation fixes and some other smaller fixes
2
2
Add a comment...

Andy Brown

Questions  - 
 
I'm probably missing something obvious here. Using nipap web interface as we want to migrate our current IP solution (Northstar) in, I've created the relevant prefixes and sub-entries. When it comes to adding hosts in, I'm choosing "add prefix from prefix" and get the addition page displayed, however I don't seem to be able to specify the IP I'm trying to add. It has correctly selected a /32 but nowhere allows me to specify the IP. If I add an entry in via this page it allocates the next available IP to the host entry, but in our case we need to assign various IPs not necessarily contiguous for the first insert into this system.
Please can you advise on where I'm missing this bit!

Thanks
1
Kristian “kll” Larsson's profile photo
 
Right, so the "add prefix from prefix" allocates the next available address as you have noticed. You need to click "add prefix" in the top right corner of the prefix list page and select "manual" and then fill in the host prefix you want.

Thinking about it, we should probably try to enhance this to make it more intuitive :)
Feel free to open github issues if you have suggestions!
Add a comment...

NIPAP
owner

Announcements  - 
 
#NIPAP v0.28.0, codenamed Hades, is released and available in the Debian testing repository. It's not marked as stable just yet, so this is for the early birds out there. Do try it out and let us know if you bump into difficulties!

The LDAP support has been improved substantially and now works together with a Windows AD server.

Features/fixes:
● Note how this version makes VRF and pool names case-insensitive. Make sure you do have any collisions!
● Improved LDAP support, now does proper TLS and is able to work with a Windows AD server (#697, #726, #737)
● Documentation on nipap.readthedocs.org is now up to date and working (#754)
● whoisd can now listen on IPv6 (#718, #719)
● pynipap is available via PyPi (#710)
● pynipap is now py3 compatible (#579)
● optparse has been replaced with argparse in some places, moving us closer to py3 compatibility (#746)
● Added example import script from Infoblox (#741)
● Improved query interpretation format which lays the foundation for enabling more complex queries using boolean operators, groupings and similar (#683)
● Fix of last_modified timestamp not being updated (#753)
● Fix of web-ui expires field for infinity value (#721, #752)
● Fix of backend for db port not being passed from config file (#742)
● Fix of init script status now having LSB compliant return codes (#739)
● Various other fixes and improvements
5
2
Add a comment...
 
Getting an error trying do run setup:
dli@DLI~/NIPAP/nipap $ python setup.py install
rst2man failed to run: [Errno 2] No such file or directory

I am running this on Linux Mint 17.1 (unbuntu derivative)
1
Add a comment...

NIPAP
owner

Announcements  - 
 
Happy new year everyone!  #NIPAP  Icarus (v0.27.3) is released which fixes three known bugs.

These were the last known bugs introduced with the new features of 0.27 and consequently 0.27.3 is now also available in the Debian stable repository and recommended for general deployment.

Moving from Iron Man (v0.26) should be fairly painless. There are database changes which means that that the upgrade scripts will modify the database tables and stored procedures. While this has been tested multiple times it is recommended that you backup your data before the upgrade (you should always have a backup anyway!).

A recap of changes between Iron Man (v0.26) and Icarus (v0.27);
Features / fixes:
● Fix of backend forking (#653). Now real performance boost!
● AVP (Attribute-Value Pair) support allowing users to store custom attributes associated with prefixes, VRFs or pools (#394, #631, #629)
● Add tags to VRFs for easy categorization and searching (#484)
● Add tags to pools for easy categorization and searching (#566)
● New status field for prefixes, improving the experience for registry type users. Status can be "assigned", "reserved" or "quarantine". (#494)
● New expires field for prefixes allowing users (typically registry) to set an expiration time of an assignment. No actions are actually taken once the expiration time has passed (#599)
● Statistics improvements for pools, now shows number of total/used/free prefixes as opposed to just showing it for addresses. The number of free prefixes is calculated based on the default prefix length of new prefixes assigned from the pool (#528).
● Rewrite of parts of web-UI using AngularJS (#635, #621, #628, #638)
● Add bootstrap CSS for easing web development. Replacement of our own components (like buttons) is off to a soft-start. (#543, #660)
● Permission check of .nipaprc to prevent the world reading it (#632)
● Fix of open file handle leaks in backend (#485)
● Add DB version check for backend to prevent running the backend with the wrong database schema version.
● Backend now ships with requirements.txt to ease running it in a virtualenv. Travis-CI also runs a job for testing NIPAP in a virtualenv.
● Some work on being more Python 3 friendly (#596, #583, #648)
● Fix statistics calculation bug (#590)
● Performance improvements (#589)
● Some documentation updates (#615)
● Various other feature improvements and bug fixes

Enjoy!
2
2
Add a comment...
 
I've received questions on the requirements of running NIPAP over the last couple of days.

#NIPAP  is pretty lightweight itself. As it depends on PostgreSQL for backend database storage and Apache for serving web pages, the requirements are roughly those of Apache + PostgreSQL.

For fast searches and similar it is imperative that the database tables fit in memory. To give an idea, a production installation with roughly 50k prefixes consumes a little under 100MB of disk space for the prefix table. The log table consumes roughly the same and the pool and VRF tables are negligible in size. With 1GB of RAM you are sure to run a performant insallation!
1
Add a comment...

NIPAP
owner

Announcements  - 
 
[Tony Stark]: If my math is right - and it always is - three gigajoules per second.

Tony Stark is a pretty clever man and he likes to make a point of his impeccable math skills. Much like Tony,  #NIPAP  has developed an aptitude for math and large numbers with the addition of statistics across prefixes, pools and VRFs. It is the single largest feature addition in the latest version (0.26), codenamed Iron Man, but does not come alone; a number of other features and fixes have been incorporated in the best version of NIPAP to date. Do enjoy Tony Iron Man!

Features / fixes:
● Support for statistics! Total / used / free prefixes are now listed for prefixes, VRFs and pool (#248)
● Add support for Ubuntu 14.04 (#568)
● Travis-CI testing of package upgrade (#524 / #525)
● Introduced AngularJS framework, it is only used on a few pages at this time but its use will become more widespread with time (#338)
● Web UI now supports searching for VRFs (#347)
● CLI dual-stack address assignment (#526)
● CLI remove now defaults to recursive when assignment contains hosts (#520)
● CLI support for user impersonation via environment variables (#538)
● CLI support for suppressing interactive prompts (#499)
● Web UI pool list page converted to AngularJS (#503)
● Faster pool listing thanks to db index (#497)
● Add db schema version check in nipapd (#460)
● Fix CLI with regards to viewing default VRF (#527)
● Fix for Web UI prefix Save button (#523)
● Fix for CLI .nipaprc bug (#509)
● Fix bug for updating display_prefix on hosts (#515)
● Fix for CLI piping (#464)
● Fix for CLI address modification traceback (#516)
● Fix tag inheritance bugs (#507 & #519)
● Fix bug for calculation of children (#518)
● Fix nipap-passwd traceback (#548)
● Fix www icons (#551)
● Fix two statistics bugs in web-UI (#552 & #553)
● Fix CLI tab completion bug for colons (#422)
● Fix CLI family sanity checking (#558)
● Fix nipap-passwd version check (#557)
● Fix edit of VRF RT in web UI (#575)

You will find it in the NIPAP Debian repo in the stable section.

v0.26 has been tested in a production environment to iron out bugs and we are up to the fourth patch version with 0.26.4, which we are fairly certain is quite bug free.
2
Add a comment...

Created by

About this community

Jose Adrian Peña

General Discussion  - 
 
Hi, all, i have a problem install NIPAP.

The terminal display the next notice

root@ipam:~# nipap-passwd add --user IPAM --password Barcelona*--NAME
Please specify name with --name

I am newbie installing app in Ubuntu.

Please your help. Thank you!
1
Add a comment...

Jeroen Valcke

Questions  - 
 
To my surprise I was able to create a prefix when logged in with a read-only account.

nipap-passwd list
username real name trusted read only
----------------------------------------------------------------
guest Guest/Anonymous 0 1
...

Both adding prefixes via "Add prefix" --> "Manual" and "Add prefix from prefix" work.
Am I missing something here?
1
Add a comment...

Damien Coxall

Questions  - 
 
Hi,

Can someone help me out with a could of questions I have, please.

1. Is there a way to bulk add networks into NIPAP? I am specifically interested in importing from IPPlan, but I'm fine with getting that data into any format needed.

2. Is there a way to add users with hashed passwords from htpasswd.

Thanx in Advance.
1
Add a comment...

Mike Yost

General Discussion  - 
 
I am having issues using the NIPAP api. I am currently evaluating IPAMs and being able to easily use the APIs is important. Whenever I have python go to connect, I get a connection refused. I did a tcpdump on the server and see the syn but nipap sends a reset. I set the xmlrpc_uri following the example. I also set the AuthOption as per the example. From there I try to pull info and get the connection refused message. Not sure what im doing wrong. The docs mention port 9002 but I didnt see the server listening on that port. I looked at the nipap config file and saw port 1337 mentioned and i cant connect to that either. Any ideas?

Im running the latest Ubuntu server build but had to install Apache 2.2 as I couldnt get 2.4 to work if that matters any. Any help would be greatly appreciated. 
1
Mike Yost's profile photoKristian “kll” Larsson's profile photo
2 comments
 
Ok. Awesome! I'm considering publishing docker containers for nipap. Do you use docker? Would it have made your life easier if nipap was available as a docker image?
Add a comment...

Garry Glendown

General Discussion  - 
 
After looking at several other IPAM tools, just came across NIPAP today ... had to do an installation as the demo site isn't working - first impression is very positive, seems to have been programmed with similar requirements and ideas as we have as to how to manage IPs ... docs are somewhat lacking it seems, but all in all, very nice !
1
Kristian “kll” Larsson's profile photo
 
Cool, happy to hear! I'll have a look at the demo site once I'm home (currently traveling).
Add a comment...

Nabil Nasrudin

Questions  - 
 
Hello , im a second year diploma student working on IPAM project with NIPAP.
I'm very new to debian and IP address management.
thanks to installation guide , i managed to get the UI running.

However , it seems that i didnt really understand how to the mechanism works . ex: by adding a prefix ,  normally we would get the info regarding the address usage, how to get the VRF , etc..

Can anyone help this newbie out ?
a 101 guide for the UI  would be very helpful 
thnks

 
1
Kristian “kll” Larsson's profile photo
 
It sounds like you are using the Web ui and I assume you have logged in. At the top of the page you will find a navigation bar that shows you three options; VRFs, prefixes and pools. Just click on prefixes, then on the right hand side you have a button that says add prefix. Click it and fill in the form, after which you have added a prefix.

It's a little bit difficult what it is precisely that you are asking about. Please elaborate if you have more questions.
Add a comment...
 
I am trying to migrate my IPAM away from spreadhseets.
One of the features I can  from a spreadsheet is the ability to link multiple subnets together.
I have an application that requires 3 subnets for a connected router. Does NIPAP allow me to link subnets together (not sure if any IPAM app does).
I have folks in my group that are not network savy and this allows them to assign IPs when needed.
1
Kristian “kll” Larsson's profile photoRobert Gauthier's profile photo
2 comments
 
What I would like is that if someone pulls up the list and finds a spare subnet in the appropriate range, they can also see that subnets 2 and 3 are assigned as well.
For example:
172.19.27.128/28 is assigned
172.20.64.8/30 and 172.20.32.8/30 are used as well.
I don't anticipate most IPAM software and I am looking to see if this has a better gui. I don't need discovery, DNS or DHCP, just a way to manage the hundreds of subnets.
Add a comment...

NIPAP
owner

Announcements  - 
 
Icarus is out! The latest version (v0.27) of #NIPAP, codenamed Icarus is now available for testing!

This is the most massive NIPAP release to date, packed with hubris and sky high ambitions. Hope we can avoid scorching by the sun...

Features / fixes:
● Fix of backend forking (#653). Now real performance boost!
● AVP (Attribute-Value Pair) support allowing users to store custom attributes associated with prefixes, VRFs or pools (#394, #631, #629)
● Add tags to VRFs for easy categorization and searching (#484)
● Add tags to pools for easy categorization and searching (#566)
● New status field for prefixes, improving the experience for registry type users. Status can be "assigned", "reserved" or "quarantine". (#494)
● New expires field for prefixes allowing users (typically registry) to set an expiration time of an assignment. No actions are actually taken once the expiration time has passed (#599)
● Statistics improvements for pools, now shows number of total/used/free prefixes as opposed to just showing it for addresses. The number of free prefixes is calculated based on the default prefix length of new prefixes assigned from the pool (#528).
● Rewrite of parts of web-UI using AngularJS (#635, #621, #628, #638)
● Add bootstrap CSS for easing web development. Replacement of our own components (like buttons) is off to a soft-start. (#543, #660)
● Permission check of .nipaprc to prevent the world reading it (#632)
● Fix of open file handle leaks in backend (#485)
● Add DB version check for backend to prevent running the backend with the wrong database schema version.
● Backend now ships with requirements.txt to ease running it in a virtualenv. Travis-CI also runs a job for testing NIPAP in a virtualenv.
● Some work on being more Python 3 friendly (#596, #583, #648)
● Fix statistics calculation bug (#590)
● Performance improvements (#589)
● Some documentation updates (#615)
● Various other feature improvements and bug fixes

You will find Icarus in the Debian testing repo. It will be a week or two before we roll it out as a stable release.

The magnificent art deco poster courtesy of rodolforever@deviantart.
5
2
Add a comment...

NIPAP
owner

Tips & Tricks  - 
 
CLI Dual stack assignment
Since v0.26, the CLI support dual-stack assignment from pools which means that instead of getting either an IPv4 or IPv6 prefix, you can now get both. Simply use 'dual-stack' as address-family instead of 'ipv4' or 'ipv6' and you will get both. Naturally, your pool needs to contain both IPv4 and IPv6 members with available space.

kll@lingloi320~$ nipap address add prefix 192.0.2.0/24 type reservation description "Core link networks"
Prefix 192.0.2.0/24 added to VRF 'default' [RT: ]
kll@lingloi320~$ nipap address add prefix 2001:db8::/48 type reservation description "Core link networks"
Prefix 2001:db8::/48 added to VRF 'default' [RT: -]
kll@lingloi320~$ nipap pool add name CORE-LINKS default-type assignment description "Link networks for my core network" ipv4_default_prefix_length 31 ipv6_default_prefix_length 112
Pool 'CORE-LINKS' created.
kll@lingloi320~$ nipap pool resize CORE-LINKS add 192.0.2.0/24
Prefix 192.0.2.0/24 in VRF 'default' [RT: -] added to pool 'CORE-LINKS'.
kll@lingloi320~$ nipap pool resize CORE-LINKS add 2001:db8::/48
Prefix 2001:db8::/48 in VRF 'default' [RT: -] added to pool 'CORE-LINKS'.
kll@lingloi320~$ nipap address add from-pool CORE-LINKS family dual-stack description "FOO-CORE-1 <> BAR-CORE-1"
Prefix 192.0.2.0/31 added to VRF 'default' [RT: -]
Prefix 2001:db8::/112 added to VRF 'default' [RT: -]
kll@lingloi320~$


It is not possible to specify prefix-length for each family, so you will need to rely on the default.
1
Add a comment...