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

First available IP address on the prefix should not be a network address #6127

New Issue
Closed
opened 2025-12-29 19:37:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:37:05 +01:00
Owner
Copy Link

Originally created by @abhi1693 on GitHub (Feb 22, 2022).

NetBox version

v3.2.0-beta1

Python version

3.8

Steps to Reproduce

  1. Create a prefix with the following data
    • Prefix: 65.49.10.64/26
    • Is pool: true
  2. Go to the prefix page for 65.49.10.64/26 and notice the First available IP

Expected Behavior

The first available IP is the network address ie 65.49.10.64/26

Observed Behavior

The first available IP is the network address should be 65.49.10.65/26

Originally created by @abhi1693 on GitHub (Feb 22, 2022). ### NetBox version v3.2.0-beta1 ### Python version 3.8 ### Steps to Reproduce 1. Create a prefix with the following data - Prefix: `65.49.10.64/26` - Is pool: `true` 2. Go to the prefix page for `65.49.10.64/26` and notice the `First available IP` ### Expected Behavior The first available IP is the network address ie `65.49.10.64/26` ### Observed Behavior The first available IP is the network address should be `65.49.10.65/26`
adam added the type: bug label 2025-12-29 19:37:05 +01:00
adam closed this issue 2025-12-29 19:37:06 +01:00
adam commented 2025-12-29 19:37:06 +01:00
Author
Owner
Copy Link

@tovin07 commented on GitHub (Feb 22, 2022):

Hi @abhi1693,

I think this is not a bug at all. Because you set is pool flag to true, therefore, all IP in this range should be valid to be assigned.

You can check this in the documentation:

And in source code:

@tovin07 commented on GitHub (Feb 22, 2022): Hi @abhi1693, I think this is not a bug at all. Because you set `is pool` flag to `true`, therefore, all IP in this range should be valid to be assigned. You can check this in the documentation: - https://netbox.readthedocs.io/en/stable/core-functionality/ipam/#prefixes - https://netbox.readthedocs.io/en/stable/models/ipam/prefix/ And in source code: - https://github.com/netbox-community/netbox/blob/develop/netbox/ipam/models/ip.py#L343
adam commented 2025-12-29 19:37:06 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 22, 2022):

@tovin07 Somehow I read the documentation wrong. I'll close this bug

@abhi1693 commented on GitHub (Feb 22, 2022): @tovin07 Somehow I read the documentation wrong. I'll close this bug
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 type: bug
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#6127
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?