starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cannot create host addresses (/32) as prefixes. These should be IPv4 addresses instead. #205

New Issue
Closed
opened 2025-12-29 16:19:20 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:19:20 +01:00
Owner
Copy Link

Originally created by @rekeds on GitHub (Jul 13, 2016).

Hi,
if it's a /32 loopback prefix/address.

Looking under Prefixes gives a /32 an Available spot, but the IP is assigned under IPs.
Can't fill the Available ip except importing a /32 entry in Prefixes.

Maybe we could somehow have the /32 marked differently if there is an IP assigned or adding /32 prefixes should be allowed.

(sorry for the english)

Originally created by @rekeds on GitHub (Jul 13, 2016). Hi, if it's a /32 loopback prefix/address. Looking under Prefixes gives a /32 an Available spot, but the IP is assigned under IPs. Can't fill the Available ip except importing a /32 entry in Prefixes. Maybe we could somehow have the /32 marked differently if there is an IP assigned or adding /32 prefixes should be allowed. (sorry for the english)
adam closed this issue 2025-12-29 16:19:20 +01:00
adam commented 2025-12-29 16:19:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 13, 2016):

A /32 is an individual IP address, not a prefix. IPv4 prefixes can only be /31 or larger.

@jeremystretch commented on GitHub (Jul 13, 2016): A /32 is an individual IP address, not a prefix. IPv4 prefixes can only be /31 or larger.
adam commented 2025-12-29 16:19:21 +01:00
Author
Owner
Copy Link

@rekeds commented on GitHub (Jul 18, 2016):

but the idea of that seems wrong..

two /32 loopbacks on different devices, yet I have to show in netbox that it's a /31 prefix?
so that in the Prefix view the IPs are not marked as "Available"? :[

also, the prefix importer allows /32.

@rekeds commented on GitHub (Jul 18, 2016): but the idea of that seems wrong.. two /32 loopbacks on different devices, yet I have to show in netbox that it's a /31 prefix? so that in the Prefix view the IPs are not marked as "Available"? :[ also, the prefix importer allows /32.
adam commented 2025-12-29 16:19:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2016):

two /32 loopbacks on different devices, yet I have to show in netbox that it's a /31 prefix?

No, not at all. In most cases, you'll define a container prefix from which you allocate loopback addresses. For example, if I allocate a loopback IP for each device at a site from 192.0.2.0/24, I'll define that prefix as a container and each of the loopbacks as an individual IP. This is optional of course: You don't strictly need to define a prefix to hold these.

also, the prefix importer allows /32.

Thanks, will get that fixed.

@jeremystretch commented on GitHub (Jul 18, 2016): > two /32 loopbacks on different devices, yet I have to show in netbox that it's a /31 prefix? No, not at all. In most cases, you'll define a container prefix from which you allocate loopback addresses. For example, if I allocate a loopback IP for each device at a site from 192.0.2.0/24, I'll define that prefix as a container and each of the loopbacks as an individual IP. This is optional of course: You don't strictly need to define a prefix to hold these. > also, the prefix importer allows /32. Thanks, will get that fixed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#205
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?