IP Interface Assignment Missing Global VRF #1407

New Issue

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

adam commented

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

Originally created by @dirtycajunrice on GitHub (Nov 15, 2017).

Issue type

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

Environment

Python version: 3.5.2
NetBox version: 2.2.5

Description

When assigning an IP address to an interface with the newly fixed IP mapping tab, you are unable to assign any public IPs directly to the firewall that are not assigned to a created VRF. As most public IPs are not assigned to a VRF as they are Global and unique, this means we still need to do the workaround for directly assigned public IPs.

Fix

To add the Global VRF as searchable option

Originally created by @dirtycajunrice on GitHub (Nov 15, 2017). ### Issue type [ ] Feature request  [x] Bug report  [ ] Documentation  ### Environment * Python version: 3.5.2 * NetBox version: 2.2.5 ### Description When assigning an IP address to an interface with the newly fixed IP mapping tab, you are unable to assign any public IPs directly to the firewall that are not assigned to a created VRF. As most public IPs are not assigned to a VRF as they are Global and unique, this means we still need to do the workaround for directly assigned public IPs. ## Fix To add the Global VRF as searchable option

adam added the type: bug label 2025-12-29 16:32:03 +01:00

adam closed this issue

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

adam commented

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

@candlerb commented on GitHub (Nov 15, 2017):

I only use the global VRF, and on testing it works fine for me; the "Assign IP" tab shows VRF: -------- (implying global VRF)

I also tried creating a new VRF. Then the "Assign IP" tab has two options in VRF dropdown (-------- plus the new VRF I created). And it still works for me: with -------- selected I can find IPs in the global VRF.

Can you explain how to replicate the problem? Or is it just a question of changing the label -------- to Global for clarity?

@candlerb commented on GitHub (Nov 15, 2017): I only use the global VRF, and on testing it works fine for me; the "Assign IP" tab shows `VRF: --------` (implying global VRF) I also tried creating a new VRF. Then the "Assign IP" tab has two options in VRF dropdown (`--------` plus the new VRF I created). And it still works for me: with `--------` selected I can find IPs in the global VRF. Can you explain how to replicate the problem? Or is it just a question of changing the label `--------` to `Global` for clarity?

adam commented

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

@jeremystretch commented on GitHub (Nov 16, 2017):

As @candlerb said I think this is just a cosmetic issue where we're not labeling the "null VRF" as global. We definitely want to be consistent with the labeling though.

@jeremystretch commented on GitHub (Nov 16, 2017): As @candlerb said I think this is just a cosmetic issue where we're not labeling the "null VRF" as global. We definitely want to be consistent with the labeling though.

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#1407