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

Primary IPv6 for VDC filters IPv4 #7245

New Issue
Closed
opened 2025-12-29 20:20:49 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:20:49 +01:00
Owner
Copy Link

Originally created by @abhi1693 on GitHub (Nov 17, 2022).

Originally assigned to: @DanSheps, @jeremystretch on GitHub.

NetBox version

v3.4-beta1

Python version

3.10

Steps to Reproduce

  1. Click on Add on the VDC page
  2. Choose ncsu-coreswitch1 on the device drop-down
  3. Click on Primary IPv6 dropdown

Expected Behavior

Only IPv6 addresses should be displayed

Observed Behavior

IPv4 addresses are displayed
image

Originally created by @abhi1693 on GitHub (Nov 17, 2022). Originally assigned to: @DanSheps, @jeremystretch on GitHub. ### NetBox version v3.4-beta1 ### Python version 3.10 ### Steps to Reproduce 1. Click on Add on the VDC page 2. Choose `ncsu-coreswitch1` on the device drop-down 3. Click on Primary IPv6 dropdown ### Expected Behavior Only IPv6 addresses should be displayed ### Observed Behavior IPv4 addresses are displayed ![image](https://user-images.githubusercontent.com/5083532/202446333-c039a05c-3858-416f-b7e5-627fc6bda988.png)
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 20:20:49 +01:00
adam closed this issue 2025-12-29 20:20:50 +01:00
adam commented 2025-12-29 20:20:50 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Nov 17, 2022):

For context it's missing something equivalent to this logic (example for devices):

ebf555e1fb/netbox/dcim/forms/model_forms.py (L614-L638)

@kkthxbye-code commented on GitHub (Nov 17, 2022): For context it's missing something equivalent to this logic (example for devices): https://github.com/netbox-community/netbox/blob/ebf555e1fb1267348ca620c15ce456767d91042a/netbox/dcim/forms/model_forms.py#L614-L638
adam commented 2025-12-29 20:20:51 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 17, 2022):

For context it's missing something equivalent to this logic (example for devices):

I think we can get away with just simple filters on this one as I don't think we care about NAT since this would be for management. TBH I am not sure why we care about nat_inside for regular devices either, seems unneeded to me but I am sure there is a use case somewhere (nat'd IP for a remote site or something)

Maybe it would make sense for a "available_on_device" filter similar to the one on vlans.

@DanSheps commented on GitHub (Nov 17, 2022): > For context it's missing something equivalent to this logic (example for devices): I think we can get away with just simple filters on this one as I don't think we care about NAT since this would be for management. TBH I am not sure why we care about nat_inside for regular devices either, seems unneeded to me but I am sure there is a use case somewhere (nat'd IP for a remote site or something) Maybe it would make sense for a "available_on_device" filter similar to the one on vlans.
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 beta status: accepted type: bug
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#7245
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?