Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent workflow adding IP to interface #1108

Closed
LordBoBCUP opened this issue Apr 27, 2017 · 1 comment
Closed

Inconsistent workflow adding IP to interface #1108

LordBoBCUP opened this issue Apr 27, 2017 · 1 comment
Labels
status: duplicate This issue has already been raised

Comments

@LordBoBCUP
Copy link

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

@jeremystretch
Copy link
Member

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 jeremystretch added the status: duplicate This issue has already been raised label Apr 28, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

2 participants