You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have quite a large setup with IP-addresses and is building our own web front end that suits our need, and have converted NIPAP to be python3 only. (everything except the webpage). Which seems to be in the works here as well, which is good.
What we have encountered is that we have delegated a bunch of prefixes for a certain purpose and during migration of the data to NIPAP, some prefixes that have been delegated is directly assigned with the whole prefix.
The assigned prefix should reside within a pool and if it released it should then it should become in reservation status and then start to be used for other tasks.
So what we are after is the possibility to assign a whole network from the same sized reservation. (using 10.0.0.0/24 below as an example)
Prefix Type Pool Description
10.0.0.0/24 R pool1
10.0.0.0/24 A Used by DC1
10.2.2.0/23 R pool1
10.2.2.0/24 A Used by DC2
10.2.3.0/25 A Used by DC1
...
This will also make it look more pretty when listing the prefixes.
Personally I think this is a missed or overlooked feature in NIPAP.
The text was updated successfully, but these errors were encountered:
Hi,
We have quite a large setup with IP-addresses and is building our own web front end that suits our need, and have converted NIPAP to be python3 only. (everything except the webpage). Which seems to be in the works here as well, which is good.
What we have encountered is that we have delegated a bunch of prefixes for a certain purpose and during migration of the data to NIPAP, some prefixes that have been delegated is directly assigned with the whole prefix.
The assigned prefix should reside within a pool and if it released it should then it should become in reservation status and then start to be used for other tasks.
So what we are after is the possibility to assign a whole network from the same sized reservation. (using 10.0.0.0/24 below as an example)
This will also make it look more pretty when listing the prefixes.
Personally I think this is a missed or overlooked feature in NIPAP.
The text was updated successfully, but these errors were encountered: