Bulk IPv6 address creation is broken #768

Closed
opened 2025-12-29 16:25:37 +01:00 by adam · 0 comments
Owner

Originally created by @jeremystretch on GitHub (Mar 14, 2017).

Issue type: Bug report

Python version: 2.7.6
NetBox version: 1.9.1

As reported by Didrik on the mailing list, there is a bug affecting the bulk creation of IPv6 addresses. This can be observed by attempting to create a range of IPv6 addresses as such:

2001:db8::[100,200,300]/128

This is expected to create three IPv6 addresses, however it creates 669 addresses. This is due to a bug in the parse_numeric_range() utility function which does not correct cast the beginning of a range to the appropriate numeric base. Thus, instead of returning e.g. range(256, 257) it returns range(100, 257).

Originally created by @jeremystretch on GitHub (Mar 14, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Bug report <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** 2.7.6 **NetBox version:** 1.9.1 <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> As reported by Didrik on the mailing list, there is a bug affecting the bulk creation of IPv6 addresses. This can be observed by attempting to create a range of IPv6 addresses as such: ``` 2001:db8::[100,200,300]/128 ``` This is expected to create three IPv6 addresses, however it creates 669 addresses. This is due to a bug in the `parse_numeric_range()` utility function which does not correct cast the beginning of a range to the appropriate numeric base. Thus, instead of returning e.g. `range(256, 257)` it returns `range(100, 257)`.
adam added the type: bug label 2025-12-29 16:25:37 +01:00
adam closed this issue 2025-12-29 16:25:37 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#768