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

Unable to assign last IPv6 address in /127 or /128 subnet to an interface #8155

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

Originally created by @matejv on GitHub (Jun 2, 2023).

NetBox version

v3.5.2

Python version

3.10

Steps to Reproduce

(Following up from #12687)

  1. Navigate to device interface
  2. Click "Add IP address"
  3. On "Add a new IP address" form set Address: 2001:db8::1/127 and click Create

Expected Behavior

A new IP Address object for 2001:db8::1/127 should be created and assigned to interface.

Observed Behavior

An error is shown:

2001:db8::1/127 is a broadcast address, which may not be assigned to an interface.

Additional notes:

This affects IPv6 /127 and /128 subnets. For IPv4 /31 and /32 subnets you are able to assign all addresses in the subnet to an interface.

Originally created by @matejv on GitHub (Jun 2, 2023). ### NetBox version v3.5.2 ### Python version 3.10 ### Steps to Reproduce (Following up from #12687) 1. Navigate to device interface 2. Click "Add IP address" 3. On "Add a new IP address" form set Address: 2001:db8::1/127 and click Create ### Expected Behavior A new IP Address object for 2001:db8::1/127 should be created and assigned to interface. ### Observed Behavior An error is shown: 2001:db8::1/127 is a broadcast address, which may not be assigned to an interface. Additional notes: This affects IPv6 /127 and /128 subnets. For IPv4 /31 and /32 subnets you are able to assign all addresses in the subnet to an interface.
adam added the type: bugstatus: duplicate labels 2025-12-29 20:33:10 +01:00
adam closed this issue 2025-12-29 20:33:10 +01:00
adam commented 2025-12-29 20:33:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 2, 2023):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #12687 for further discussion.

@jeremystretch commented on GitHub (Jun 2, 2023): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #12687 for further discussion.
adam commented 2025-12-29 20:33:11 +01:00
Author
Owner
Copy Link

@matejv commented on GitHub (Jun 2, 2023):

Yes, I have raised the issue in #12687 and have been advised by @decoupca to open a separate bug report with details to reproduce the issue, which I have done here.

@matejv commented on GitHub (Jun 2, 2023): Yes, I have raised the issue in #12687 and have been advised by @decoupca to open a separate bug report with details to reproduce the issue, which I have done here.
adam commented 2025-12-29 20:33:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 2, 2023):

@decoupca said:

If you have a confirmed failure of assigning a /31 address, open a bug report with full details on how to reproduce.

That is not what your description above entails.

@jeremystretch commented on GitHub (Jun 2, 2023): @decoupca said: > If you have a confirmed failure of assigning a /31 address, open a bug report with full details on how to reproduce. That is not what your description above entails.
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 status: duplicate 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#8155
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?