Replies: 1 comment
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I recently built a small NetBox plugin that I’d like to share with the community.
Project name: NetBox Endpoint Locator
Repository:
https://github.com/Jaycelu/netbox_-endpoint_locator
The goal of this plugin is simple:
If you only have an endpoint IP address or MAC address, you can quickly locate the access switch, interface, and VLAN directly from NetBox.
In day-to-day operations, this is a very common troubleshooting workflow:
So I built this plugin to bring that workflow closer to NetBox.
What it does
Given an
IPv4address or aMACaddress, the plugin queries LibreNMS APIs and tries to return:The main lookup flow is roughly:
IP -> ARP -> MAC -> FDB -> Port -> VLANIf the input is a MAC address, the flow becomes:
MAC -> ARP / FDB -> Port -> VLANThe UI also lets you expand the raw API response, which makes it easier to troubleshoot field differences across LibreNMS versions or environments.
Why I built it
In my own environment, I often need to answer a very practical question:
Where exactly is this endpoint connected?
The traditional workflow usually looks like this:
None of those steps are hard, but they are repetitive and fragmented.
This plugin is meant to be a small but useful bridge:
making NetBox not only a source of truth for inventory, but also a quicker entry point for endpoint troubleshooting.
Current features
IPorMACTarget environment
Currently tested and intended mainly for:
4.4.xInstallation
Install the plugin in the same Python environment used by NetBox, then enable it in
configuration.py:Beta Was this translation helpful? Give feedback.
All reactions