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

Add option to limit IP Addresses displayed in interface tables #9017

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

Originally created by @JohannesKreuzer on GitHub (Dec 31, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.6.9

Feature type

Change to existing functionality

Proposed functionality

Allow to limit the list of IP Addresses to e.g. 10, so interfaces with many assigned IPs won't clog the table.

Use case

When having e.g. NAT interfaces with 256 assigned IPs on a central firewall on a virtual interface this will clog the table, e.g. making it hard to find the next interface and also the name for the current interface. So an option to limit the viewed addresses would be handy.

Possible look, when limited to 10 addresses:
image

Database changes

N/A

External dependencies

No response

Originally created by @JohannesKreuzer on GitHub (Dec 31, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.6.9 ### Feature type Change to existing functionality ### Proposed functionality Allow to limit the list of IP Addresses to e.g. 10, so interfaces with many assigned IPs won't clog the table. ### Use case When having e.g. NAT interfaces with 256 assigned IPs on a central firewall on a virtual interface this will clog the table, e.g. making it hard to find the next interface and also the name for the current interface. So an option to limit the viewed addresses would be handy. Possible look, when limited to 10 addresses: ![image](https://github.com/netbox-community/netbox/assets/1869209/9222d5d3-4900-4605-b606-8112de274dba) ### Database changes N/A ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:44:16 +01:00
adam closed this issue 2025-12-29 20:44:16 +01:00
adam commented 2025-12-29 20:44:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 2, 2024):

When having e.g. NAT interfaces with 256 assigned IPs on a central firewall on a virtual interface this will clog the table

This occurs because you're incorrectly modeling IP address assignments. IP addresses belonging to a NAT pool should not be assigned to an interface.

@jeremystretch commented on GitHub (Jan 2, 2024): > When having e.g. NAT interfaces with 256 assigned IPs on a central firewall on a virtual interface this will clog the table This occurs because you're incorrectly modeling IP address assignments. IP addresses belonging to a NAT pool should not be assigned to an interface.
adam commented 2025-12-29 20:44:17 +01:00
Author
Owner
Copy Link

@JohannesKreuzer commented on GitHub (Jan 2, 2024):

So what is you suggestion on how to model the link of the NAT pool to the device performing the NAT?

@JohannesKreuzer commented on GitHub (Jan 2, 2024): So what is you suggestion on how to model the link of the NAT pool to the device performing the NAT?
adam commented 2025-12-29 20:44:17 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jan 3, 2024):

Hi there, product manager weighing in here.

I've labeled this FR with status: needs owner because we think there's value in the behavior you describe, despite any misgivings about your particular use case.

For what it's worth, I suggest looking into using IP ranges to model your NAT pools. You can find details in the IPAM docs.

@jeffgdotorg commented on GitHub (Jan 3, 2024): Hi there, product manager weighing in here. I've labeled this FR with `status: needs owner` because we think there's value in the behavior you describe, despite any misgivings about your particular use case. For what it's worth, I suggest looking into using IP ranges to model your NAT pools. You can find details in [the IPAM docs](https://docs.netbox.dev/en/stable/models/ipam/ipaddress/#network-address-translation-nat).
adam commented 2025-12-29 20:44:17 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jan 8, 2024):

Would it make sense to just show the count of IP addresses? If so, I can take onwership of this issue.

@abhi1693 commented on GitHub (Jan 8, 2024): Would it make sense to just show the count of IP addresses? If so, I can take onwership of this issue.
adam commented 2025-12-29 20:44:17 +01:00
Author
Owner
Copy Link

@JohannesKreuzer commented on GitHub (Jan 18, 2024):

I personally would display IPs if there are only 1 or 2 assigned and otherwise say e.g. 30 IP addresses assigned.

@JohannesKreuzer commented on GitHub (Jan 18, 2024): I personally would display IPs if there are only 1 or 2 assigned and otherwise say e.g. 30 IP addresses assigned.
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: accepted type: feature
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#9017
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?