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

Inconsistent workflow adding IP to interface #889

New Issue
Closed
opened 2025-12-29 16:26:45 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:26:45 +01:00
Owner
Copy Link

Originally created by @LordBoBCUP on GitHub (Apr 27, 2017).

Issue type:

Python version: 2.7.12
NetBox version: v1.9.6

Hi, I believe that the workflow for adding a new IP to an interface from the Device->Add IP to Interface allows for you to create and add another, its unlikely that you would want to do this as interfaces typically would only have a single address added to them. If you are for instance going through and adding IPs to virtual interfaces on a newly deployed switch you could think that by clicking that button you can continue adding to more virtual interfaces, however, if you do, you end up at a place where you cannot select Site/Rack/Device/Interface, the options are only Site/Rack then Device/Interface are ----

Not sure if this is the intended workflow and removing the button and only having the create/cancel buttons is better, or if fixing the form presented after clicking create and add another is a better method.

Thanks
Alex

Originally created by @LordBoBCUP on GitHub (Apr 27, 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: <!-- 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.12 **NetBox version:** v1.9.6 <!-- 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. --> Hi, I believe that the workflow for adding a new IP to an interface from the Device->Add IP to Interface allows for you to create and add another, its unlikely that you would want to do this as interfaces typically would only have a single address added to them. If you are for instance going through and adding IPs to virtual interfaces on a newly deployed switch you could think that by clicking that button you can continue adding to more virtual interfaces, however, if you do, you end up at a place where you cannot select Site/Rack/Device/Interface, the options are only Site/Rack then Device/Interface are ---- Not sure if this is the intended workflow and removing the button and only having the create/cancel buttons is better, or if fixing the form presented after clicking create and add another is a better method. Thanks Alex
adam added the status: duplicate label 2025-12-29 16:26:45 +01:00
adam closed this issue 2025-12-29 16:26:45 +01:00
adam commented 2025-12-29 16:26:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 28, 2017):

Pre-population of the form should be covered by #648. Going to close out this one as a duplicate.

its unlikely that you would want to do this as interfaces typically would only have a single address added to them

It's very common to have multiple IPs assigned to an interface. For example, one IPv4 and one IPv6 address.

@jeremystretch commented on GitHub (Apr 28, 2017): Pre-population of the form should be covered by #648. Going to close out this one as a duplicate. > its unlikely that you would want to do this as interfaces typically would only have a single address added to them It's very common to have multiple IPs assigned to an interface. For example, one IPv4 and one IPv6 address.
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
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#889
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?