Netbox: The first and last IP within a prefix are assumed to be unusable
when a /27 prefix is created only 30 free IPs are mentionned. Although this is valid for Ethernet segments it is confusing when the prefix is used as a pool for nat addresses or aggregating loopbacks. It might be usefull to add a flag to a prefix if it is an ethernet segement or just a container for something else
NetTinkerer
All 2 comments
It's pretty easy to modify this behavior, but we need to figure out how to indicate whether the network/broadcast IPs should be counted. It might make sense to add a new prefix type called "pool" and count otherwise unusable IPs for prefixes of this type. It might also make sense to count them for container prefixes.
jeremystretch
on 31 Oct 2016
FWIW, RackTables work around this by using "reserved" addresses, that a checkbox permits to allocate easily while creating the prefix. That way, every prefix is useable as a pool or not.
footplus
on 3 Nov 2016
Related issues
robbagithub
路
3Comments
Ali-Yazdani
路
3Comments
mrfroggg
路
3Comments
soer7022
路
3Comments
hellerve
路
3Comments
Most helpful comment
It's pretty easy to modify this behavior, but we need to figure out how to indicate whether the network/broadcast IPs should be counted. It might make sense to add a new prefix type called "pool" and count otherwise unusable IPs for prefixes of this type. It might also make sense to count them for container prefixes.