/32 IP's not automatically represented in /32 subnet.

[darcynz]

NetBox version

v2.11.7

Python version

3.7

Steps to Reproduce

1. Have a /32 IP address,

2. Create a /32 Subnet for that IP address

3. In the new subnet on the IP addresses tab observe IP's.

Expected Behavior

IP address reference should be observed and not the ability to assign an IP address in the subnet.

Observed Behavior

'Available IP' Button is present instead of a reference to the IP address as per 1).

[jeremystretch]

Why shouldn't a user be able to create a /32 IP address for assignment to an interface in addition to a /32 route to advertise that address?

[WillIrvine]

I think the issue here is that the /32 IP address gets created in the /32 subnet, but then does not display when navigating back to the Subnet

Example:

1. Make /32 Prefix

2. Make /32 IP address within that prefix

3. Go back to parent prefix, newly created IP address does not display under /32 prefixes IP address's, however IP address has been created.

[darcynz]

Sorry I should have included pictures. We have no issue with duplicate /32's just that they are not displaying within a subnet as per WillIrvine's images above.

[WillIrvine]

Hi

#6455 (comment)

This solution seems to work and AFAIA does not look to cause any undesired issues.
This looks to however be more of a design question as expressed by Jeremy - Should a /32 Prefix contain a /32 IP.

I think it should as people are using IP's and Prefix's for separate purposes, and it maintains a familiar workflow to track both individually. But if not we should at least limit the UI from displaying that there is 1 available address within the prefix.

Happy to put in a PR for this if accepted.

[stevenmyhre]

I also ran into this. We are using prefixes to document NAT translations (even though netbox doesn't support it specifically), and, it's perfectly valid to have a 1-1 nat with a /32 prefix, i.e. 1-1 NAT. However, the single IP Address in the prefix gets lost the way it is coded currently.