Assigning IP workflow is unworkable. No matter the direction it is done. #1441

New Issue

adam · 2025-12-29T16:32:14+01:00

adam commented

2025-12-29 16:32:14 +01:00

Originally created by @phobiadhs on GitHub (Dec 7, 2017).

Issue type

[x ] Feature request
[x ] Bug report
[ ] Documentation

Environment

Python version: 3.4.5-4
NetBox version: 2.2.7

Description

Currently, adding an IP to an interface requires two active tabs (One in the target prefix to identify an available IP and one on the device to assign the IP.) It requires cutting and pasting and simply isn't efficient or workable. It has made Netbox nearly unusable for my shop.

The old method was set up so that you could create the IP from/within the prefix and assign that IP to a device and interface either by searching or using the drill down method (there was a form for this until recently).

In 2.2.5, the ability to add the next available IP within the prefix was added to the Add IP option within the prefix but that really serves no purpose because you still have to have a second window open to assign the IP you just created.

In short, my request is two fold.

When creating an IP within a given prefix using either the add IP method or by selecting from an available block (x available) within the IP list, the ability to assign the created or selected IP to a device be added back. Both the device search and drill down methods were useful and should be included.
When adding an IP to a device from the device screen, the ability to select an prefix, and an available IP (or next available within the prefix) within that prefix be added.

Honestly, this is such a big deal for my company that we are willing to resort to flat out bribery to get this functionality back. Scotch? Rye? Beer? Steaks? Say the word.

Originally created by @phobiadhs on GitHub (Dec 7, 2017). ### Issue type [x ] Feature request  [x ] Bug report  [ ] Documentation  ### Environment * Python version: 3.4.5-4 * NetBox version: 2.2.7 ### Description Currently, adding an IP to an interface requires two active tabs (One in the target prefix to identify an available IP and one on the device to assign the IP.) It requires cutting and pasting and simply isn't efficient or workable. It has made Netbox nearly unusable for my shop. The old method was set up so that you could create the IP from/within the prefix and assign that IP to a device and interface either by searching or using the drill down method (there was a form for this until recently). In 2.2.5, the ability to add the next available IP within the prefix was added to the Add IP option within the prefix but that really serves no purpose because you still have to have a second window open to assign the IP you just created. In short, my request is two fold. 1. When creating an IP within a given prefix using either the add IP method or by selecting from an available block (x available) within the IP list, the ability to assign the created or selected IP to a device be added back. Both the device search and drill down methods were useful and should be included. 2. When adding an IP to a device from the device screen, the ability to select an prefix, and an available IP (or next available within the prefix) within that prefix be added. Honestly, this is such a big deal for my company that we are willing to resort to flat out bribery to get this functionality back. Scotch? Rye? Beer? Steaks? Say the word.

adam closed this issue

2025-12-29 16:32:14 +01:00

adam commented

2025-12-29 16:32:14 +01:00

@jeremystretch commented on GitHub (Dec 8, 2017):

Please see the discussion in #1512. If the current workflow is not sufficient for your needs, NetBox may not be the right solution for you.

@jeremystretch commented on GitHub (Dec 8, 2017): Please see the discussion in #1512. If the current workflow is not sufficient for your needs, NetBox may not be the right solution for you.

adam commented

2025-12-29 16:32:14 +01:00

@phobiadhs commented on GitHub (Dec 8, 2017):

Have you tried adding an IP to a device? Seriously. Just go through the process and tell me that is an efficient use of clicks and time. It takes twice as long as it did before and is so prone to errors that the entire point of the software flies out the window. Beyond that, there is no capability for bulk IP add either now with this method. This is a regression. Sure, it works with some fooling around but is a regression.

@phobiadhs commented on GitHub (Dec 8, 2017): Have you tried adding an IP to a device? Seriously. Just go through the process and tell me that is an efficient use of clicks and time. It takes twice as long as it did before and is so prone to errors that the entire point of the software flies out the window. Beyond that, there is no capability for bulk IP add either now with this method. This is a regression. Sure, it works with some fooling around but is a regression.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#1441