-
Notifications
You must be signed in to change notification settings - Fork 63
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
Show device information #484
Comments
Hi, NTV displays devices, not Interfaces or IP addresses. We've had some proposals like this before. The problem is that IP addresses (or MAC addresses) don't belong to devices. So, technically speaking, there are no "IP addresses of devices". There are IP addresses of interfaces. A device can easily have 50 interfaces. Interfaces can have theoretically an unlimited number of IP addresses. NetBox models this situation exactly like it is in the real world. Imagine a router or L3 switch with a bunch of IP addresses for interfaces and virtual interfaces (for vlans). Which IP address are we supposed to display? Displaying all of them would end in a complete chaos. |
NetBox allows the assignment of a single primary IPv4 and/or IPv6 directly to a device, though (and a single OOB IP). Having a toggle for that/those might be handy. |
You are right. These ones are indeed device propoerties. I havn't had that in mind.
Why not offer three checkboxes or a multiple choice combobox to allow any combination? We could possibly extend this to all possible device properties, both in the label and in the popup. That way, every user can set what is important to them. |
So you think we can expect this in an upcoming update. Would be nice if I could print out a diagram like this, which included the ip addresses for reference :) |
NetBox version
v3.7.4
Topology Views version
3.9.1
Feature type
New functionality
Proposed functionality
The ability to show the IP address underneath the labels on the map
Use case
ability to easily obtain the IP addresses of devices, and also find free ip addresses.
External dependencies
No response
The text was updated successfully, but these errors were encountered: